Sarvam API Outage History

30 incidents recorded over the last 365 days, 29 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded Sarvam API Incident

Sarvam API incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 24, 2026Analytics Service Infrastructure UpgradeMaintenance has started1h 20mResolved
Oct 16, 2026STT playground experiencing issuesThis is resolved1h 23mResolved
Oct 15, 2026Analytics Performance DegradationThe fix for the Analytics query slowdown has been fully deployed. System lag has cleared and query performance is completely restored.-177 minResolved
Oct 15, 2026Identified: Smart Flow Service DegradationThe fix for the Smart Flow call failures has been fully deployed and verified. All API calls and workflow executions have returned to normal operation. We appreciate your patience while we resolved this issue. If you…56 minResolved
Oct 1, 2026Content Studio experiencing issuesThis is resolved28 minResolved
Oct 1, 2026Data Availability and Retention Configuration Issues in Voice AgentsWe have completed mitigation for an automated data cleanup configuration issue on Samvaad. All core operational services, real-time calling, and billing system calculations remain fully intact and unaffected. **Impact…-1034 minResolved
Sep 30, 2026Data Availability and Retention Configuration Issues in Voice AgentsWe have completed mitigation for an automated data cleanup configuration issue on Samvaad. All core operational services, real-time calling, and billing system calculations remain fully intact and unaffected. **Impact…2h 33mResolved
Sep 24, 2026Partial Outage on Voice AgentsWe have successfully resolved the latency issues affecting our models. All systems are operating smoothly, and response times have returned to standard performance levels. We will continue monitoring our infrastructure…-1 minResolved
Sep 22, 2026API request authentication issuesThe issue affecting API request authentication has been resolved. Requests are now authenticating normally. We apologize for the disruption and thank you for your patience.31 minResolved
Sep 21, 2026Intermittent KYC Verification IssuesThe issue was resolved at **11:00 PM IST**, and KYC verification is now operating normally. Affected users can retry their verification.-969 minResolved
Aug 28, 2026Potential Impact to 7965-Series Numbers (Vobiz)The issue with the carrier has been resolved, and services are operating normally. We apologize for the inconvenience.43 minResolved
Aug 25, 2026Outbound calling failures on 8071584-series numbers (Vobiz)The issue affected fewer than 15 numbers in the 8071584xxx series. All impacted customers have been contacted directly and offered replacement numbers should they wish to switch. No action is required from customers…-950 minResolved
Aug 24, 2026Outbound calling failures on 8071584-series numbers (Vobiz)The issue affected fewer than 15 numbers in the 8071584xxx series. All impacted customers have been contacted directly and offered replacement numbers should they wish to switch. No action is required from customers…-37 minResolved
Aug 20, 2026Chat Completions API outageAll errors have been resolved.4h 17mResolved
Aug 14, 2026High latencies observed for dubbing and voice cloningThis is resolved now46 minResolved
Aug 12, 2026Vobiz numbers starting with 79 and 80 are observing carrier side issues which is causing drop in connectivity from 12 Aug, 14:25. We expect a resolution from them by 4:30PMThe carrier issue has been resolved now.1h 3mResolved
Aug 7, 2026Intermittent model failures affecting calls We experienced intermittent failures in the calls due to errors from two of our models. Users might have encountered agents not responding in a few turns. The fix has been deployed and we will continue to monitor. We…-20 minResolved
Aug 3, 2026Content Agents and Dubbing API are experiencing issuesThis is resolved9 minResolved
Jul 25, 2026Degraded API PerformanceThe connectivity issues affecting our services have been resolved. All systems are now operating normally. We apologize for any disruption this may have caused and thank you for your patience.2h 0mResolved
Jul 24, 2026Elevated Latency and Intermittent Request FailuresThe upstream network issue has been fully resolved, and latency and error rates across all affected services have returned to normal. All APIs are operating as expected. We appreciate your patience while we worked to…2h 5mResolved
Jul 23, 2026Elevated Latency and Intermittent Request FailuresThe upstream network issue has been fully resolved, and latency and error rates across all affected **Speech To Text** services have returned to normal. All APIs are operating as expected. We appreciate your patience…13 minResolved
Jul 20, 2026Elevated Latency and Intermittent Request FailuresThe upstream network issue has been fully resolved, and latency and error rates across all affected **Speech To Text** services have returned to normal. All APIs are operating as expected. We appreciate your patience…2h 50mResolved
Jun 10, 2026Degraded API PerformanceThe connectivity issues affecting our services have been resolved. All systems are now operating normally. We apologize for any disruption this may have caused and thank you for your patience.41 minResolved
May 26, 2026Chat Completion API affectedUsers should be able to make calls now.14h 38mResolved
May 26, 2026Elevated latenciesAll APIs are operational now9h 55mResolved
May 22, 2026Elevated latency on our APIsAll models and APIs are fully up and running. Systems have returned to normal operating conditions, and we are monitoring performance closely. Thank you for your patience.3h 49mResolved
May 8, 2026Degraded Performance – Text to Speech (TTS)We have successfully resolved the issue impacting TTS requests. All services are now operating normally, and we are continuing to monitor the situation to ensure stability.33 minResolved
Apr 14, 2026Issue Affecting Speech-to-Text Batch ProcessingThe issue impacting the Speech-to-Text Batch API has been resolved. Batch processing is functioning normally, and all systems are fully operational.2 minResolved
Apr 10, 2026Scheduled Maintenance Notification – April 12, 1–3 AM ISTHi, We would like to inform you about scheduled maintenance on **Sunday, 12th April 2026**, from **1:00 AM to 3:00 AM IST**. During this maintenance window, our services will be in a controlled degraded state with…35h 9mScheduled
Apr 4, 2026High Load on Inference ServersAll systems are now fully operational and performing at normal capacity. The high load issue has been resolved and we have confirmed stable performance across Speech To Text, Text To Speech, Text, and Chat services. We…45 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Sarvam API incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Sarvam API Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Sarvam API acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Sarvam API outage in this window ran 1d 11h, against a mean recovery of 3h 47m. If you depend on Sarvam API in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.