Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Plivo outage history

    60 recorded Plivo incidents since January 2025, with official updates, affected components, duration and resolution information.

    Back to current status

    Intermittent Call failures towards India

    Started October 10, 2026 at 8:09 AM UTC · 26m

    Pending
    1. October 10, 2026 at 8:09 AM UTCinvestigating

      Dear Valued Customers, We are currently observing intermittent call failures affecting outbound calls to India. Our team is actively working with our carrier partner to identify the root cause and restore service as quickly as possible. We will provide our next update within the next 30 minutes.

    2. October 10, 2026 at 8:25 AM UTCidentified

      The issue has been identified and a fix is being implemented.

    3. October 10, 2026 at 8:25 AM UTCmonitoring

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

    4. October 10, 2026 at 8:34 AM UTCresolved

      This incident has been resolved.

    Intermittent Call failures towards India

    Started September 11, 2026 at 6:02 AM UTC · 33m

    Pending
    1. September 11, 2026 at 6:02 AM UTCidentified

      Dear Valued Customers, We are currently observing intermittent call failures affecting both inbound and outbound calls to India. Our team is actively working with our carrier partner to identify the root cause and restore service as quickly as possible. We will provide our next update within the next 30 minutes.

    2. September 11, 2026 at 6:27 AM UTCmonitoring

      carrier partner fixed the issue and we are monitoring the results.

    3. September 11, 2026 at 6:35 AM UTCresolved

      This incident has been resolved

    Voice Call Webhook Delivery Degradation

    Started August 25, 2026 at 7:25 AM UTC · 6h 51m

    Pending
    Affected components
    PSTN CallsREST APIs and XML
    1. August 25, 2026 at 7:25 AM UTCidentified

      Dear Valued Customers, We are currently observing an intermittent issue where a subset of voice calls are not triggering status callbacks, including ringing, hangup, and call-status webhook events. Call processing itself is unaffected, and calls are connecting and completing normally. We have identified the cause as a degraded event-processing component on a subset of our media servers and are actively working on remediation. The impact is intermittent, and most calls continue to receive webhooks normally.

    2. August 25, 2026 at 7:41 AM UTCmonitoring

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

    3. August 25, 2026 at 2:16 PM UTCresolved

      This incident has been resolved.

    Call failures towards India

    Started July 31, 2026 at 5:01 PM UTC · 10h 36m

    Pending
    Affected components
    PSTN CallsREST APIs and XML
    1. July 31, 2026 at 5:01 PM UTCinvestigating

      Dear Valued Customer, We are observing outbound call failures in the India region. Our team is investigating the issue.

    2. July 31, 2026 at 5:45 PM UTCidentified

      We have identified the issue with our cloud service provider. Our team is working closely with them to resolve the issue, and we will provide another update as soon as more information becomes available.

    3. July 31, 2026 at 6:36 PM UTCmonitoring

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

    4. August 1, 2026 at 3:37 AM UTCresolved

      This incident has been resolved.

    Intermittent Call failures towards India

    Started July 20, 2026 at 6:05 AM UTC · 3h 10m

    Pending
    Affected components
    PSTN CallsREST APIs and XML
    1. July 20, 2026 at 6:05 AM UTCinvestigating

      Dear Valued Customers, We are currently observing intermittent call failures affecting both inbound and outbound calls to India. Our team is actively working with our carrier partner to identify the root cause and restore service as quickly as possible. We will provide our next update within the next 30 minutes.

    2. July 20, 2026 at 6:15 AM UTCmonitoring

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

    3. July 20, 2026 at 9:15 AM UTCresolved

      This incident has been resolved.

    Outbound MMS Failures on Toll-Free Numbers (US & Canada)

    Started July 11, 2026 at 7:47 AM UTC · 2h 10m

    OutageMajor incident
    Affected components
    MMS API
    1. July 11, 2026 at 7:47 AM UTCinvestigating

      Dear Valued Customer, We have identified an issue causing failures for outbound MMS messages sent from Toll-Free numbers (US & Canada). The failures are due to a connectivity issue with an upstream carrier partner, and affected messages are failing to be delivered. SMS traffic and MMS sent over other routes are not impacted. Our team is actively engaged with the carrier partner to restore service. We will share a further update shortly. If you have any questions or concerns regarding this incident, please contact Plivo Support. Support portal: https://support.plivo.com/hc/en-us

    2. July 11, 2026 at 9:32 AM UTCmonitoring

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

    3. July 11, 2026 at 9:57 AM UTCresolved

      This incident has been resolved.

    Outbound Call Failures

    Started July 2, 2026 at 1:40 PM UTC · 2h 49m

    Pending
    Affected components
    ConferenceTranscriptionText-to-SpeechPSTN CallsEndpoint calls (SIP)REST APIs and XMLSpeech RecognitionRecordingsAnswering Machine detectionBYOCClient Calls (Browser & Mobile)
    1. July 2, 2026 at 1:40 PM UTCinvestigating

      Dear Valued Customer, We are currently experiencing a full outbound call outage. Our team is actively engaged and working to identify the root cause and restore service as quickly as possible. We will share our next update within 30 minutes, or sooner if there is a material change. For urgent concerns, please contact Plivo Support: https://support.plivo.com/hc/en-us

    2. July 2, 2026 at 1:45 PM UTCmonitoring

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

    3. July 2, 2026 at 4:29 PM UTCresolved

      This incident has been resolved.

    Outbound Call Failures for Specific 9180 Caller IDs

    Started June 30, 2026 at 8:00 AM UTC · 1h 44m

    OutageMajor incident
    Affected components
    Voice, Asia
    1. June 30, 2026 at 8:00 AM UTCinvestigating

      Dear Valued Customer, We are observing outbound call failures in the India region. Calls from 9180 caller IDs are impacted. All other services are operating normally. We are working with out carrier partners to restore the service.

    2. June 30, 2026 at 9:38 AM UTCmonitoring

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

    3. June 30, 2026 at 9:45 AM UTCresolved

      This incident has been resolved.

    Call Failures in US and India regions

    Started June 19, 2026 at 1:01 PM UTC · 56m

    OutageMajor incident
    Affected components
    PSTN CallsEndpoint calls (SIP)REST APIs and XMLSIP TrunkingClient Calls (Browser & Mobile)
    1. June 19, 2026 at 1:01 PM UTCinvestigating

      Dear Valued Customer, We are experiencing call failures in the India and US region.

    2. June 19, 2026 at 1:27 PM UTCmonitoring

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

    3. June 19, 2026 at 1:57 PM UTCresolved

      This incident has been resolved.

    Call failures for 911600 series numbers in India region

    Started June 15, 2026 at 6:00 AM UTC · 0m

    Pending
    1. June 15, 2026 at 7:26 AM UTCresolved

      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

    WhatsApp Business API — Elevated Errors and Delays

    Started June 12, 2026 at 4:30 PM UTC · 51m

    Pending
    1. June 12, 2026 at 4:30 PM UTCmonitoring

      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. June 12, 2026 at 5:21 PM UTCresolved

      This incident has been resolved.

    Intermittent Outbound call failures in India region for 9180 series

    Started June 12, 2026 at 5:21 AM UTC · 3h 52m

    IssuesMinor incident
    Affected components
    PSTN Calls
    1. June 12, 2026 at 5:21 AM UTCinvestigating

      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. June 12, 2026 at 9:13 AM UTCresolved

      This incident has been resolved.

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

    Started June 6, 2026 at 1:00 PM UTC · 0m

    Pending
    1. June 8, 2026 at 5:37 AM UTCresolved

      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.

    Inbound call failures in India region

    Started May 12, 2026 at 10:50 AM UTC · 0m

    Pending
    1. May 12, 2026 at 11:26 AM UTCresolved

      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

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

    Started April 8, 2026 at 6:30 AM UTC · 0m

    Pending
    1. April 8, 2026 at 4:36 PM UTCresolved

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

    Missing Web hook Events for Voice Calls in India Region

    Started March 28, 2026 at 1:23 PM UTC · 1h 30m

    IssuesMinor incident
    Affected components
    REST APIs and XML
    1. March 28, 2026 at 1:23 PM UTCinvestigating

      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. March 28, 2026 at 2:13 PM UTCidentified

      Issue has been identified. Fix is being implemented.

    3. March 28, 2026 at 2:46 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results

    4. March 28, 2026 at 2:52 PM UTCresolved

      This incident has been resolved

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

    Started February 9, 2026 at 2:59 PM UTC · 1h 0m

    IssuesMinor incident
    Affected components
    PSTN CallsSIP TrunkingClient Calls (Browser & Mobile)
    1. February 9, 2026 at 2:59 PM UTCinvestigating

      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. February 9, 2026 at 3:14 PM UTCinvestigating

      We are continuing to investigate this issue.

    3. February 9, 2026 at 3:41 PM UTCmonitoring

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

    4. February 9, 2026 at 3:59 PM UTCresolved

      This incident has been resolved.

    Failures to retrieve CDRs in India Region

    Started February 9, 2026 at 12:25 PM UTC · 28m

    IssuesMinor incident
    Affected components
    CDR (Call Detail Records)Recordings
    1. February 9, 2026 at 12:25 PM UTCinvestigating

      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. February 9, 2026 at 12:26 PM UTCmonitoring

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

    3. February 9, 2026 at 12:52 PM UTCresolved

      This incident has been resolved.

    Service degradation - Intermittent Messaging Failures

    Started February 8, 2026 at 1:41 PM UTC · 3h 30m

    Pending
    Affected components
    Verify APISMS API
    1. February 8, 2026 at 1:41 PM UTCinvestigating

      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. February 8, 2026 at 2:49 PM UTCmonitoring

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

    3. February 8, 2026 at 5:11 PM UTCresolved

      This incident has been resolved.

    Outbound call failures in India region for 160 series

    Started February 5, 2026 at 8:39 AM UTC · 4h 21m

    OutageCritical incident
    Affected components
    PSTN Calls
    1. February 5, 2026 at 8:39 AM UTCinvestigating

      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. February 5, 2026 at 9:31 AM UTCmonitoring

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

    3. February 5, 2026 at 9:46 AM UTCidentified

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

    4. February 5, 2026 at 1:01 PM UTCresolved

      This incident has been resolved.