Plivo: Connectivity issue in one of the AU region server (AU BYOC number)
Timeline of updates
- resolved
We're experiencing connectivity issues in one of our secondary server located in AU region. This incident will only impact AU BYOC DID service. But, this can be avoided if the BYOC carrier is routing calls to our DNS SRV: au.sbc.plivo.com (Our primary server in AU region is UP and running).
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: minor) posted by Plivo, started 2016-06-05 12:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Connectivity issue in one of the AU region server (AU BYOC number)
- Vendor
- Plivo
- Date
- URL
- https://rewindex.com/company/plivo/incidents/x8cmlwvg5crq
Plivo profileRecent Plivo incidentsAll outages on June 5, 2016Plivo in June 2016MarkdownJSON