User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 2 hr ago. Last stored result reached it in 147 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 06 | 0 | 0.0 | 201 ms | 0 |
| Tue 08 | 0 | 0.0 | 223 ms | 0 |
| Tue 10 | 0 | 0.0 | 123 ms | 0 |
| Tue 12 | 0 | 0.0 | 264 ms | 0 |
| Tue 14 | 0 | 0.0 | 142 ms | 0 |
| Tue 17 | 0 | 0.0 | 245 ms | 0 |
| Tue 19 | 0 | 0.0 | 269 ms | 0 |
| Tue 21 | 0 | 0.0 | 246 ms | 0 |
| Tue 23 | 0 | 0.0 | 191 ms | 0 |
| Wed 02 | 0 | 0.0 | 236 ms | 0 |
| Wed 04 | 0 | 0.0 | 198 ms | 0 |
| Wed 06 | 0 | 0.0 | 195 ms | 0 |
| Wed 08 | 0 | 0.0 | 84 ms | 0 |
| Wed 11 | 0 | 0.0 | 242 ms | 0 |
| Wed 13 | 0 | 0.0 | 133 ms | 0 |
| Wed 15 | 0 | 0.0 | 307 ms | 0 |
| Wed 17 | 0 | 0.0 | 277 ms | 0 |
| Wed 19 | 0 | 0.0 | 271 ms | 0 |
| Wed 21 | 0 | 0.0 | 338 ms | 0 |
| Thu 00 | 0 | 0.0 | 156 ms | 0 |
| Thu 02 | 0 | 0.0 | 93 ms | 0 |
| Thu 04 | 0 | 0.0 | 301 ms | 0 |
| Thu 06 | 0 | 0.0 | 129 ms | 0 |
| Thu 08 | 0 | 0.0 | 136 ms | 0 |
| Thu 10 | 0 | 0.0 | 402 ms | 0 |
| Thu 12 | 0 | 0.0 | 197 ms | 0 |
| Thu 14 | 0 | 0.0 | 280 ms | 0 |
| Thu 16 | 0 | 0.0 | 339 ms | 0 |
| Thu 18 | 0 | 0.0 | 238 ms | 0 |
| Thu 20 | 0 | 0.0 | 299 ms | 0 |
| Thu 22 | 0 | 0.0 | 244 ms | 0 |
| Fri 00 | 0 | 0.0 | 464 ms | 0 |
| Fri 02 | 0 | 0.0 | 196 ms | 0 |
| Fri 05 | 0 | 0.0 | 255 ms | 0 |
| Fri 07 | 0 | 0.0 | 216 ms | 0 |
| Fri 09 | 0 | 0.0 | 181 ms | 0 |
| Fri 11 | 0 | 0.0 | 304 ms | 0 |
| Fri 12 | 0 | 0.0 | 109 ms | 0 |
| Fri 14 | 0 | 0.0 | 234 ms | 0 |
| Fri 16 | 0 | 0.0 | 193 ms | 0 |
| Fri 18 | 0 | 0.0 | 390 ms | 0 |
| Fri 20 | 0 | 0.0 | 246 ms | 0 |
| Fri 22 | 0 | 0.0 | 177 ms | 0 |
| Fri 23 | 0 | 0.0 | 84 ms | 0 |
| Sat 01 | 0 | 0.0 | 155 ms | 0 |
| Sat 03 | 0 | 0.0 | 153 ms | 0 |
| Sat 05 | 0 | 0.0 | 140 ms | 0 |
| Sat 07 | 0 | 0.0 | 147 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Blurred.gg 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 Blurred.gg goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Blurred.gg alerts to Slack, Discord or a webhook — free.
We track Blurred.gg (blurred.gg) as part of the Productivity group. Blurred.gg offers premium DMA cheats with Aimbot, ESP, and more. Trusted by thousands with instant delivery and 24/7 support.
Blurred.gg publishes an official status page at status.blurred.gg; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 194 ms average, 84–390 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 Blurred.gg incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
194 ms on average over the last 24 hours (84–390 ms).
Yes, at https://status.blurred.gg.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Blurred.gg here at once, the problem is on Blurred.gg'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 Blurred.gg. 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.