Arcade.dev Outage History
7 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 Arcade.dev Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 17, 2026 | Disruption with user registration and upgradesThis incident has been resolved. | 2h 22m | Resolved |
| Dec 4, 2025 | Arcade Chat issuesThe issue has been resolved. The issue stemmed from the addition of a new features allowing users to belong to multiple Arcade projects, and the chat application not using the newest APIs. | 1h 44m | Resolved |
| Dec 4, 2025 | Errors in the Sign-up FlowWe have worked around the issue and have bug reports open with our identity provider to ensure this won't happen again. | 45 min | Resolved |
| Nov 18, 2025 | Service OutageThis incident has been resolved. | 4h 50m | Resolved |
| Nov 6, 2025 | Unplanned DowntimeWe determined that because of recently adding thousands(!) of tools, one of our production components required a longer than expected startup process, meaning its health check endpoint was unavailable before the timeout… | 33 min | Resolved |
| Nov 3, 2025 | Database UpgradeThe scheduled maintenance has been completed. | 1h 15m | Scheduled |
| Oct 1, 2025 | Dashboard Authentication FailuresFrom 7:30pm PST to 8:30pm PST users were unable to log into the dashboard. Non-dashboard related API calls were uninterrupted. | -60 min | Resolved |
How to Read This Arcade.dev 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 Arcade.dev 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 Arcade.dev outage in this window ran 4h 50m, against a mean recovery of 1h 55m. If you depend on Arcade.dev 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.