Elevated Call Failure Rate on 9180 Number Series(India Region)

What to do

• Check whether you use Plivo in in. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-06-06 13:00 UTC and 2026-06-06 13:00 UTC may need a replay.

• Subscribe to Plivo's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=plivo works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Plivo 1

1. resolvedJun 6, 2026, 1:00 PM UTC

   Incident Summary — Elevated Call Failure Rate on 9180 Number Series. Specific number series of 9180 were impacted for outbound calls. Incident Window: 5th June 2026, 6:30 PM IST — 6th June 11:30 AM IST Impact: Outbound calls to the 9180 number series were affected throughout the incident window. The failure rate reached approximately 34% at peak. Other number series and carrier paths were unaffected. The issue appeared to partially ease during low-traffic overnight hours but fully reasserted when business-hours call volumes resumed on the morning of 6 June. Resolution: Once issue was detected engineering team analysed the issue and resolved by replacing affected routing infrastructure. Issue was resolved by 6th June 11:30 AM.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.