Plivo: Outbound Voice API call failures
Timeline of updates
- resolved
A couple of our customers experienced an issue while dispatching outbound Voice API calls, the calls were rejected stating "max call rate limit reached", this was due to malfunctioning of our call rate monitoring service. We have resolved the issue and actively monitoring it. Duration From: 20 April 12:15 AM UTC To: 20 April 03:10 AM UTC
From Plivo’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.plivo.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Plivo, started 2020-04-20 00:30 UTC, resolved after 0 min, 1 update(s).
- Title
- Outbound Voice API call failures
- Vendor
- Plivo
- Date
- URL
- https://rewindex.com/company/plivo/incidents/hs6l2mxsplb7
Plivo profileRecent Plivo incidentsAll outages on April 20, 2020Plivo in April 2020MarkdownJSON