Axios HQ Outage History
3 incidents recorded over the last 365 days, 3 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 Axios HQ Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 5, 2026 | Scheduled Maintenance, Aug 12th from 9:00 - 11:00 PM ETMaintenance has started | 175h 34m | Resolved |
| Mar 16, 2026 | HQ is experiencing an outage The issue has been resolved. We apologize for any inconvenience the disruption may have caused. | 20 min | Resolved |
| Nov 18, 2025 | Intermittent Platform Outage due to Cloudflare IncidentCloudflare has resolved the issue. Everything has been functional for the past few hours but we were extra cautious in case additional errors would appear. Thank you for your patience. | 7h 37m | 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 Axios HQ 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 Axios HQ 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 Axios HQ 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 Axios HQ outage in this window ran 7d 7h, against a mean recovery of 2d 13h. If you depend on Axios HQ 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.