Aha! Outage History
6 incidents recorded over the last 365 days, 6 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 Aha! Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 1, 2026 | Some Aha! Builder applications unavailable.Resolution is confirmed. If you are still experiencing issues, try restarting your browser to clear stale DNS cache entries. | 33 min | Resolved |
| Aug 27, 2026 | Slow performance for some usersSome users may have experienced slow performance for ten minutes between 8:27am and 8:37am PDT. | -15 min | Resolved |
| Jul 28, 2026 | Degraded performance for some customers.This incident has been resolved. | 25 min | Resolved |
| Feb 18, 2026 | Slow performance for some customersThis incident has been resolved. | 1h 1m | Resolved |
| Feb 10, 2026 | Elevated Error Rates for some customersSome Aha! customers experienced elevated error rates between 7:26 AM and 8:52 AM EST. | -3 min | Resolved |
| Feb 3, 2026 | Slow performance for Aha! AppThe issue was fully resolved at 10:42 AM EST. | 4h 3m | 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 Aha! 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 Aha! 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 Aha! 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 Aha! outage in this window ran 4h 3m, against a mean recovery of 1h 31m. If you depend on Aha! 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.