User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Gaming
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 1 hr ago. Last stored result reached it in 72 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 01 | 0 | 0.0 | 112 ms | 0 |
| Tue 03 | 0 | 0.0 | 110 ms | 0 |
| Tue 05 | 0 | 0.0 | 229 ms | 0 |
| Tue 07 | 0 | 0.0 | 100 ms | 0 |
| Tue 10 | 0 | 0.0 | 114 ms | 0 |
| Tue 12 | 0 | 0.0 | 118 ms | 0 |
| Tue 14 | 0 | 0.0 | 134 ms | 0 |
| Tue 16 | 0 | 0.0 | 138 ms | 0 |
| Tue 18 | 0 | 0.0 | 145 ms | 0 |
| Tue 21 | 0 | 0.0 | 175 ms | 0 |
| Tue 23 | 0 | 0.0 | 295 ms | 0 |
| Wed 01 | 0 | 0.0 | 98 ms | 0 |
| Wed 03 | 0 | 0.0 | 106 ms | 0 |
| Wed 06 | 0 | 0.0 | 139 ms | 0 |
| Wed 08 | 0 | 0.0 | 1082 ms | 0 |
| Wed 10 | 0 | 0.0 | 428 ms | 0 |
| Wed 12 | 0 | 0.0 | 211 ms | 0 |
| Wed 14 | 0 | 0.0 | 136 ms | 0 |
| Wed 16 | 0 | 0.0 | 404 ms | 0 |
| Wed 19 | 0 | 0.0 | 211 ms | 0 |
| Wed 21 | 0 | 0.0 | 159 ms | 0 |
| Wed 23 | 0 | 0.0 | 130 ms | 0 |
| Thu 01 | 0 | 0.0 | 259 ms | 0 |
| Thu 03 | 0 | 0.0 | 135 ms | 0 |
| Thu 05 | 0 | 0.0 | 99 ms | 0 |
| Thu 07 | 0 | 0.0 | 231 ms | 0 |
| Thu 09 | 0 | 0.0 | 77 ms | 0 |
| Thu 11 | 0 | 0.0 | 212 ms | 0 |
| Thu 13 | 0 | 0.0 | 221 ms | 0 |
| Thu 15 | 0 | 0.0 | 153 ms | 0 |
| Thu 17 | 0 | 0.0 | 190 ms | 0 |
| Thu 19 | 0 | 0.0 | 109 ms | 0 |
| Thu 21 | 0 | 0.0 | 120 ms | 0 |
| Thu 23 | 0 | 0.0 | 151 ms | 0 |
| Fri 01 | 0 | 0.0 | 223 ms | 0 |
| Fri 03 | 0 | 0.0 | 101 ms | 0 |
| Fri 05 | 0 | 0.0 | 160 ms | 0 |
| Fri 07 | 0 | 0.0 | 109 ms | 0 |
| Fri 09 | 0 | 0.0 | 96 ms | 0 |
| Fri 10 | 0 | 0.0 | 109 ms | 0 |
| Fri 11 | 0 | 0.0 | 88 ms | 0 |
| Fri 13 | 0 | 0.0 | 295 ms | 0 |
| Fri 15 | 0 | 0.0 | 177 ms | 0 |
| Fri 17 | 0 | 0.0 | 120 ms | 0 |
| Fri 18 | 0 | 0.0 | 148 ms | 0 |
| Fri 19 | 0 | 0.0 | 231 ms | 0 |
| Fri 21 | 0 | 0.0 | 270 ms | 0 |
| Fri 23 | 0 | 0.0 | 72 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 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for ERLCX 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 ERLCX goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send ERLCX alerts to Slack, Discord or a webhook — free.
We track ERLCX (erlcx.com) as part of the Gaming group. Browse and share ER:LC liveries, map templates, and custom content on ERLCX
ERLCX publishes an official status page at status.erlcx.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with gaming services: login and matchmaking failures, server disconnects, and store or download errors.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 155 ms average, 72–295 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public ERLCX incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
155 ms on average over the last 24 hours (72–295 ms).
Yes, at https://status.erlcx.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For gaming services, watch for login and matchmaking failures, server disconnects, and store or download errors. If many people report ERLCX here at once, the problem is on ERLCX'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 ERLCX. 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.