User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
arcade.dev · AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 23 min ago. Last stored result reached it in 679 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 401 ms | 0 |
| Mon 19 | 0 | 0.0 | 999 ms | 0 |
| Mon 21 | 0 | 0.0 | 551 ms | 0 |
| Mon 23 | 0 | 0.0 | 84 ms | 0 |
| Tue 01 | 0 | 0.0 | 942 ms | 0 |
| Tue 03 | 0 | 0.0 | 906 ms | 0 |
| Tue 05 | 0 | 0.0 | 380 ms | 0 |
| Tue 07 | 0 | 0.0 | 709 ms | 0 |
| Tue 09 | 0 | 0.0 | 90 ms | 0 |
| Tue 11 | 0 | 0.0 | 109 ms | 0 |
| Tue 14 | 0 | 0.0 | 835 ms | 0 |
| Tue 16 | 0 | 0.0 | 428 ms | 0 |
| Tue 18 | 0 | 0.0 | 563 ms | 0 |
| Tue 20 | 0 | 0.0 | 614 ms | 0 |
| Tue 23 | 0 | 0.0 | 91 ms | 0 |
| Wed 01 | 0 | 0.0 | 1020 ms | 0 |
| Wed 03 | 0 | 0.0 | 983 ms | 0 |
| Wed 05 | 0 | 0.0 | 511 ms | 0 |
| Wed 07 | 0 | 0.0 | 281 ms | 0 |
| Wed 10 | 0 | 0.0 | 763 ms | 0 |
| Wed 12 | 0 | 0.0 | 612 ms | 0 |
| Wed 14 | 0 | 0.0 | 699 ms | 0 |
| Wed 16 | 0 | 0.0 | 172 ms | 0 |
| Wed 18 | 0 | 0.0 | 694 ms | 0 |
| Wed 20 | 0 | 0.0 | 70 ms | 0 |
| Wed 21 | 0 | 0.0 | 1272 ms | 0 |
| Wed 23 | 0 | 0.0 | 1023 ms | 0 |
| Thu 01 | 0 | 0.0 | 414 ms | 0 |
| Thu 03 | 0 | 0.0 | 441 ms | 0 |
| Thu 05 | 0 | 0.0 | 435 ms | 0 |
| Thu 07 | 0 | 0.0 | 350 ms | 0 |
| Thu 09 | 0 | 0.0 | 476 ms | 0 |
| Thu 11 | 0 | 0.0 | 645 ms | 0 |
| Thu 14 | 0 | 0.0 | 665 ms | 0 |
| Thu 16 | 0 | 0.0 | 110 ms | 0 |
| Thu 18 | 0 | 0.0 | 530 ms | 0 |
| Thu 20 | 0 | 0.0 | 755 ms | 0 |
| Thu 22 | 0 | 0.0 | 445 ms | 0 |
| Fri 00 | 0 | 0.0 | 711 ms | 0 |
| Fri 02 | 0 | 0.0 | 93 ms | 0 |
| Fri 04 | 0 | 0.0 | 555 ms | 0 |
| Fri 06 | 0 | 0.0 | 592 ms | 0 |
| Fri 08 | 0 | 0.0 | 94 ms | 0 |
| Fri 10 | 0 | 0.0 | 663 ms | 0 |
| Fri 11 | 0 | 0.0 | 652 ms | 0 |
| Fri 13 | 0 | 0.0 | 830 ms | 0 |
| Fri 15 | 0 | 0.0 | 400 ms | 0 |
| Fri 17 | 0 | 0.0 | 679 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Arcade yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Arcade goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Arcade alerts to Slack, Discord or a webhook — free.
We track Arcade (arcade.dev) as part of the AI group. Arcade is the actions runtime for enterprise AI agents — one control point to enforce, execute, and govern every action, every time. Try it free.
Arcade publishes an official status page at status.arcade.dev; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 539 ms average, 93–830 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Arcade incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
539 ms on average over the last 24 hours (93–830 ms).
Yes, at https://status.arcade.dev.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Arcade here at once, the problem is on Arcade's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Arcade. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.