CheckUpstream measured Plivo at 100.000% availability across 672 independent checks (global · api). 11 incidents were recorded in the past 12 months; the most recent resolved 6 days ago after 9 minutes. Status signals are polled from Plivo's official Atlassian Statuspage status page, alongside independent probes and community reports.
7 days measured availability how this is computed
100.000%
global · api · n=672 · p95 587ms (7d)
Share of our own checks against Plivo endpoints that returned Plivo's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 1 incident · 7 of 7 days with none posted · 2m of declared impact
Fewer incidents in the last 30 days than 34% of 232 tracked services.
Share of each window with no impact declared by Plivo
7d
99.973%
30d
99.994%
90d
99.998%
180d
99.987%
1y
99.994%
Downtime like this can be refundable
If you're a paying Plivo customer, outages in these windows may count against Plivo's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Plivo entitlement →Does Plivo actually matter to you?
A Plivo outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Aug 25, 07:25 UTC · resolved in 9m · Resolved
Jul 11, 07:47 UTC · resolved in 2h 12m · Resolved
Jun 30, 08:00 UTC · resolved in 1h 49m · Resolved
Live Plivo status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/plivo)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Plivo is currently Operational. CheckUpstream tracks Plivo in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Plivo's last resolved incident started 6 days ago and lasted 9 minutes (degraded performance).
Looking for the live "is Plivo down" view? See the Plivo Live status page.
Jun 19, 13:01 UTC · resolved in 1h · Resolved
Plivo's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Plivo endpoints. It is the share of checks that returned the expected response, not a figure taken from Plivo's status page.
Sign up to CheckUpstream and add Plivo to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Plivo's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.