Historial de interrupciones de Plivo

1. August 25, 2026 at 7:25 AM UTCidentified

   Queridos Clientes Valorados, Actualmente estamos observando un problema intermitente donde un subconjunto de llamadas de voz no están activando los callbacks de estado, incluyendo los eventos de anillo, ahorcamiento y llamada-status webhook. El procesamiento de llamadas en sí mismo no es afectado, y las llamadas se conectan y completan normalmente. Hemos identificado la causa como un componente de procesamiento de eventos degradado en un subconjunto de nuestros servidores multimedia y estamos trabajando activamente en la rehabilitación. El impacto es intermitente, y la mayoría de las llamadas siguen recibiendo webhooks normalmente.

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

   Se ha aplicado una solución y estamos monitoreando los resultados.

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

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 31, 2026 at 5:01 PM UTCinvestigating

   Querido valioso cliente, Estamos observando fallos de llamadas en la región de la India. Nuestro equipo está investigando el tema.

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

   Hemos identificado el problema con nuestro proveedor de servicios en la nube. Nuestro equipo está colaborando estrechamente con ellos para resolver el problema, y proporcionaremos otra actualización tan pronto como se disponga de más información.

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

   Se ha aplicado una solución y estamos monitoreando los resultados.

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

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 20, 2026 at 6:05 AM UTCinvestigating

   Queridos Clientes Valorados, Actualmente estamos observando fallos intermitentes de llamadas que afectan tanto a llamadas inbound como a la India. Nuestro equipo está trabajando activamente con nuestro socio portador para identificar la causa raíz y restaurar el servicio lo más rápido posible. Proporcionaremos nuestra próxima actualización en los próximos 30 minutos.

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

   Se ha aplicado una solución y estamos monitoreando los resultados.

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

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 11, 2026 at 7:47 AM UTCinvestigating

   Querido valioso cliente, Hemos identificado un problema causando fracasos para mensajes de MMS de salida enviados desde números libres de llamadas Toll (US & Canadá). Los fallos se deben a un problema de conectividad con un socio de transportista de corriente avanzada, y los mensajes afectados no se entregan. El tráfico de SMS y MMS enviados sobre otras rutas no son impactados. Nuestro equipo está activamente comprometido con el socio portador para restaurar el servicio. Compartiremos una nueva actualización en breve. Si tiene alguna pregunta o preocupación respecto a este incidente, póngase en contacto con Plivo Support. Portal de apoyo: https://support.plivo.com/hc/en-us

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

   Se ha aplicado una solución y estamos monitoreando los resultados.

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

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

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.

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.

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.

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

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.

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.

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.

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

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

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

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.

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.

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.

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.

1. February 1, 2026 at 1:53 PM 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. February 1, 2026 at 1:54 PM UTCinvestigating

   We are continuing to investigate this issue.

3. February 1, 2026 at 2:19 PM UTCresolved

   The carrier has resolved the issue.

1. February 1, 2026 at 11:04 AM UTCinvestigating

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

2. February 1, 2026 at 11:26 AM UTCinvestigating

   We are continuing to investigate this issue.

3. February 1, 2026 at 11:31 AM 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.