Is Plivo down?
Vendor reports no incidentWhat Plivo reports
Plivo reports no incident on its status page.
As of the last successful poll, 2026-11-05 14:59 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingchecked 2 minutes ago
Our checks of Plivo pass from all 10 regions we check.
As of Nov 5, 2026, 3:08 PM UTC, RealUptime's checks of Plivo passed in all 10 regions that returned a reading.
Plivo reports: All systems operational (“All Systems Operational”)
Plivo's own component breakdown, as they publish it
- Longcode SMS, USA & CanadaOperational
- REST APIs and XMLOperational
- SIP TrunkingOperational
- SIP Trunking, North AmericaOperational
- SMS APIOperational
- Voice, North AmericaOperational
- MMS APIOperational
- PSTN CallsOperational
- SIP Trunking, South AmericaOperational
- Shortcode SMS, USA & CanadaOperational
- Voice, South AmericaOperational
- Client Calls (Browser & Mobile)Operational
- Powerpack SMSOperational
- SIP Trunking, EuropeOperational
- Toll-free SMS, USA & CanadaOperational
- Voice, EuropeOperational
- MMS, USA & CanadaOperational
- Powerpack MMSOperational
- SIP Trunking, AsiaOperational
- Voice, AsiaOperational
- ConferenceOperational
- SIP Trunking, AfricaOperational
- SMS, Mexico & South AmericaOperational
- Verify APIOperational
- Voice, AfricaOperational
- RecordingsOperational
- SIP Trunking, OceaniaOperational
- SMS, AsiaOperational
- Voice, OceaniaOperational
- ConsoleOperational
- SMS, EuropeOperational
- Text-to-SpeechOperational
- FlowOperational
- SMS, AfricaOperational
- TranscriptionOperational
- Account & Phone Number APIsOperational
- SMS, OceaniaOperational
- Speech RecognitionOperational
- Endpoint calls (SIP)Operational
- Number Lookup APIOperational
- BYOCOperational
- Payments and BillingOperational
- Answering Machine detectionOperational
- Support Ticketing SystemOperational
- CDR (Call Detail Records)Operational
These are Plivo's components, named and scored by Plivo. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.
This is Plivo's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.
Plivo response time, by region
Check your own site while you wait on Plivo
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Plivo. It cannot diagnose Plivo's own systems.
What we measured, function by function
Plivo answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- DocumentationUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
Email me when Plivo reports an incident on its status page, and again when it reports it resolved.
Get an email when Plivo reports an incident
Email me when Plivo reports an incident on its status page, and again when it reports it resolved. No account, no card.
What our checks show, and what people reported
- North AmericaChecks passingUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 699msstatus code: 404checked: Nov 5, 2026, 2:49 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Plivo normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 1421msstatus code: 404checked: Nov 5, 2026, 2:42 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Plivo normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralChecks passinglatency: 1220msstatus code: 404checked: Nov 5, 2026, 2:45 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Plivo normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaChecks passinglatency: 502msstatus code: 404checked: Nov 5, 2026, 3:00 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Plivo normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaChecks passinglatency: 1009msstatus code: 404checked: Nov 5, 2026, 2:24 PM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Plivo normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropeChecks passingEurope, UK
- EuropeChecks passinglatency: 976msstatus code: 404checked: Nov 5, 2026, 2:46 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Plivo normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKChecks passinglatency: 613msstatus code: 404checked: Nov 5, 2026, 2:19 PM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Plivo normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificChecks passingAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 2627msstatus code: 404checked: Nov 5, 2026, 3:08 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Plivo normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaChecks passinglatency: 436msstatus code: 404checked: Nov 5, 2026, 2:25 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Plivo normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaChecks passinglatency: 2089msstatus code: 404checked: Nov 5, 2026, 2:31 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Plivo normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using Plivo, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Plivo yet, which is not evidence that nothing is wrong.
Recent probe events
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Plivo since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for Plivo covering any window you pick, with our check readings and Plivo's own claim at the time, side by side.
Full check history for Plivo: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.
Monitor your own site the same way
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter
Put this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/plivo)<a href="https://realuptime.io/outages/plivo"><img src="https://realuptime.io/outages/plivo/badge.svg?days=30" alt="Plivo uptime by RealUptime's checks" height="20"></a>Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.
To cite this page: RealUptime, "Is Plivo down?", https://realuptime.io/outages/plivo. The readings change with every check, so give the date you read them.
What we check
What our check can and cannot see
A pass means the service's servers answered our request with the error they give a request that carries no account or valid input. It does not show that sign-in works or that any real request succeeds.
Host checked: api.plivo.com