Plivo: Recordings affected
Timeline of updates
- resolved
We observe that Recording files may not be returning correctly for calls this was because of a misconfiguration in our systems, We are working on recovering all the files.
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-01-07 12:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Recordings affected
- Vendor
- Plivo
- Date
- URL
- https://rewindex.com/company/plivo/incidents/hf2sszy32mgt
Plivo profileRecent Plivo incidentsAll outages on January 7, 2016Plivo in January 2016MarkdownJSON