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
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 24, 2026 | Analytics Service Infrastructure UpgradeMaintenance has started | 1h 20m | Resolved |
| Oct 16, 2026 | STT playground experiencing issuesThis is resolved | 1h 23m | Resolved |
| Oct 15, 2026 | Analytics Performance DegradationThe fix for the Analytics query slowdown has been fully deployed. System lag has cleared and query performance is completely restored. | -177 min | Resolved |
| Oct 15, 2026 | Identified: 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 min | Resolved |
| Oct 1, 2026 | Content Studio experiencing issuesThis is resolved | 28 min | Resolved |
| Oct 1, 2026 | Data 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 min | Resolved |
| Sep 30, 2026 | Data 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 33m | Resolved |
| Sep 24, 2026 | Partial 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 min | Resolved |
| Sep 22, 2026 | API 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 min | Resolved |
| Sep 21, 2026 | Intermittent 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 min | Resolved |
| Aug 28, 2026 | Potential 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 min | Resolved |
| Aug 25, 2026 | Outbound 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 min | Resolved |
| Aug 24, 2026 | Outbound 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 min | Resolved |
| Aug 20, 2026 | Chat Completions API outageAll errors have been resolved. | 4h 17m | Resolved |
| Aug 14, 2026 | High latencies observed for dubbing and voice cloningThis is resolved now | 46 min | Resolved |
| Aug 12, 2026 | Vobiz 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 3m | Resolved |
| Aug 7, 2026 | Intermittent 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 min | Resolved |
| Aug 3, 2026 | Content Agents and Dubbing API are experiencing issuesThis is resolved | 9 min | Resolved |
| Jul 25, 2026 | Degraded 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 0m | Resolved |
| Jul 24, 2026 | Elevated 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 5m | Resolved |
| Jul 23, 2026 | Elevated 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 min | Resolved |
| Jul 20, 2026 | Elevated 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 50m | Resolved |
| Jun 10, 2026 | Degraded 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 min | Resolved |
| May 26, 2026 | Chat Completion API affectedUsers should be able to make calls now. | 14h 38m | Resolved |
| May 26, 2026 | Elevated latenciesAll APIs are operational now | 9h 55m | Resolved |
| May 22, 2026 | Elevated 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 49m | Resolved |
| May 8, 2026 | Degraded 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 min | Resolved |
| Apr 14, 2026 | Issue 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 min | Resolved |
| Apr 10, 2026 | Scheduled 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 9m | Scheduled |
| Apr 4, 2026 | High 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 min | Resolved |
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.