Anything Outage History
14 incidents recorded over the last 365 days, 14 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 Anything Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 2, 2026 | Issue Routing Some ApplicationsWe've resolved the issue and apps should be serving traffic normally. | 1h 43m | Resolved |
| Nov 1, 2026 | Issue With Builder And Hosted AppsWe've fully recovered. | 12h 52m | Resolved |
| Oct 24, 2026 | Issues Booting Some Projects in BuilderWe've resolved the upstream issue. | 2h 21m | Resolved |
| Sep 22, 2026 | Issues with Mobile App SubmissionsMobile app submissions are now fully functional. If you are still encountering issues, please contact support. | 49h 18m | Resolved |
| Jul 7, 2026 | Issues Publishing Some ProjectsWe've deployed a fix and the situation is resolved. | 50h 21m | Resolved |
| Jun 25, 2026 | Dev servers failing to startThe upstream provider has fixed their issue and we are seeing our systems recover. | 25 min | Resolved |
| May 7, 2026 | Integration Requests FailingWe've fully recovered. | 38 min | Resolved |
| Apr 17, 2026 | Investigating Delays Starting Dev ServersDev server start times are back to normal. | 8 min | Resolved |
| Mar 6, 2026 | Integrations OutageIntegrations were restored. | -92 min | Resolved |
| Mar 5, 2026 | API containers are unhealthy due to mass DB transaction contentionRolled back. | 2 min | Resolved |
| Jan 14, 2026 | Issues with Builder PreviewsThe issue has been resolved and we've returned to normal operation. | 44 min | Resolved |
| Jan 10, 2026 | Issues Running BuilderWe've resolved the issue and are fully recovered. | 1h 5m | Resolved |
| Dec 15, 2025 | Issues with Agent Image UploadsWe've recovered from the issues with our upstream provider and uploads should be working now. | 6h 12m | Resolved |
| Nov 24, 2025 | Site OutageAll issues have been resolved. | 1h 12m | 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 Anything 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 Anything 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 Anything 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 Anything outage in this window ran 2d 2h, against a mean recovery of 9h 46m. If you depend on Anything 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.