Historia awarii Plivo

1. 25 sierpnia 2026 07:25 UTCidentified

   Drodzy klienci, Obecnie obserwujemy przerywany problem, w którym podzbiór połączeń głosowych nie uruchamia połączeń ze statusem, w tym połączeń telefonicznych, rozłączeń i połączeń ze statusem. Samo przetwarzanie połączeń nie ma wpływu, a połączenia łączą się i kończą normalnie. Zidentyfikowaliśmy przyczynę jako zdegradowany element przetwarzania zdarzeń na naszym serwerze medialnym i aktywnie pracujemy nad rekultywacją. Uderzenie jest przerywane, a większość połączeń nadal otrzymywać haki internetowe normalnie.

2. 25 sierpnia 2026 07:41 UTCmonitoring

   Wprowadzono rozwiązanie i monitorujemy wyniki.

3. 25 sierpnia 2026 14:16 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 31 lipca 2026 17:01 UTCinvestigating

   Szanowny Kliencie, Obserwujemy wypadki wywoławcze w regionie Indii. Nasz zespół bada sprawę.

2. 31 lipca 2026 17:45 UTCidentified

   Zidentyfikowaliśmy problem z naszym dostawcą usług w chmurze. Nasz zespół ściśle z nimi współpracuje, aby rozwiązać ten problem, a my dostarczymy kolejną aktualizację, jak tylko więcej informacji stanie się dostępne.

3. 31 lipca 2026 18:36 UTCmonitoring

   Wprowadzono rozwiązanie i monitorujemy wyniki.

4. 1 sierpnia 2026 03:37 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 20 lipca 2026 06:05 UTCinvestigating

   Drodzy klienci, Obecnie obserwujemy przerywane niepowodzenia połączeń wpływające zarówno na połączenia przychodzące, jak i wychodzące do Indii. Nasz zespół aktywnie współpracuje z naszym partnerem nośnikiem, aby jak najszybciej zidentyfikować przyczynę i przywrócić usługę. Dostarczymy naszą następną aktualizację w ciągu najbliższych 30 minut.

2. 20 lipca 2026 06:15 UTCmonitoring

   Wprowadzono rozwiązanie i monitorujemy wyniki.

3. 20 lipca 2026 09:15 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 11 lipca 2026 07:47 UTCinvestigating

   Szanowny Kliencie, Zidentyfikowaliśmy problem powodujący awarię wiadomości MMS wysyłanych z numeru Toll- Free (USA & Kanada). Usterki te wynikają z problemów związanych z połączeniem z dostawcą wyższego szczebla, a komunikaty, których to dotyczy, nie są dostarczane. Ruch SMS i MMS wysyłane na inne trasy nie mają wpływu. Nasz zespół aktywnie współpracuje z partnerem przewoźnika w celu przywrócenia usługi. Wkrótce podzielimy się dalszymi informacjami. Jeśli masz jakieś pytania lub wątpliwości dotyczące tego incydentu, skontaktuj się z Plivo Support. Portal wsparcia: https: / / support.plivo.com / hc / en- us

2. 11 lipca 2026 09:32 UTCmonitoring

   Wprowadzono rozwiązanie i monitorujemy wyniki.

3. 11 lipca 2026 09:57 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 2 lipca 2026 13:40 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. 2 lipca 2026 13:45 UTCmonitoring

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

3. 2 lipca 2026 16:29 UTCresolved

   This incident has been resolved.

1. 30 czerwca 2026 08:00 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. 30 czerwca 2026 09:38 UTCmonitoring

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

3. 30 czerwca 2026 09:45 UTCresolved

   This incident has been resolved.

1. 19 czerwca 2026 13:01 UTCinvestigating

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

2. 19 czerwca 2026 13:27 UTCmonitoring

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

3. 19 czerwca 2026 13:57 UTCresolved

   This incident has been resolved.

1. 15 czerwca 2026 07:26 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

1. 12 czerwca 2026 16:30 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. 12 czerwca 2026 17:21 UTCresolved

   This incident has been resolved.

1. 12 czerwca 2026 05:21 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. 12 czerwca 2026 09:13 UTCresolved

   This incident has been resolved.

1. 8 czerwca 2026 05:37 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.

1. 12 maja 2026 11:26 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

1. 8 kwietnia 2026 16:36 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).

1. 28 marca 2026 13:23 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. 28 marca 2026 14:13 UTCidentified

   Issue has been identified. Fix is being implemented.

3. 28 marca 2026 14:46 UTCmonitoring

   A fix has been implemented and we are monitoring the results

4. 28 marca 2026 14:52 UTCresolved

   This incident has been resolved

1. 9 lutego 2026 14:59 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. 9 lutego 2026 15:14 UTCinvestigating

   We are continuing to investigate this issue.

3. 9 lutego 2026 15:41 UTCmonitoring

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

4. 9 lutego 2026 15:59 UTCresolved

   This incident has been resolved.

1. 9 lutego 2026 12:25 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. 9 lutego 2026 12:26 UTCmonitoring

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

3. 9 lutego 2026 12:52 UTCresolved

   This incident has been resolved.

1. 8 lutego 2026 13:41 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. 8 lutego 2026 14:49 UTCmonitoring

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

3. 8 lutego 2026 17:11 UTCresolved

   This incident has been resolved.

1. 5 lutego 2026 08:39 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. 5 lutego 2026 09:31 UTCmonitoring

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

3. 5 lutego 2026 09:46 UTCidentified

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

4. 5 lutego 2026 13:01 UTCresolved

   This incident has been resolved.

1. 1 lutego 2026 13:53 UTCinvestigating

   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. 1 lutego 2026 13:54 UTCinvestigating

   We are continuing to investigate this issue.

3. 1 lutego 2026 14:19 UTCresolved

   The carrier has resolved the issue.

1. 1 lutego 2026 11:04 UTCinvestigating

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

2. 1 lutego 2026 11:26 UTCinvestigating

   We are continuing to investigate this issue.

3. 1 lutego 2026 11:31 UTCresolved

   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.