Plivo Outage History

Plivo is up right now

Plivo had 41 outages in the last 2 years totaling 83h 4m of downtime — averaging 1.7 incidents per month.

There were 41 Plivo outages since January 14, 2025 totaling 83h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.plivo.com

Notice June 15, 2026

Call failures for 911600 series numbers in India region

Detected by Pingoru
Jun 15, 2026, 07:26 AM UTC
Resolved
Jun 15, 2026, 06:00 AM UTC
Duration
Timeline · 1 update
  1. resolved Jun 15, 2026, 07:26 AM UTC

    Dear Valued Customer, We recently experienced call failures in the India region for the 911600 series numbers. After initial investigation, our carrier partner was notified, who took corrective action and the incident was resolved Incident Start Time: 15th June 2026, 11:15 IST Incident End Time: 15th June 2026, 11:45 IST If you have any questions or concerns regarding this incident, please contact Plivo Support. Support portal: https://support.plivo.com/hc/en-us

Read the full incident report →

Notice June 12, 2026

WhatsApp Business API — Elevated Errors and Delays

Detected by Pingoru
Jun 12, 2026, 04:30 PM UTC
Resolved
Jun 12, 2026, 05:21 PM UTC
Duration
50m
Timeline · 2 updates
  1. monitoring Jun 12, 2026, 04:30 PM UTC

    Dear Valued Customer, We are aware of elevated error rates and message delays affecting WhatsApp messaging on the Plivo platform. This is caused by an ongoing disruption with WhatsApp's Cloud API, part of a broad Meta platform outage currently affecting multiple Meta services. The issue originates upstream at Meta and is not specific to Plivo's infrastructure. Impact: Messages sent to or received from WhatsApp recipients may be delayed or fail during this window. Plivo's other services (Voice, SMS, Verify) are operating normally. We are monitoring Meta's recovery and will post another update within 60 minutes, or sooner if the situation changes. If you have any questions or concerns regarding this incident, please contact Plivo Support. Support portal: https://support.plivo.com/hc/en-us

  2. resolved Jun 12, 2026, 05:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 12, 2026

Intermittent Outbound call failures in India region for 9180 series

Detected by Pingoru
Jun 12, 2026, 05:21 AM UTC
Resolved
Jun 12, 2026, 09:13 AM UTC
Duration
3h 52m
Affected: PSTN Calls
Timeline · 2 updates
  1. investigating Jun 12, 2026, 05:21 AM UTC

    Dear Valued Customer, We are observing intermittent outbound call failures in the India region. Calls from specific series of 9180 Caller IDs are impacted. All other services are operating normally. We are working with our carrier partner to resolve this

  2. resolved Jun 12, 2026, 09:13 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 6, 2026

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

Detected by Pingoru
Jun 06, 2026, 01:00 PM UTC
Resolved
Jun 06, 2026, 01:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Jun 08, 2026, 05:37 AM 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.

Read the full incident report →

Notice May 12, 2026

Inbound call failures in India region

Detected by Pingoru
May 12, 2026, 11:26 AM UTC
Resolved
May 12, 2026, 10:50 AM UTC
Duration
Timeline · 1 update
  1. resolved May 12, 2026, 11:26 AM UTC

    Dear Valued Customer, We recently experienced intermittent Inbound Call failures in India region. Our engineering and operations teams promptly investigated and resolved the issue. The root cause was identified, and corrective actions have been implemented to prevent recurrence. Incident Start Time: 12th May 2026 10:50 UTC Incident End Time: 12th May 2026 11:20 UTC If you have any questions or concerns regarding this incident, please contact Plivo Support. Support portal: https://support.plivo.com/hc/en-us

Read the full incident report →

Notice April 8, 2026

PHLO: Inbound call failures — sub-account numbers on main account PHLO apps

Detected by Pingoru
Apr 08, 2026, 06:30 AM UTC
Resolved
Apr 08, 2026, 06:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Apr 08, 2026, 04:36 PM UTC

    Dear Valued Customer, We observed some inbound calls to PHLO applications were not being processed successfully. This affected a specific configuration where a phone number rented to a sub-account was attached to a PHLO application owned by the parent account. A recent deployment introduced a change in the request authentication flow that did not account for this configuration. The issue has been identified and fixed. Customers using phone numbers and PHLOs directly under their main account were not impacted. If you have any questions or need further assistance, please don't hesitate to contact Plivo Support through our Support Portal(https://support.plivo.com/hc/en-us).

Read the full incident report →

Minor March 28, 2026

Missing Web hook Events for Voice Calls in India Region

Detected by Pingoru
Mar 28, 2026, 01:23 PM UTC
Resolved
Mar 28, 2026, 02:52 PM UTC
Duration
1h 29m
Affected: REST APIs and XML
Timeline · 4 updates
  1. investigating Mar 28, 2026, 01:23 PM UTC

    Some webhook events for voice calls are not being generated in the India region. We are actively investigating and working to resolve this as quickly as possible. Updates will be provided as they become available.

  2. identified Mar 28, 2026, 02:13 PM UTC

    Issue has been identified. Fix is being implemented.

  3. monitoring Mar 28, 2026, 02:46 PM UTC

    A fix has been implemented and we are monitoring the results

  4. resolved Mar 28, 2026, 02:52 PM UTC

    This incident has been resolved

Read the full incident report →

Minor February 9, 2026

Voice calls are impacted due to infrastructure issue in US region.

Detected by Pingoru
Feb 09, 2026, 02:59 PM UTC
Resolved
Feb 09, 2026, 03:59 PM UTC
Duration
1h
Affected: SIP TrunkingPSTN CallsClient Calls (Browser & Mobile)
Timeline · 4 updates
  1. investigating Feb 09, 2026, 02:59 PM UTC

    Please be advised that voice calls in the US region are currently being impacted by an infrastructure issue. We are investigating the matter alongside our infrastructure partner to resolve this as quickly as possible. We will provide further updates as they become available.

  2. investigating Feb 09, 2026, 03:14 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Feb 09, 2026, 03:41 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Feb 09, 2026, 03:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 9, 2026

Failures to retrieve CDRs in India Region

Detected by Pingoru
Feb 09, 2026, 12:25 PM UTC
Resolved
Feb 09, 2026, 12:52 PM UTC
Duration
27m
Affected: RecordingsCDR (Call Detail Records)
Timeline · 3 updates
  1. investigating Feb 09, 2026, 12:25 PM UTC

    Dear Valued Customer, We are observing failures to retrieve CDR and recordings. All other services are operating normally. Our engineers are actively working to resolve the issue and restore service. Please contact Plivo Support for any questions. Support portal: https://support.plivo.com/hc/en-us

  2. monitoring Feb 09, 2026, 12:26 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 09, 2026, 12:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 8, 2026

Service degradation - Intermittent Messaging Failures

Detected by Pingoru
Feb 08, 2026, 01:41 PM UTC
Resolved
Feb 08, 2026, 05:11 PM UTC
Duration
3h 29m
Affected: SMS APIVerify API
Timeline · 3 updates
  1. investigating Feb 08, 2026, 01:41 PM UTC

    Dear Valued Customer, We are currently experiencing intermittent message failures affecting a subset of Messaging traffic. Our engineering teams have identified the issue and are actively working to stabilize the service. Other platform services continue to operate normally. We are closely monitoring the situation and will provide further updates as progress is made. We apologize for any inconvenience caused and appreciate your patience while we work toward a resolution. If you have any questions, please get in touch with Plivo Support. Support portal: https://support.plivo.com/hc/en-us Sincerely, Plivo Team

  2. monitoring Feb 08, 2026, 02:49 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 08, 2026, 05:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical February 5, 2026

Outbound call failures in India region for 160 series

Detected by Pingoru
Feb 05, 2026, 08:39 AM UTC
Resolved
Feb 05, 2026, 01:01 PM UTC
Duration
4h 21m
Affected: PSTN Calls
Timeline · 4 updates
  1. investigating Feb 05, 2026, 08:39 AM UTC

    Dear Valued Customer, We are observing outbound call failures in the India region. Calls originating from 160 Caller IDs are impacted. All other services are operating normally. Our engineers are actively working to resolve the issue and restore service.

  2. monitoring Feb 05, 2026, 09:31 AM UTC

    The carrier has implemented a fix. Calls are working as expected. We are currently monitoring.

  3. identified Feb 05, 2026, 09:46 AM UTC

    We are observing outbound call failures in the India region. Calls originating from 160 Caller IDs are impacted. We are currently investigating.

  4. resolved Feb 05, 2026, 01:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 1, 2026

Carrier degradation India

Detected by Pingoru
Feb 01, 2026, 01:53 PM UTC
Resolved
Feb 01, 2026, 02:19 PM UTC
Duration
25m
Affected: Voice, AsiaSIP Trunking, Asia
Timeline · 3 updates
  1. investigating Feb 01, 2026, 01:53 PM UTC

    One of our carrier in India is observing minor call failures towards India phone numbers. A small percentage of phone numbers may experience call failures. We're actively working with our carrier partner to get this issue resolved as soon as possible. Please contact Plivo Support for any questions. Support portal: https://support.plivo.com

  2. investigating Feb 01, 2026, 01:54 PM UTC

    We are continuing to investigate this issue.

  3. resolved Feb 01, 2026, 02:19 PM UTC

    The carrier has resolved the issue.

Read the full incident report →

Notice February 1, 2026

Voice and Zentrunk partial outage

Detected by Pingoru
Feb 01, 2026, 11:04 AM UTC
Resolved
Feb 01, 2026, 11:31 AM UTC
Duration
27m
Affected: REST APIs and XMLSIP TrunkingPSTN CallsClient Calls (Browser & Mobile)ConferenceEndpoint calls (SIP)
Timeline · 3 updates
  1. investigating Feb 01, 2026, 11:04 AM UTC

    We are currently investigating call degradation for the Voice API and Zentrunk services.

  2. investigating Feb 01, 2026, 11:26 AM UTC

    We are continuing to investigate this issue.

  3. resolved Feb 01, 2026, 11:31 AM UTC

    We observed elevated latency for approximately 10 minutes, which may have briefly affected performance for some users. The underlying issue was identified and addressed, and the system has since returned to normal operation.

Read the full incident report →

Notice January 7, 2026

Delivery issue with outbound SMS to the US from certain 10DLC campaigns.

Detected by Pingoru
Jan 07, 2026, 08:25 AM UTC
Resolved
Jan 08, 2026, 11:01 AM UTC
Duration
1d 2h
Affected: SMS API
Timeline · 2 updates
  1. investigating Jan 07, 2026, 08:25 AM UTC

    We are currently investigating reports of delivery issues affecting a subset of 10DLC traffic. Impacted customers may observe messages marked as DELIVERED in logs, even though these messages may not have been successfully delivered to the handset. This issue has been escalated to our carrier partners, and we are awaiting an update on the routing path.

  2. resolved Jan 08, 2026, 11:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 29, 2025

Intermittent Message Failures

Detected by Pingoru
Oct 29, 2025, 02:33 PM UTC
Resolved
Oct 29, 2025, 02:33 PM UTC
Duration
Affected: SMS APIVerify API
Timeline · 1 update
  1. resolved Oct 29, 2025, 02:33 PM UTC

    We experienced intermittent SMS message failures between 13:50 UTC and 13:59 UTC on 29th Oct 2025 due to an underlying infrastructure failure. The issue was auto-recovered, and all systems have since stabilized. Message processing has fully recovered, and the platform is operating normally. Incident Start Time: 29th Oct 2025 13:50 UTC Incident End Time: 29th Oct 2025 13:59 UTC

Read the full incident report →

Major October 29, 2025

Outbound call failures in India Bangalore Region

Detected by Pingoru
Oct 29, 2025, 03:49 AM UTC
Resolved
Oct 29, 2025, 06:17 AM UTC
Duration
2h 28m
Affected: PSTN Calls
Timeline · 3 updates
  1. investigating Oct 29, 2025, 03:49 AM UTC

    Dear Valued Customer, We are observing outbound call failures in the India region. Calls originating from 080 Caller IDs are impacted. All other services are operating normally. Our engineers are actively working to resolve the issue and restore service.

  2. monitoring Oct 29, 2025, 06:07 AM UTC

    The carrier has implemented a fix. Calls are working as expected. We are currently monitoring.

  3. resolved Oct 29, 2025, 06:17 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 26, 2025

Intermittent SMS failures in India Region

Detected by Pingoru
Oct 26, 2025, 03:35 PM UTC
Resolved
Oct 27, 2025, 04:13 AM UTC
Duration
12h 38m
Affected: SMS, Asia
Timeline · 3 updates
  1. identified Oct 26, 2025, 03:35 PM UTC

    Dear Valued Customer, We are currently experiencing intermittent issues impacting SMS in India Region. Our Internal team is actively investigating and working to resolve the issue as quickly as possible. If you have any questions, please get in touch with Plivo Support. Support portal: https://support.plivo.com/hc/en-us

  2. monitoring Oct 26, 2025, 04:23 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Oct 27, 2025, 04:13 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 7, 2025

Intermittent Message failures in India Region

Detected by Pingoru
Oct 07, 2025, 07:19 AM UTC
Resolved
Oct 06, 2025, 02:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Oct 07, 2025, 07:19 AM UTC

    Dear Valued Customer, We recently experienced intermittent SMS failures. Our engineering and operations teams promptly investigated and resolved the issue. The root cause was identified, and corrective actions have been implemented to prevent recurrence. Incident Start Time: 6th Oct 2025 14:30 UTC Incident End Time: 7th Oct 2025 03:30 UTC If you have any questions or concerns regarding this incident, please contact Plivo Support. Support portal: https://support.plivo.com/hc/en-us

Read the full incident report →

Minor July 31, 2025

Intermittent Call failures in India Region

Detected by Pingoru
Jul 31, 2025, 02:24 PM UTC
Resolved
Jul 31, 2025, 02:39 PM UTC
Duration
14m
Affected: PSTN Calls
Timeline · 3 updates
  1. investigating Jul 31, 2025, 02:24 PM UTC

    Dear Valued Customer, We are observing partial/intermittent Call failures in the India region . Calls originating from International Caller IDs towards India were not affected. All other services are operating normally. Our engineers are actively working to resolve the issue and restore service. Incident Start Time: 31st July 2025 06:25 IST Incident End Time: 31st July 2025 07:25 IST Please contact Plivo Support for any questions. Support portal: https://support.plivo.com/hc/en-us

  2. monitoring Jul 31, 2025, 02:33 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jul 31, 2025, 02:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 20, 2025

Intermittent Message failures

Detected by Pingoru
Jun 20, 2025, 06:09 PM UTC
Resolved
Jun 20, 2025, 08:48 PM UTC
Duration
2h 38m
Timeline · 3 updates
  1. investigating Jun 20, 2025, 06:09 PM UTC

    Dear Valued Customer, We are currently experiencing intermittent issues impacting SMS and Verify requests. Our engineering team is actively investigating and working to resolve the issue as quickly as possible. If you have any questions, please get in touch with Plivo Support. Support portal: https://support.plivo.com/hc/en-us

  2. monitoring Jun 20, 2025, 08:07 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 20, 2025, 08:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 19, 2025

Inbound Call failures in the India region

Detected by Pingoru
Jun 19, 2025, 01:21 PM UTC
Resolved
Jun 19, 2025, 11:45 AM UTC
Duration
Timeline · 1 update
  1. resolved Jun 19, 2025, 01:21 PM UTC

    Dear Valued Customer, We recently experienced inbound call failures affecting users in the India region during the time window specified below. The issue has since been resolved, and all services are currently operating normally. Incident Start Time: 19th June 2025 11:45 UTC Incident End Time: 19th June 2025 12:50 UTC If you have any questions or concerns regarding this incident, please contact Plivo Support. Support portal: https://support.plivo.com/hc/en-us

Read the full incident report →

Notice June 5, 2025

Intermittent Outbound Call failures in the India region

Detected by Pingoru
Jun 05, 2025, 06:38 AM UTC
Resolved
Jun 05, 2025, 05:25 AM UTC
Duration
Timeline · 1 update
  1. resolved Jun 05, 2025, 06:38 AM UTC

    Dear Valued Customer, We recently experienced intermittent outbound call failures affecting users in the India region during the time window specified below. The issue has since been resolved, and all services are currently operating normally. Incident Start Time: 5th June 2025 05:25 UTC Incident End Time: 5th June 2025 05:50 UTC If you have any questions or concerns regarding this incident, please contact Plivo Support. Support portal: https://support.plivo.com/hc/en-us

Read the full incident report →

Minor May 20, 2025

Intermittent SMS & MMS failure

Detected by Pingoru
May 20, 2025, 07:30 AM UTC
Resolved
May 20, 2025, 07:30 AM UTC
Duration
Timeline · 1 update
  1. resolved May 20, 2025, 07:54 AM UTC

    Dear Valued Customer, We recently experienced intermittent SMS and MMS failures. Our engineering and operations teams promptly investigated and resolved the issue. The root cause was identified, and corrective actions have been implemented to prevent recurrence. Incident Start Time: 20th May 2025 07:30 UTC Incident End Time: 20th May 2025 07:50 UTC If you have any questions or concerns regarding this incident, please contact Plivo Support. Support portal: https://support.plivo.com/hc/en-us

Read the full incident report →

Minor May 13, 2025

Intermittent Call failures in the Mumbai region

Detected by Pingoru
May 13, 2025, 02:41 PM UTC
Resolved
May 14, 2025, 12:45 PM UTC
Duration
22h 3m
Affected: PSTN Calls
Timeline · 3 updates
  1. investigating May 13, 2025, 02:41 PM UTC

    Dear Valued Customer, We observed partial/intermittent Call failures in the India region towards Mumbai phone numbers. Calls originating from International Caller IDs towards India were not affected. All other services are operating normally. We're actively working with our carrier partner to get this issue resolved as soon as possible. Please contact Plivo Support for any questions. Support portal: https://support.plivo.com/hc/en-us

  2. monitoring May 13, 2025, 03:59 PM UTC

    We will continue to monitor the situation and provide another update as soon as possible.

  3. resolved May 14, 2025, 12:45 PM UTC

    This incident has been resolved.

Read the full incident report →