发布方状态 · statuspage

Roblox 状态

Live incidents and maintenance pulled from the publisher's official status page.

等待中
Roblox · roblox
发布方状态源等待中
via statuspage
0.00% uptimelast 30 days
2026-06-29: no data2026-06-30: no data2026-07-01: no data2026-07-02: no data2026-07-03: no data2026-07-04: no data2026-07-05: no data2026-07-06: no data2026-07-07: no data2026-07-08: no data2026-07-09: no data2026-07-10: no data2026-07-11: no data2026-07-12: no data2026-07-13: no data2026-07-14: no data2026-07-15: no data2026-07-16: no data2026-07-17: no data2026-07-18: no data2026-07-19: no data2026-07-20: no data2026-07-21: no data2026-07-22: no data2026-07-23: no data2026-07-24: no data2026-07-25: no data2026-07-26: no data2026-07-27: no data2026-07-28: partial outage, 0.0% uptime, 5 checks
30 days agocollecting data · 1/30 daystoday
Checked 8s ago single-source feed every 5 min · publisher feed direct probe, not crowd-reported

发布方状态

Indicator
error
Description
Live status feed is temporarily unavailable.
Source
https://status.roblox.com
Adapter
statuspage
结果解读

Publisher status data not yet available.

A poll is in progress or the upstream feed returned an error. Refresh in a few seconds.

下一步操作

First probe pending

We're running your check now. Reload in a few seconds to see live data.

官方状态页

status.roblox.com Roblox's official status page

FAQ

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.

Roblox status
<a href="https://isitdown.io/publisher/roblox"><img src="https://isitdown.io/badge/publisher/roblox.svg" alt="Roblox status"></a>

相关

Epic Games / FortniteDiscordCloudflareGitHubTwitchRedditOpenAIAnthropic / Claude

方法论

探测方式
We poll the publisher's official status page endpoint (Statuspage.io JSON, Riot's status API, etc.) and read their own incident feed.
计为宕机的条件
The publisher reports a major or critical indicator, or the adapter returns a protocol error.
计为降级的条件
The publisher reports minor issues or maintenance. Active incidents are listed even when the overall indicator is green.
细节
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.
频率
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.
限速目标
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.
数据来源
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.
JSON: /check?target=roblox&format=json Share: https://isitdown.io/publisher/roblox