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 2 hr ago. Last stored result reached it in 218 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 190 ms | 0 |
| Tue 01 | 0 | 0.0 | 209 ms | 0 |
| Tue 03 | 0 | 0.0 | 298 ms | 0 |
| Tue 06 | 0 | 0.0 | 238 ms | 0 |
| Tue 08 | 0 | 0.0 | 272 ms | 0 |
| Tue 10 | 0 | 0.0 | 361 ms | 0 |
| Tue 12 | 0 | 0.0 | 213 ms | 0 |
| Tue 14 | 0 | 0.0 | 381 ms | 0 |
| Tue 16 | 0 | 0.0 | 164 ms | 0 |
| Tue 19 | 0 | 0.0 | 378 ms | 0 |
| Tue 21 | 0 | 0.0 | 279 ms | 0 |
| Tue 23 | 0 | 0.0 | 274 ms | 0 |
| Wed 01 | 0 | 0.0 | 383 ms | 0 |
| Wed 04 | 0 | 0.0 | 775 ms | 0 |
| Wed 06 | 0 | 0.0 | 345 ms | 0 |
| Wed 08 | 0 | 0.0 | 297 ms | 0 |
| Wed 10 | 0 | 0.0 | 237 ms | 0 |
| Wed 12 | 0 | 0.0 | 95 ms | 0 |
| Wed 15 | 0 | 0.0 | 205 ms | 0 |
| Wed 16 | 0 | 0.0 | 271 ms | 0 |
| Wed 19 | 0 | 0.0 | 173 ms | 0 |
| Wed 21 | 0 | 0.0 | 244 ms | 0 |
| Wed 23 | 0 | 0.0 | 199 ms | 0 |
| Thu 01 | 0 | 0.0 | 263 ms | 0 |
| Thu 03 | 0 | 0.0 | 285 ms | 0 |
| Thu 05 | 0 | 0.0 | 119 ms | 0 |
| Thu 07 | 0 | 0.0 | 116 ms | 0 |
| Thu 09 | 0 | 0.0 | 124 ms | 0 |
| Thu 11 | 0 | 0.0 | 255 ms | 0 |
| Thu 13 | 0 | 0.0 | 159 ms | 0 |
| Thu 16 | 0 | 0.0 | 325 ms | 0 |
| Thu 18 | 0 | 0.0 | 319 ms | 0 |
| Thu 20 | 0 | 0.0 | 255 ms | 0 |
| Thu 22 | 0 | 0.0 | 236 ms | 0 |
| Fri 00 | 0 | 0.0 | 240 ms | 0 |
| Fri 02 | 0 | 0.0 | 143 ms | 0 |
| Fri 04 | 0 | 0.0 | 194 ms | 0 |
| Fri 06 | 0 | 0.0 | 126 ms | 0 |
| Fri 08 | 0 | 0.0 | 327 ms | 0 |
| Fri 10 | 0 | 0.0 | 308 ms | 0 |
| Fri 11 | 0 | 0.0 | 306 ms | 0 |
| Fri 13 | 0 | 0.0 | 249 ms | 0 |
| Fri 14 | 0 | 0.0 | 198 ms | 0 |
| Fri 16 | 0 | 0.0 | 228 ms | 0 |
| Fri 18 | 0 | 0.0 | 272 ms | 0 |
| Fri 19 | 0 | 0.0 | 315 ms | 0 |
| Fri 21 | 0 | 0.0 | 218 ms | 0 |
| Fri 23 | 0 | 0.0 | 218 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 Bloxtsar 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 Bloxtsar goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Bloxtsar alerts to Slack, Discord or a webhook — free.
We track Bloxtsar (bloxtsar.com) as part of the Gaming group. Trade Roblox game items on Bloxtsar with real-time values, trade ads, calculators, secure messaging, and community tools across popular Roblox games.
Bloxtsar publishes an official status page at status.bloxtsar.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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 233 ms average, 126–327 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 Bloxtsar incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
233 ms on average over the last 24 hours (126–327 ms).
Yes, at https://status.bloxtsar.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 Bloxtsar here at once, the problem is on Bloxtsar'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 Bloxtsar. 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.