58 Plivo incidents · 2025年1月 — official updates, affected components, duration and resolution details.
亲爱的贵客 我们目前观察着一个断断续续的问题, 即一些声音呼叫没有触发状态回调, 电话处理本身没有受到影响,而且电话正常连接和完成。 我们已查明这一原因是我们媒体服务器子集中的一个已退化的事件处理部分,并正在积极进行补救。 影响是断断续续的,大多数电话继续正常收到webhoks.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
亲爱的贵客 我们在印度地区看到外来的呼叫失败。 我们的小组正在调查这个问题.
我们已经与我们的云服务供应商确定了这一问题。 我们的小组正同他们密切合作来解决这个问题,一旦获得更多信息,我们将提供另一个最新情况.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
亲爱的贵客 目前,我们观察到断断续续的呼叫失败,影响到进出印度的呼叫。 我们的团队正同我们的航空伙伴积极合作,以查明根源并尽快恢复服务。 我们将在今后30分钟内提供下一次最新情况.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
亲爱的贵客 我们已查明一个问题, 造成来自免费电话号码(美国和加拿大)的MMS消息失效。 失败的原因是与上游承运人伙伴的连通性问题,受影响的信息未能交付。 通过其他路线发送的短信和短信没有受到影响。 我们的团队正积极与航母合作伙伴接触,以恢复服务. 我们不久将进一步介绍最新情况。 如果您对此事有任何问题或担忧,请联系Plivo Support。 支助门户:https://support.plivo.com/hc/en-us
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
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
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Dear Valued Customer, We are experiencing call failures in the India and US region.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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
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
This incident has been resolved.
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
This incident has been resolved.
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.
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
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).
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.
Issue has been identified. Fix is being implemented.
A fix has been implemented and we are monitoring the results
This incident has been resolved
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.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
The carrier has implemented a fix. Calls are working as expected. We are currently monitoring.
We are observing outbound call failures in the India region. Calls originating from 160 Caller IDs are impacted. We are currently investigating.
This incident has been resolved.
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
We are continuing to investigate this issue.
The carrier has resolved the issue.
We are currently investigating call degradation for the Voice API and Zentrunk services.
We are continuing to investigate this issue.
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.