Is Roblox down? (client-side check)
This page runs a network probe from your browser against four Roblox endpoints and reports whether each one responds. It's not an official status feed — it tells you what your network can reach right now.
What this page actually measures
A truly authoritative Roblox status page lives at status.roblox.com — that's
the company's own incident feed, and it's what to check first during a confirmed outage.
What this page does is independent: from your browser, it tries to reach a few
Roblox endpoints and reports whether the request completed. If your home network has a
DNS issue or a parental-control filter blocking Roblox, this page will show those
endpoints as unreachable even though Roblox itself is fine.
The probes use a mix of techniques:
- Thumbnail / CDN endpoints are probed with
<img>tags. An image either loads (success) or errors (failure). This is the most reliable signal because image requests aren't subject to CORS. - roblox.com and API edges are probed with
fetch(url, { mode: "no-cors" }). The response is opaque — we can't read it — but we can tell if the request reached a server. - Results are cached in
sessionStoragefor 60 seconds so a refresh doesn't hammer the endpoints.
What each column actually hits
The four cells aren't four different Roblox systems — they're four specific requests, and
knowing which is which makes the grid much more readable. Web is a fetch
against the roblox.com homepage. API edge is a fetch against the login
route on the same host — a different path through the same front door, included because
login trouble sometimes surfaces while the heavily-cached homepage still answers.
CDN loads a static image from the t1.rbxcdn.com asset host,
and Thumbnails loads one from tr.rbxcdn.com, the host that
serves avatar and item thumbnails in-game and on the site. Each probe gets six seconds;
anything slower is counted as DOWN, so a badly struggling connection can look like an
outage even when packets are technically arriving.
When to trust this page
Use it as a first-pass check. If three of the four probes fail, something is almost certainly wrong on Roblox's side (or your whole internet is down — try opening any other site). If only one probe fails, it's more likely a regional CDN node, a DNS hiccup, or your local network filter.
If the page reports everything green but you still can't connect in the Roblox app, the issue is probably with the Roblox client itself, the specific server you tried to join, or login services — none of which this page can detect.
Two failure patterns deserve special suspicion. First, images DOWN while the fetches show OK is the signature of a content blocker: ad blockers, strict privacy modes, and some school filters cancel third-party image requests before they leave the browser, which reads as a CDN failure here. Try a normal window before concluding anything about Roblox. Second, the reverse asymmetry: the fetch probes count a request as reachable if any server answers — and that includes a parental-control or network filter answering on Roblox's behalf with a block page. The image probes are stricter, because they only pass when a real image actually decodes. So OK fetches plus two dead image probes is a hint that something between you and Roblox is intercepting, not that Roblox is half-down.
If it really is down
Confirm on status.roblox.com, then wait — there is no client-side trick that
brings a platform outage back faster. One safety note worth stating plainly: outages are
prime time for phishing. Any site or message that says "Roblox is down, log in here to
check your account" is a credential grab, full stop. A reachability page like this one
never needs your password, and neither does any legitimate status service.
FAQ
Why can't this tell me what's wrong, just whether something is wrong?
BloxToolbox is a static site. It has no backend, so it can't query Roblox's internal incident feed. We measure reachability and let you draw the conclusion.
Will this page get me unbanned if I'm rate-limited?
No. This is a reachability test, not an account-status check.
Why did a re-run show different results a minute later?
The four probes run concurrently with a six-second timeout each, and results are cached in your browser for 60 seconds. A momentary DNS or Wi-Fi hiccup can fail one probe on one run and pass it on the next. Treat a single mixed reading as noise and a repeated pattern as signal.
Does this page send my data to Roblox?
The probes are plain requests sent with no referrer, and the results live only in your browser's sessionStorage for 60 seconds. Nothing about the check is stored by us or sent anywhere else — the only traffic is the four requests themselves.
Related tools
- Asset ID lookup — fetch a thumbnail by ID.
- Robux ↔ USD converter