Arcade.dev incident
Some tool authorization links on Arcade Cloud return a 502 error
Resolved after 4 hours 58 minutes, affecting Engine API, on October 29, 2026.
Further investigation has limited this to very limited MCP Servers - Limited exposure to Arcade Cloud customers. Downgrading impacted - fix to ship soon.
Affected components
Update timeline
- investigating Oct 29, 2026, 06:28 PM UTC
Some users who click an authorization link (cloud.arcade.dev/a/…) to connect a tool are seeing a 502 error page instead of the provider's consent screen. Authorization cannot be completed for the affected tools until this is fixed. Tools that users have already authorized continue to run, and the API, dashboard, and MCP gateways are not affected. We have found the cause. For some providers, the redirect to the consent page carries headers large enough to exceed a buffer limit at our edge, which returns the 502. A fix is merged and is being deployed to production now. We will post an update once it is live and verified. Earliest known failure: approximately 16:10 UTC today.
- identified Oct 29, 2026, 06:28 PM UTC
The issue has been identified and a fix is being implemented.
- identified Oct 29, 2026, 10:20 PM UTC
Further investigation has limited this to very limited MCP Servers - Limited exposure to Arcade Cloud customers. Downgrading impacted - fix to ship soon.
- resolved Oct 29, 2026, 11:26 PM UTC
The issue has been resolved.
Your product runs on more than Arcade.dev
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services