Anomali Outage History
11 incidents recorded over the last 365 days. 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 Anomali Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jun 26, 2026 | Infrastructure and Capacity Maintenance (US SaaS)The scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jun 24, 2026 | Infrastructure and Capacity Maintenance (EU SaaS)The scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jun 23, 2026 | Infrastructure and Capacity Maintenance (US SaaS)The scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Jun 22, 2026 | Infrastructure and Capacity Maintenance (EU SaaS)The scheduled maintenance has been completed. | 3h 0m | Scheduled |
| May 8, 2026 | Infrastructure and Capacity Maintenance (US SaaS)The scheduled maintenance has been completed. | 1h 0m | Scheduled |
| May 1, 2026 | Infrastructure and Capacity Maintenance (US SaaS)The scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Apr 24, 2026 | Infrastructure and Capacity Maintenance (EU SaaS)The scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Feb 27, 2026 | Infrastructure and Capacity Maintenance (US SaaS)The scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Feb 26, 2026 | Infrastructure and Capacity Maintenance (US SaaS)The scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Feb 13, 2026 | Infrastructure and Capacity Maintenance (US SaaS)The scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Feb 12, 2026 | Infrastructure and Capacity Maintenance (EU SaaS)The scheduled maintenance has been completed. | 2h 0m | Scheduled |
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 Anomali 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 Anomali 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 Anomali 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 Anomali outage in this window ran 3h, against a mean recovery of 1h 55m. If you depend on Anomali 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.