First probe pending
We're running your check now. Reload in a few seconds to see live data.
Estado del publisher · statuspage
Estado de Roblox
Live incidents and maintenance pulled from the publisher's official status page.
PENDIENTE
0.00% uptimelast 30 days
30 days agocollecting data · 1/30 daystoday
Checked 7s ago
single-source feed
every 5 min · publisher feed
direct probe, not crowd-reported
Estado del publisher
- Indicator
- error
- Description
- Live status feed is temporarily unavailable.
- Source
- https://status.roblox.com
- Adapter
- statuspage
Qué significa
Publisher status data not yet available.
A poll is in progress or the upstream feed returned an error. Refresh in a few seconds.
Qué hacer ahora
Browse
Explore the global status page while you wait.
Página de estado oficial
status.roblox.com Roblox's official status pageFAQ
Why does this page show Roblox as up while my game won't connect?
Publisher status pages show the publisher's view, not yours. Roblox aggregates many internal signals; user-visible problems (matchmaker queues, regional CDN issues, account auth) sometimes don't trip the public indicator. Check the active incidents list below for narrower scope.
How is this different from a direct probe?
Websites and game servers get hit with a live network request. Publishers don't expose a single check endpoint, so we poll their official status feed (Statuspage, Riot, etc.) every 5 minutes and surface their classification verbatim.
Where does the data come from?
Directly from Roblox's own status feed, see https://status.roblox.com. We don't aggregate Twitter or DownDetector signals.
Status badge
Embed a live status badge on your site, README, or status page. Updates automatically, same status-aware SVG the rest of isitdown.io uses.
<a href="https://isitdown.io/publisher/roblox"><img src="https://isitdown.io/badge/publisher/roblox.svg" alt="Roblox status"></a>
Relacionados
Metodología
- Sonda
- We poll the publisher's official status page endpoint (Statuspage.io JSON, Riot's status API, etc.) and read their own incident feed.
- Se considera CAÍDO si
- The publisher reports a major or critical indicator, or the adapter returns a protocol error.
- Se considera DEGRADADO si
- The publisher reports minor issues or maintenance. Active incidents are listed even when the overall indicator is green.
- Detalle
- Publisher checks differ from direct probing: we inherit the publisher's own classification. If Atlassian says "all systems operational" while users can't connect, our check will show up, the signal is theirs, not ours.
- Cadencia
- Every 5 minutes, in parallel across 4 independent probe methods (HTTP/1.1 with strict TLS, HTTP/2, a browser User-Agent GET, and a curl-style HEAD) from our edge network. We check probe diversity, not geography — if a site blocks a non-browser User-Agent or only speaks HTTP/1.1, the four cards show it.
- Objetivos con límite de tasa
- If a host returns 429 or consistently drops connections from our IPs, we cap retries at 3 and report the last observed status, we do not flood the target to confirm the outage.
- Fuente de datos
- Our verdict is based on direct multi-method probes, every result above is a live network request, never a Twitter mention or DownDetector aggregate. User reports, when shown, appear separately below as a supplementary signal and are never used to determine the up/down verdict.