Vendor record
Plivo
Checked
Front door check counts and Plivo’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented Plivo endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- api.plivo.com
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Plivo product, region or your app worked.
How we count front door checksPlivo says
Incident posts from Plivo’s status page, with its titles, impact levels and times. They say what Plivo chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
1
incidents Plivo posted, last 7 days
Most recent records · all dates
Intermittent Call failures towards India
Not specifiedPlivo’s postStarted, per Plivo
Closed in our record(31m)
Intermittent Call failures towards India
Not specifiedPlivo’s postStarted, per Plivo
Closed in our record(38m)
Voice Call Webhook Delivery Degradation
Not specifiedPlivo’s postStarted, per Plivo
Closed in our record(6h 54m)
Call failures towards India
Not specifiedPlivo’s postStarted, per Plivo
Closed in our record(10h 38m)
Intermittent Call failures towards India
Not specifiedPlivo’s postStarted, per Plivo
Closed in our record(3h 13m)
7 older records
Outbound MMS Failures on Toll-Free Numbers (US & Canada)
MajorPlivo’s postStarted, per Plivo
Closed in our record(2h 12m)
Outbound Call Failures
Not specifiedPlivo’s postStarted, per Plivo
Closed in our record(2h 50m)
Outbound Call Failures for Specific 9180 Caller IDs
MajorPlivo’s postStarted, per Plivo
Closed in our record(1h 49m)
Call Failures in US and India regions
MajorPlivo’s postStarted, per Plivo
Closed in our record(1h)
WhatsApp Business API — Elevated Errors and Delays
Not specifiedPlivo’s postStarted, per Plivo
Closed in our record(59m)
Intermittent Outbound call failures in India region for 9180 series
MinorPlivo’s postStarted, per Plivo
Closed in our record(3h 59m)
Missing Web hook Events for Voice Calls in India Region
MinorPlivo’s postStarted, per Plivo
Closed in our record(1h 39m)
Your code, your dependencies
See which of your code paths call Plivo
Connect GitHub or GitLab to find where your public or private repository uses Plivo. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Plivo status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Plivo currently down?
Plivo's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Plivo last have an outage?
The most recent closed incident record began 6 days ago and spans 31 minutes. The vendor reported an incident. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Plivo?
No. CheckUpstream checks Plivo’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor Plivo in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Plivo?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.