User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Gaming
ea.com · Gaming
Something is off: our checks are slower than usual or had a single recent failure.
Live diagnosis
Tests ea.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
Reachable from all 4 regions we check from.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Slow or flaky
Last check reached it in 2806 ms · 3 min ago.
No status feed
Apex Legends does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 11:30 | 0 | 0.0 | 1240 ms | 0 |
| 11:45 | 0 | 0.0 | 958 ms | 0 |
| 12:00 | 0 | 0.0 | 910 ms | 0 |
| 12:15 | 0 | 0.0 | 647 ms | 0 |
| 12:30 | 0 | 0.0 | 98 ms | 0 |
| 12:45 | 0 | 0.0 | 1070 ms | 0 |
| 13:00 | 0 | 0.0 | 1163 ms | 0 |
| 13:15 | 0 | 0.0 | 144 ms | 0 |
| 13:30 | 0 | 0.0 | 175 ms | 0 |
| 13:45 | 0 | 0.0 | 957 ms | 0 |
| 14:00 | 0 | 0.0 | 560 ms | 0 |
| 14:15 | 0 | 0.0 | 392 ms | 0 |
| 14:30 | 0 | 0.0 | 113 ms | 0 |
| 14:45 | 0 | 0.0 | 352 ms | 0 |
| 15:00 | 0 | 0.0 | 106 ms | 0 |
| 15:15 | 0 | 0.0 | 210 ms | 0 |
| 15:30 | 0 | 0.0 | 123 ms | 0 |
| 15:45 | 0 | 0.0 | 378 ms | 0 |
| 16:00 | 0 | 0.0 | 148 ms | 0 |
| 16:15 | 0 | 0.0 | 924 ms | 0 |
| 16:30 | 0 | 0.0 | 306 ms | 0 |
| 16:45 | 0 | 0.0 | 314 ms | 0 |
| 17:00 | 0 | 0.0 | 1379 ms | 0 |
| 17:15 | 0 | 0.0 | 88 ms | 0 |
| 17:30 | 0 | 0.0 | 840 ms | 0 |
| 17:45 | 0 | 0.0 | 1232 ms | 0 |
| 18:00 | 0 | 0.0 | 2107 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed this status badge · JSON
No outages on record for Apex Legends 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 Apex Legends goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Something is off: our checks are slower than usual or had a single recent failure.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.