Auphonic Outage History
4 incidents recorded over the last 365 days, 4 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Auphonic Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 30, 2026 | Cloudflare storage works again | 3 min | Resolved |
| Oct 29, 2026 | Degraded Performance of Storage Backend | 164h 10m | Resolved |
| Oct 20, 2026 | Audio processing problems due to a Hetzner network problem | 380h 25m | Resolved |
| Oct 1, 2026 | Audio Processing interruption | 838h 26m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Auphonic incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Auphonic Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Auphonic acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Auphonic outage in this window ran 34d 22h, against a mean recovery of 14d 9h. If you depend on Auphonic in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.