Sarvam AI Outage History

Sarvam AI is up right now

Pingoru has recorded 33 incidents for Sarvam AI: 32 in the last 12 months and 17 in the last 90 days.

Source: status.sarvam.ai

33incidents recorded
32last 12 months
17last 90 days
3 hourstypical duration
Incidents per month
048AprMayJunJulAugSepOct4
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct2%
Pingoru began tracking Sarvam AI in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202646 of 720 (1%)
May 2026527 of 744 (4%)
June 202612 of 720 (0%)
July 202648 of 744 (1%)
August 2026813 of 744 (2%)
September 2026521 of 720 (3%)
October 2026413 of 573 (2%)

Incidents, newest first

Minor October 16, 2026 STT playground experiencing issues 1h 23m Content Agents

Started Oct 16, 2026, 07:44 AM UTC· resolved Oct 16, 2026, 09:07 AM UTC

  1. investigating Oct 16, 2026, 07:44 AM UTC

    STT playground batch uploads are failing

  2. resolved Oct 16, 2026, 09:07 AM UTC

    This is resolved

Read the full incident report →

Minor October 15, 2026 Analytics Performance Degradation 30m Call Analytics

Started Oct 15, 2026, 10:10 AM UTC· resolved Oct 15, 2026, 10:40 AM UTC

  1. investigating Oct 15, 2026, 10:10 AM UTC

    We are investigating reports of delayed Analytics queries. A fix is currently being deployed to resolve the underlying API traffic bottleneck. Query processing speed is expected to normalize within 30 minutes. Further updates will follow if necessary.

  2. resolved Oct 15, 2026, 10:40 AM UTC

    The fix for the Analytics query slowdown has been fully deployed. System lag has cleared and query performance is completely restored.

Read the full incident report →

Minor October 15, 2026 Identified: Smart Flow Service Degradation 2h 48m Telephony

Started Oct 15, 2026, 06:30 AM UTC· resolved Oct 15, 2026, 09:18 AM UTC

  1. identified Oct 15, 2026, 06:30 AM UTC

    We have identified the issue causing Smart Flow call failures, which stemmed from a recent API contract change. A fix is actively being implemented and deployed. We expect service to normalize shortly and will post an update upon resolution.

  2. resolved Oct 15, 2026, 09:18 AM UTC

    The 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 continue to experience any residual issues, please reach out to our support team.

Read the full incident report →

Minor October 1, 2026 Content Studio experiencing issues 28m Content Agents

Started Oct 01, 2026, 09:49 AM UTC· resolved Oct 01, 2026, 10:18 AM UTC

  1. investigating Oct 01, 2026, 09:49 AM UTC

    Dubbing projects and clones are not visible for certain users.

  2. resolved Oct 01, 2026, 10:18 AM UTC

    This is resolved

Read the full incident report →

Major September 30, 2026 Data Availability and Retention Configuration Issues in Voice Agents 20h Call Analytics

Started Sep 30, 2026, 11:56 AM UTC· resolved Oct 01, 2026, 07:57 AM UTC

  1. investigating Sep 30, 2026, 11:56 AM UTC

    We are currently investigating an issue affecting historical data availability and retention settings within Voice Agents across select organizations. We have identified missing reporting/analytics data spanning from late August to September 5th and are actively investigating root causes and recovery options. Our team is treating this with high priority. Further updates will be provided as investigation and recovery progress.

Read the full incident report →

Minor September 24, 2026 Partial Outage on Voice Agents 15m Calls

Started Sep 24, 2026, 09:01 AM UTC· resolved Sep 24, 2026, 09:16 AM UTC

  1. investigating Sep 24, 2026, 09:01 AM UTC

    We are currently investigating increased latency across our models, which may cause delayed or degraded responses. Our team is actively working on a fix, and we will share updates as soon as possible. We apologize for the friction this is causing.

  2. resolved Sep 24, 2026, 09:34 AM UTC

    We 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 closely. Thank you for your patience while we addressed this issue.

Read the full incident report →

Minor September 22, 2026 API request authentication issues 31m Speech To Text, Translate, LID, Chat Completion and 4 more

Started Sep 22, 2026, 06:21 AM UTC· resolved Sep 22, 2026, 06:52 AM UTC

  1. identified Sep 22, 2026, 06:21 AM UTC

    We are experiencing issues authenticating some API requests, which may cause requests to fail. Our team is investigating, and we will share updates as more information becomes available.

  2. resolved Sep 22, 2026, 06:52 AM UTC

    The issue affecting API request authentication has been resolved. Requests are now authenticating normally. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Minor September 20, 2026 Intermittent KYC Verification Issues 8h 30m Other APIs

Started Sep 20, 2026, 09:30 AM UTC· resolved Sep 20, 2026, 06:00 PM UTC

  1. identified Sep 20, 2026, 09:30 AM UTC

    Some users might experience intermittent issues with KYC verification through Vobiz.

  2. resolved Sep 20, 2026, 06:00 PM UTC

    The issue was resolved at 11:00 PM IST, and KYC verification is now operating normally. Affected users can retry their verification.

Read the full incident report →

Minor August 28, 2026 Potential Impact to 7965-Series Numbers (Vobiz) 43m Telephony

Started Aug 28, 2026, 05:09 AM UTC· resolved Aug 28, 2026, 05:53 AM UTC

  1. identified Aug 28, 2026, 05:09 AM UTC

    We are currently investigating an issue with our underlying carrier that may affect call connectivity on 7965-series numbers. Our team is working with the provider to resolve the issue and will share further updates as they become available. We apologize for the inconvenience. Provider status: https://status.vobiz.ai/history

  2. resolved Aug 28, 2026, 05:53 AM UTC

    The issue with the carrier has been resolved, and services are operating normally. We apologize for the inconvenience.

Read the full incident report →

Minor August 24, 2026 Outbound calling failures on 8071584-series numbers (Vobiz) – Telephony

Started Aug 24, 2026, 02:00 PM UTC· resolved Aug 24, 2026, 02:00 PM UTC

  1. resolved Aug 24, 2026, 02:00 PM UTC

    We have successfully resolved the issue impacting outbound calls on the +918071584xxx number series. All services are now operating normally, and we are continuing to monitor to ensure stability. We apologize for the inconvenience.

  2. identified Aug 24, 2026, 02:37 PM UTC

    Outbound calls placed from Vobiz numbers in the +918071584xxx series are failing to connect. The cause is a misconfiguration on the carrier side, confirmed by the provider. Impact began at approximately 14:30 IST. These numbers are being replaced. Affected accounts will be contacted directly with replacement numbers. No other number series is affected. Provider status: https://status.vobiz.ai/history

Read the full incident report →

Minor August 20, 2026 Chat Completions API outage 4h 17m Chat Completion

Started Aug 20, 2026, 11:05 AM UTC· resolved Aug 20, 2026, 03:23 PM UTC

  1. investigating Aug 20, 2026, 11:05 AM UTC

    The Chat Completions API is currently unavailable for the sarvam-105b conversations model. All requests to this model are failing. Other APIs are operating normally. We are investigating and will update as soon as we have more information.

  2. resolved Aug 20, 2026, 03:23 PM UTC

    All errors have been resolved.

Read the full incident report →

Minor August 14, 2026 High latencies observed for dubbing and voice cloning 46m Content Agents

Started Aug 14, 2026, 11:48 AM UTC· resolved Aug 14, 2026, 12:34 PM UTC

  1. investigating Aug 14, 2026, 11:48 AM UTC

    High latencies observed for dubbing and voice cloning

  2. resolved Aug 14, 2026, 12:34 PM UTC

    This is resolved now

Read the full incident report →

Minor August 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:30PM 1h 3m Telephony

Started Aug 12, 2026, 10:20 AM UTC· resolved Aug 12, 2026, 11:23 AM UTC

  1. identified Aug 12, 2026, 10:20 AM UTC

    For more details - https://status.vobiz.ai/history

  2. resolved Aug 12, 2026, 11:23 AM UTC

    The carrier issue has been resolved now.

Read the full incident report →

Minor August 7, 2026 Intermittent model failures affecting calls 42m Speech To Text, Translate, LID, Chat Completion and 14 more

Started Aug 07, 2026, 01:47 PM UTC· resolved Aug 07, 2026, 02:29 PM UTC

  1. investigating Aug 07, 2026, 01:47 PM UTC

    We are currently experiencing intermittent request failures affecting calls. Users may encounter agents not responding or calls failing to connect. Our team is actively investigating and we will share an update within 30 minutes.

  2. resolved Aug 07, 2026, 02:29 PM UTC

    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 apologise for the inconvenience caused.

Read the full incident report →

Minor August 3, 2026 Content Agents and Dubbing API are experiencing issues 9m Dubbing, Content Agents, Content Agents

Started Aug 03, 2026, 12:18 PM UTC· resolved Aug 03, 2026, 12:27 PM UTC

  1. investigating Aug 03, 2026, 12:18 PM UTC

    Dubbing and voice cloning are temporarily unavailable. All other APIs are unaffected.

  2. resolved Aug 03, 2026, 12:27 PM UTC

    This is resolved

Read the full incident report →

Minor July 25, 2026 Degraded API Performance 2h Speech To Text, Speech To Text Translate Rest API, Text To Speech Streaming API, Translate and 7 more

Started Jul 25, 2026, 03:18 PM UTC· resolved Jul 25, 2026, 05:18 PM UTC

  1. investigating Jul 25, 2026, 03:18 PM UTC

    We are currently investigating reports of degraded performance and intermittent connectivity issues affecting some of our services. Our team is actively looking into this and will provide updates shortly. We apologize for the inconvenience.

  2. resolved Jul 25, 2026, 05:18 PM UTC

    The 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.

Read the full incident report →

Minor July 24, 2026 Elevated Latency and Intermittent Request Failures 2h 5m Speech To Text, Speech To Text Translate Rest API, Speech To Text Translate Batch API, Speech To Text Batch API and 2 more

Started Jul 24, 2026, 12:41 PM UTC· resolved Jul 24, 2026, 02:46 PM UTC

  1. investigating Jul 24, 2026, 12:41 PM UTC

    We are currently experiencing service degradation due to a network issue with one of our upstream infrastructure providers. Users may encounter elevated latency or intermittent request failures. Our team is actively monitoring the situation and working with the vendor to resolve the issue.

  2. resolved Jul 24, 2026, 02:46 PM UTC

    The 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 resolve this. If you continue to experience any issues, please reach out to our support team.

Read the full incident report →

Minor May 26, 2026 Chat Completion API affected 14h 38m Chat Completion

Started May 26, 2026, 03:03 PM UTC· resolved May 27, 2026, 05:42 AM UTC

  1. identified May 26, 2026, 03:03 PM UTC

    We're currently experiencing failures on the Chat Completion API due to an issue with the underlying model. Our team is actively working on a resolution. We'll share another update as soon as we have more information.

  2. resolved May 27, 2026, 05:42 AM UTC

    Users should be able to make calls now.

Read the full incident report →

Minor May 26, 2026 API Service Disruption — All APIs Affected – Speech To Text, Speech To Text Translate Rest API, Text To Speech Streaming API, Translate and 8 more

Started May 26, 2026, 02:41 PM UTC· resolved May 26, 2026, 02:41 PM UTC

  1. investigating Mar 26, 2026, 04:29 AM UTC

    We are currently investigating an issue affecting all Sarvam API endpoints and the API dashboard (dashboard.sarvam.ai: http://dashboard.sarvam.ai). Users may experience errors or timeouts when making API requests. Our team is actively working on resolving this. We will provide updates as we learn more.

  2. identified Mar 26, 2026, 05:34 AM UTC

    The issue has been identified and our services are recovering. Most API endpoints are now operational, though some users may experience degraded performance including elevated latency or intermittent errors as systems fully stabilize. We are actively monitoring the recovery. A further update will be provided once all services are fully restored.

  3. monitoring Mar 26, 2026, 05:56 AM UTC

    Most API endpoints are now operational, though some users may experience degraded performance including elevated latency or intermittent errors as systems fully stabilize. The API Dashboard (dashboard.sarvam.ai: http://dashboard.sarvam.ai) may experience temporary downtime as we complete the recovery process. API access via keys continues to work — only the dashboard UI is affected. We will update once the dashboard is fully back online.

  4. monitoring Mar 26, 2026, 06:29 AM UTC

    All API endpoints and the API Dashboard (dashboard.sarvam.ai: http://dashboard.sarvam.ai) are now back online and operating normally. We are continuing to monitor the situation to ensure stability. Thank you for your patience.

  5. resolved Mar 26, 2026, 06:52 AM UTC

    All Sarvam API endpoints and the API Dashboard (dashboard.sarvam.ai: http://dashboard.sarvam.ai) are fully operational. The disruption was caused by an unexpected surge in usage that exceeded our current capacity thresholds. A detailed Root Cause Analysis (RCA) will be published shortly. Thank you for your patience.

  6. resolved May 26, 2026, 02:41 PM UTC

    APIs are now fully operational. The issue was caused by temporary model unavailability, which has been resolved. Thank you for your patience.

Read the full incident report →

Minor May 26, 2026 Elevated latencies 9h 55m Speech To Text, Speech To Text Translate Rest API, Text To Speech Streaming API, Translate and 9 more

Started May 26, 2026, 08:02 AM UTC· resolved May 26, 2026, 05:58 PM UTC

  1. identified May 26, 2026, 08:02 AM UTC

    We're currently observing elevated latencies on our APIs. Our team has identified the issue and is actively investigating. We'll share another update as soon as we have more information.

  2. identified May 26, 2026, 10:46 AM UTC

    We're currently experiencing intermittent failures on APIs due to model unavailability. Our team has identified the issue and is actively working on a resolution. We'll share another update as soon as we have more information.

  3. monitoring May 26, 2026, 05:11 PM UTC

    The incident has been resolved and APIs are functional now. We’re continuing to monitor the services closely to ensure stability. Thank you for your patience and understanding.

  4. resolved May 26, 2026, 05:58 PM UTC

    All APIs are operational now

Read the full incident report →

Minor May 22, 2026 Elevated latency on our APIs 3h 49m Speech To Text, Speech To Text Translate Rest API, Text To Speech Streaming API, Translate and 10 more

Started May 22, 2026, 05:20 AM UTC· resolved May 22, 2026, 09:09 AM UTC

  1. identified May 22, 2026, 05:20 AM UTC

    We're currently seeing higher-than-usual latency on our Speech-to-Text and Text-to-Speech APIs. Requests are still going through, but responses may be slower than normal. We've identified a network-level issue affecting one of our infrastructure providers and are actively working with them to resolve it. We'll share an update shortly.

  2. identified May 22, 2026, 08:18 AM UTC

    We are currently experiencing a outage affecting all model APIs. API requests are failing intermediately. Affected services include Speech-to-Text, Text-to-Speech, Translation, Transliteration, and all other model endpoints.

  3. resolved May 22, 2026, 09:09 AM UTC

    All 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.

Read the full incident report →

Minor May 8, 2026 Degraded Performance – Text to Speech (TTS) 1h 36m Text To Speech Streaming API, Text To Speech

Started May 08, 2026, 07:01 AM UTC· resolved May 08, 2026, 08:37 AM UTC

  1. investigating May 08, 2026, 07:01 AM UTC

    We are currently experiencing degraded performance with our Text to Speech (TTS) services affecting a subset of users. A temporary mitigation has been deployed, and the team is actively working on a permanent fix. We will continue to share updates as we make progress.

  2. resolved May 08, 2026, 08:37 AM UTC

    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.

Read the full incident report →

Major April 14, 2026 Issue Affecting Speech-to-Text Batch Processing 2m

Started Apr 14, 2026, 11:54 AM UTC· resolved Apr 14, 2026, 11:57 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Critical April 4, 2026 High Load on Inference Servers 45m

Started Apr 04, 2026, 04:34 AM UTC· resolved Apr 04, 2026, 05:20 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major October 16, 2025 The Bulbul TTS model experienced an unexpected downtime –

Started Oct 16, 2025, 12:25 PM UTC· resolved Oct 16, 2025, 12:25 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →