Arcade.dev Outage History

Arcade.dev is up right now

Arcade.dev had 6 outages in the last 2 years totaling 15h 24m of downtime — averaging 0.2 incidents per month.

There were 6 Arcade.dev outages since November 6, 2025 totaling 15h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.arcade.dev

Minor October 6, 2026

Authorization prompts hanging in Claude Cowork

Detected by Pingoru
Oct 06, 2026, 09:04 PM UTC
Resolved
Oct 07, 2026, 02:11 AM UTC
Duration
5h 7m
Affected: Engine API
Timeline · 2 updates
  1. investigating Oct 06, 2026, 09:04 PM UTC

    We have identified the cause of hanging authorization prompts for some users connecting to Arcade through Claude Cowork. Claude Cowork does not correctly handle the URL elicitation flow that Arcade uses to authorize users. Claude Code is not affected. We are working on a mitigation and have reported the issue to Anthropic. Until then, users can authorize new tools through Claude Code. We will post another update when the mitigation is live.

  2. resolved Oct 07, 2026, 02:11 AM UTC

    Issue has been resolved

Read the full incident report →

Major July 17, 2026

Disruption with user registration and upgrades

Detected by Pingoru
Jul 17, 2026, 03:37 PM UTC
Resolved
Jul 17, 2026, 05:59 PM UTC
Duration
2h 22m
Affected: Dashboard
Timeline · 4 updates
  1. investigating Jul 17, 2026, 03:37 PM UTC

    We are investigating an issue where users are unable to register or upgrade plans

  2. identified Jul 17, 2026, 03:56 PM UTC

    The solution has been identified and is being implemented

  3. identified Jul 17, 2026, 04:22 PM UTC

    Registration issues have been resolved. Plan upgrade fix is being implemented

  4. resolved Jul 17, 2026, 05:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 4, 2025

Arcade Chat issues

Detected by Pingoru
Dec 04, 2025, 01:53 AM UTC
Resolved
Dec 04, 2025, 03:37 AM UTC
Duration
1h 44m
Affected: Arcade Chat
Timeline · 2 updates
  1. investigating Dec 04, 2025, 01:53 AM UTC

    We are investigating issues using tools on chat.arcade.dev. The Arcade platform API and infrastructure remain healthy.

  2. resolved Dec 04, 2025, 03:37 AM UTC

    The 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.

Read the full incident report →

Minor December 4, 2025

Errors in the Sign-up Flow

Detected by Pingoru
Dec 04, 2025, 12:48 AM UTC
Resolved
Dec 04, 2025, 01:33 AM UTC
Duration
45m
Affected: Dashboard
Timeline · 2 updates
  1. investigating Dec 04, 2025, 12:48 AM UTC

    We are investigating an issue with our identity provider that is causing sign-ups to error during the email verification flow. After seeing a page with an error, you should still receive an email; click the link in that email to continue the sign-up flow.

  2. resolved Dec 04, 2025, 01:33 AM UTC

    We have worked around the issue and have bug reports open with our identity provider to ensure this won't happen again.

Read the full incident report →

Critical November 18, 2025

Service Outage

Detected by Pingoru
Nov 18, 2025, 11:55 AM UTC
Resolved
Nov 18, 2025, 04:46 PM UTC
Duration
4h 50m
Affected: Engine APIDashboardCloud APIArcade Chat
Timeline · 9 updates

Read the full incident report →

Critical November 6, 2025

Unplanned Downtime

Detected by Pingoru
Nov 06, 2025, 11:20 PM UTC
Resolved
Nov 06, 2025, 11:54 PM UTC
Duration
33m
Affected: Engine API
Timeline · 4 updates
  1. investigating Nov 06, 2025, 11:20 PM UTC

    We are currently investigating an issue with our production deployments. We are attempting to rollback to a stable version. Investigation of the issue continues.

  2. investigating Nov 06, 2025, 11:22 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Nov 06, 2025, 11:30 PM UTC

    Our prod services are now recovering. We are continuing to monitor and have identified the root cause of the issue.

  4. resolved Nov 06, 2025, 11:54 PM UTC

    We 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 expired. As a result, orchestrator was constantly restarting nodes, leading to poor availability of this critical component. Going forward, we plan to move these tasks out of component startup so this doesn't happen again and we can continue to support even larger numbers of tools.

Read the full incident report →