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 36 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 117 ms | 0 |
| Mon 17 | 0 | 0.0 | 382 ms | 0 |
| Mon 19 | 0 | 0.0 | 41 ms | 0 |
| Mon 21 | 0 | 0.0 | 38 ms | 0 |
| Mon 23 | 0 | 0.0 | 149 ms | 0 |
| Tue 01 | 0 | 0.0 | 39 ms | 0 |
| Tue 03 | 0 | 0.0 | 35 ms | 0 |
| Tue 06 | 0 | 0.0 | 22 ms | 0 |
| Tue 08 | 0 | 0.0 | 154 ms | 0 |
| Tue 10 | 0 | 0.0 | 93 ms | 0 |
| Tue 12 | 0 | 0.0 | 84 ms | 0 |
| Tue 14 | 0 | 0.0 | 183 ms | 0 |
| Tue 16 | 0 | 0.0 | 120 ms | 0 |
| Tue 19 | 0 | 0.0 | 195 ms | 0 |
| Tue 21 | 0 | 0.0 | 236 ms | 0 |
| Tue 23 | 0 | 0.0 | 33 ms | 0 |
| Wed 01 | 0 | 0.0 | 192 ms | 0 |
| Wed 04 | 0 | 0.0 | 99 ms | 0 |
| Wed 06 | 0 | 0.0 | 92 ms | 0 |
| Wed 08 | 0 | 0.0 | 30 ms | 0 |
| Wed 10 | 0 | 0.0 | 181 ms | 0 |
| Wed 12 | 0 | 0.0 | 161 ms | 0 |
| Wed 15 | 0 | 0.0 | 124 ms | 0 |
| Wed 17 | 0 | 0.0 | 707 ms | 0 |
| Wed 18 | 0 | 0.0 | 41 ms | 0 |
| Wed 20 | 0 | 0.0 | 37 ms | 0 |
| Wed 22 | 0 | 0.0 | 49 ms | 0 |
| Thu 00 | 0 | 0.0 | 103 ms | 0 |
| Thu 02 | 0 | 0.0 | 38 ms | 0 |
| Thu 04 | 0 | 0.0 | 24 ms | 0 |
| Thu 06 | 0 | 0.0 | 28 ms | 0 |
| Thu 09 | 0 | 0.0 | 34 ms | 0 |
| Thu 11 | 0 | 0.0 | 70 ms | 0 |
| Thu 13 | 0 | 0.0 | 33 ms | 0 |
| Thu 15 | 0 | 0.0 | 97 ms | 0 |
| Thu 17 | 0 | 0.0 | 23 ms | 0 |
| Thu 19 | 0 | 0.0 | 49 ms | 0 |
| Thu 21 | 0 | 0.0 | 25 ms | 0 |
| Thu 23 | 0 | 0.0 | 21 ms | 0 |
| Fri 01 | 0 | 0.0 | 27 ms | 0 |
| Fri 03 | 0 | 0.0 | 53 ms | 0 |
| Fri 05 | 0 | 0.0 | 39 ms | 0 |
| Fri 07 | 0 | 0.0 | 46 ms | 0 |
| Fri 09 | 0 | 0.0 | 24 ms | 0 |
| Fri 11 | 0 | 0.0 | 19 ms | 0 |
| Fri 12 | 0 | 0.0 | 28 ms | 0 |
| Fri 14 | 0 | 0.0 | 32 ms | 0 |
| Fri 16 | 0 | 0.0 | 36 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Blitz 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 Blitz goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Blitz alerts to Slack, Discord or a webhook — free.
Blitz, at blitz.gg, is one of the Gaming services we monitor. Your go-to resource for in-game overlays, meta stats, and tier lists for your favorite games like League of Legends, Teamfight Tactics, VALORANT, EFT, Fortnite, CS2, Apex Legends, Marvel Rivals, and Deadlock.
Blitz publishes an official status page at status.blitz.gg; when we can read it, its incident level is folded into the status shown here.
Typical issues with gaming services: login and matchmaking failures, server disconnects, and store or download errors.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 32 ms average, 10–53 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Blitz incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
32 ms on average over the last 24 hours (10–53 ms).
Yes, at https://status.blitz.gg.
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 Blitz here at once, the problem is on Blitz'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 Blitz. 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.