Act 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 Act Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 29, 2026 | US Customers - 504 Gateway timeoutsThis issue has been resolved. The fix has been implemented and verified. If you continue to experience any problems, please clear your browser cache by following the knowledgebase article below, or reach out to… | 3h 16m | Resolved |
| May 8, 2026 | US Region Service DisruptionFollowing an AWS infrastructure outage, one of our Act! Cloud database servers required a migration and recovery in order to restore service. As part of this process, customers may experience a loss of data submitted or… | 4h 54m | Resolved |
| Apr 15, 2026 | Resolved: Partial Sync Disruption – Australia, Europe & UK RegionsRemote database sync was partially impacted in the Australian, EU, and UK regions Impact windows (all times UTC): • Australia: 14 Apr 14:00 - 15 Apr 06:00 (16 hours) • EU & UK: 14 Apr 20:00 - 15 Apr 06:00 (10… | -1236 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 Act 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 Act 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 Act 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 Act outage in this window ran 4h 54m, against a mean recovery of 4h 5m. If you depend on Act 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.