Is Plivo Down?

No — Plivo is up

Reachable from all 8 checked regions

Average response time: 348ms

Last checked 5 hours ago · checks run every 6 hours

Official status page: https://status.plivo.com

Plivo uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

336ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 55 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

55-day clean streak

Sep 14 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

198ms

DNS 31ms TCP 2ms TLS 10ms TTFB 191ms

arn

266ms

DNS 78ms TCP 1ms TLS 10ms TTFB 255ms

cdg

233ms

DNS 33ms TCP 1ms TLS 7ms TTFB 229ms

dfw

222ms

DNS 70ms TCP 1ms TLS 5ms TTFB 218ms

ewr

466ms

DNS 201ms TCP 2ms TLS 7ms TTFB 445ms

sjc

179ms

DNS 86ms TCP 2ms TLS 7ms TTFB 174ms

syd

427ms

DNS 98ms TCP 1ms TLS 7ms TTFB 425ms

yyz

798ms

DNS 137ms TCP 8ms TLS 16ms TTFB 687ms

What Plivo does

Plivo is a cloud communications platform providing SMS, MMS, voice calling and SIP trunking through APIs, alongside no-code tools for building voice agents. Applications use it to send verification codes, notifications and marketing messages, and to place or receive calls. When it fails, the visible symptom is usually a login that never completes because the one-time code never arrives.

What an outage looks like

One-time passcodes and alerts are accepted by the API but never reach handsets, so sign-ups and logins stall for end users. Calls fail to connect or drop mid-conversation. Delivery receipts stop arriving, leaving messages stuck in a sent state. Because Plivo reports per region, traffic to one continent can fail while another is unaffected, which makes an outage look intermittent.

What to do about it

status.plivo.com is unusually detailed: it reports SMS, Voice and SIP Trunking separately for North America, South America, Europe, Asia, Africa and Oceania, plus per-route rows for longcode, shortcode and toll-free traffic in the USA and Canada. Match the failing route to its region row before assuming a platform-wide problem. For verification codes, offer an email fallback instead of letting users retry.

Is it down for everyone, or just you?

If this page says Plivo is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Plivo outage FAQ

Messages send successfully but never arrive. Is Plivo down?

Check the region row for the destination rather than the overall banner. Plivo reports SMS delivery separately for North America, South America, Europe, Asia, Africa and Oceania, so traffic to one region can fail while the rest is healthy. An accepted API call means Plivo queued the message, not that a carrier delivered it.

Does a Plivo outage affect voice and SMS together?

Often not. The status page lists SMS API, MMS API and the voice products as distinct components, and then breaks voice down by region again. Voice can be degraded in Europe while SMS to the same countries is fine. Read the specific component and region combination your traffic uses instead of the top-level state.

Users cannot log in because the passcode never arrives. What now?

Offer a second factor that does not depend on SMS, such as an emailed code or an authenticator app, and say so on the login screen. Repeated retries add cost and can trip carrier filtering without helping. Check Plivo's Verify API component and the destination region row, since either one can be the cause.

Will queued messages send after the incident clears?

Usually, and that is a reason not to resend. Messages Plivo accepted are queued on its side, so a backlog often flushes once delivery recovers, which delivers duplicates to anyone you resent to. Time-sensitive codes are the exception, since a passcode arriving late is useless, and those are better replaced than repeated.

Are delivery receipts a reliable outage signal?

They are a useful early one, but they fail separately. Plivo tracks CDR, its call detail records component, on its own, and delivery reporting can stall while messages are still going out normally. Missing receipts mean you cannot see delivery, not necessarily that it stopped. Confirm with a test message to a handset you control.

How we measure this

We request Plivo's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Plivo publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Plivo goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required