Hedra Outage History
5 incidents recorded over the last 365 days, 5 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 Hedra Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Feb 27, 2026 | An elevated number of generations failures are reported.The issue has been resolved. All failed generations will be refunded by EOD. | 1h 4m | Resolved |
| Dec 25, 2025 | High Queue times for Character-3The queue has returned to normal operating levels. We will retain scaled capacity to ensure we can meet the demand. | 1h 42m | Resolved |
| Dec 5, 2025 | Cloudflare outage: authentication impacted Cloudflare has resolved the issue. | 6h 15m | Resolved |
| Nov 6, 2025 | An elevated number of generation failures are occuring with the Character-3 modelQueue is recovering, generations are restored to full capacity. | 40 min | Resolved |
| Nov 6, 2025 | Scheduled Maintenance - Brief Service InterruptionMaintenance is complete and service is fully restored. Thank you for your patience! | 18 min | 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 Hedra 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 Hedra 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 Hedra 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 Hedra outage in this window ran 6h 15m, against a mean recovery of 1h 60m. If you depend on Hedra 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.