Skip to content

Outage tracker / Roblox

Is Roblox down?

I'm having a problem

Vendor reports no incidentWhat Roblox reports

Roblox reports no incident on its status page.

As of the last successful poll, 2026-10-19 20:46 UTC.

Roblox's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked moments ago

Our checks of Roblox pass from all 10 regions we check.

As of Oct 19, 2026, 8:55 PM UTC, RealUptime's checks of Roblox passed in all 10 regions that returned a reading.

Front-door and live API checks

Email me when Roblox reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Roblox's own statement from its status page, with our regional reading beside it.

our check readinglive · checked Oct 19, 2026, 8:55 PM UTC
US-East534 msChecks passing
US-West1858 msChecks passing
Europe293 msChecks passing
Asia-Pacific1271 msChecks passing
US-Central1394 msChecks passing
Canada875 msChecks passing
UK469 msChecks passing
Southeast Asia304 msChecks passing
Australia1359 msChecks passing
South America839 msChecks passing
their status pagetheir claim, not our reading

Roblox publishes no status feed we can read, so the only reading here is our check reading on the left.

Roblox response time, by region

US-East
787msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 357ms2026-09-21 UTC: p95 365ms2026-09-22 UTC: p95 330ms2026-09-23 UTC: p95 309ms2026-09-24 UTC: p95 390ms2026-09-25 UTC: p95 338ms2026-09-26 UTC: p95 340ms2026-09-27 UTC: p95 288ms2026-09-28 UTC: p95 378ms2026-09-29 UTC: p95 353ms2026-09-30 UTC: p95 348ms2026-10-01 UTC: p95 375ms2026-10-02 UTC: p95 461ms2026-10-03 UTC: p95 333ms2026-10-04 UTC: p95 336ms2026-10-05 UTC: p95 302ms2026-10-06 UTC: p95 342ms2026-10-07 UTC: p95 272ms2026-10-08 UTC: p95 342ms2026-10-09 UTC: p95 336ms2026-10-10 UTC: p95 310ms2026-10-11 UTC: p95 274ms2026-10-12 UTC: p95 350ms2026-10-13 UTC: p95 329ms2026-10-14 UTC: p95 337ms2026-10-15 UTC: p95 348ms2026-10-16 UTC: p95 396ms2026-10-17 UTC: p95 627ms2026-10-18 UTC: p95 752ms2026-10-19 UTC: p95 787ms
Sep 20Oct 4Oct 19
US-West
2.1sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.7s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 1.6s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.5s2026-10-06 UTC: p95 1.4s2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.1s
Sep 20Oct 4Oct 19
Europe
677msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 252ms2026-09-21 UTC: p95 268ms2026-09-22 UTC: p95 291ms2026-09-23 UTC: p95 288ms2026-09-24 UTC: p95 323ms2026-09-25 UTC: p95 410ms2026-09-26 UTC: p95 352ms2026-09-27 UTC: p95 328ms2026-09-28 UTC: p95 376ms2026-09-29 UTC: p95 358ms2026-09-30 UTC: p95 331ms2026-10-01 UTC: p95 342ms2026-10-02 UTC: p95 433ms2026-10-03 UTC: p95 380ms2026-10-04 UTC: p95 332ms2026-10-05 UTC: p95 327ms2026-10-06 UTC: p95 314ms2026-10-07 UTC: p95 470ms2026-10-08 UTC: p95 311ms2026-10-09 UTC: p95 282ms2026-10-10 UTC: p95 339ms2026-10-11 UTC: p95 256ms2026-10-12 UTC: p95 325ms2026-10-13 UTC: p95 279ms2026-10-14 UTC: p95 298ms2026-10-15 UTC: p95 327ms2026-10-16 UTC: p95 324ms2026-10-17 UTC: p95 398ms2026-10-18 UTC: p95 513ms2026-10-19 UTC: p95 677ms
Sep 20Oct 4Oct 19
Asia-Pacific
1.7sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 891ms2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 937ms2026-09-24 UTC: p95 965ms2026-09-25 UTC: p95 994ms2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 914ms2026-10-02 UTC: p95 851ms2026-10-03 UTC: p95 844ms2026-10-04 UTC: p95 884ms2026-10-05 UTC: p95 862ms2026-10-06 UTC: p95 980ms2026-10-07 UTC: p95 836ms2026-10-08 UTC: p95 881ms2026-10-09 UTC: p95 969ms2026-10-10 UTC: p95 816ms2026-10-11 UTC: p95 883ms2026-10-12 UTC: p95 868ms2026-10-13 UTC: p95 870ms2026-10-14 UTC: p95 846ms2026-10-15 UTC: p95 936ms2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.7s
Sep 20Oct 4Oct 19
US-Central
2.1sp95 · latest
2.5s1.3s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.8s2026-09-21 UTC: p95 1.7s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 1.5s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.6s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.5s2026-10-06 UTC: p95 1.5s2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.6s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.1s
Sep 20Oct 4Oct 19
Canada
1.7sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.4s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.7s
Sep 20Oct 4Oct 19
UK
815msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 306ms2026-09-21 UTC: p95 417ms2026-09-22 UTC: p95 392ms2026-09-23 UTC: p95 519ms2026-09-24 UTC: p95 605ms2026-09-25 UTC: p95 554ms2026-09-26 UTC: p95 570ms2026-09-27 UTC: p95 506ms2026-09-28 UTC: p95 475ms2026-09-29 UTC: p95 471ms2026-09-30 UTC: p95 463ms2026-10-01 UTC: p95 492ms2026-10-02 UTC: p95 413ms2026-10-03 UTC: p95 379ms2026-10-04 UTC: p95 423ms2026-10-05 UTC: p95 403ms2026-10-06 UTC: p95 456ms2026-10-07 UTC: p95 452ms2026-10-08 UTC: p95 396ms2026-10-09 UTC: p95 399ms2026-10-10 UTC: p95 397ms2026-10-11 UTC: p95 466ms2026-10-12 UTC: p95 437ms2026-10-13 UTC: p95 454ms2026-10-14 UTC: p95 396ms2026-10-15 UTC: p95 643ms2026-10-16 UTC: p95 507ms2026-10-17 UTC: p95 698ms2026-10-18 UTC: p95 785ms2026-10-19 UTC: p95 815ms
Sep 20Oct 4Oct 19
Southeast Asia
2.2sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 952ms2026-10-04 UTC: p95 912ms2026-10-05 UTC: p95 922ms2026-10-06 UTC: p95 898ms2026-10-07 UTC: p95 973ms2026-10-08 UTC: p95 943ms2026-10-09 UTC: p95 922ms2026-10-10 UTC: p95 800ms2026-10-11 UTC: p95 997ms2026-10-12 UTC: p95 823ms2026-10-13 UTC: p95 882ms2026-10-14 UTC: p95 868ms2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 827ms2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.2s
Sep 20Oct 4Oct 19
Australia
2.6sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.8s2026-09-21 UTC: p95 1.9s2026-09-22 UTC: p95 1.8s2026-09-23 UTC: p95 1.6s2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.7s2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.7s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.8s2026-10-06 UTC: p95 1.6s2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.6s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.6s2026-10-17 UTC: p95 2.2s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.6s
Sep 20Oct 4Oct 19
South America
1.8sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 941ms2026-09-21 UTC: p95 895ms2026-09-22 UTC: p95 780ms2026-09-23 UTC: p95 997ms2026-09-24 UTC: p95 920ms2026-09-25 UTC: p95 920ms2026-09-26 UTC: p95 956ms2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 934ms2026-09-29 UTC: p95 904ms2026-09-30 UTC: p95 994ms2026-10-01 UTC: p95 934ms2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 927ms2026-10-07 UTC: p95 778ms2026-10-08 UTC: p95 940ms2026-10-09 UTC: p95 994ms2026-10-10 UTC: p95 996ms2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 962ms2026-10-15 UTC: p95 873ms2026-10-16 UTC: p95 707ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.8s
Sep 20Oct 4Oct 19

Check your own site while you wait on Roblox

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Roblox. It cannot diagnose Roblox's own systems.

What we measured, function by function

Roblox answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 534msstatus code: 200checked: Oct 19, 2026, 8:55 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Roblox normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1858msstatus code: 200checked: Oct 19, 2026, 8:53 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Roblox normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 1394msstatus code: 200checked: Oct 19, 2026, 8:52 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Roblox normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 875msstatus code: 200checked: Oct 19, 2026, 8:51 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Roblox normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 839msstatus code: 200checked: Oct 19, 2026, 8:52 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Roblox normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 293msstatus code: 200checked: Oct 19, 2026, 8:53 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Roblox normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 469msstatus code: 200checked: Oct 19, 2026, 8:53 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Roblox normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1271msstatus code: 200checked: Oct 19, 2026, 8:54 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Roblox normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 304msstatus code: 200checked: Oct 19, 2026, 8:53 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Roblox normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1359msstatus code: 200checked: Oct 19, 2026, 8:54 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Roblox normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Roblox, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We started counting reports for Roblox on September 9, 2026.

Recent probe events

Site issue, 9mdeclared on their status page2026-10-05
Studio publish issues, 3h 13mdeclared on their status page2026-09-28
Subset of Asset uploads are disabled, 3h 19mdeclared on their status page2026-08-07
Issue Publishing Avatar Accessories, 6h 34mdeclared on their status page2026-07-25
Mitigated: Current issues with the platform, 49mdeclared on their status page2026-06-29
Issue opening Roblox on certain platforms, 49mdeclared on their status page2026-06-02
Players and users may be unable to connect at this time, 1h 17mdeclared on their status page2026-05-07
Issues with loading web views, 7h 34mdeclared on their status page2026-04-26

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Roblox since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Roblox covering any window you pick, with our check readings and Roblox's own claim at the time, side by side.

Full check history for Roblox: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

Roblox uptime by RealUptime's checksLive, from this page's own readings.
[![Roblox uptime by RealUptime's checks](https://realuptime.io/outages/roblox/badge.svg?days=30)](https://realuptime.io/outages/roblox)
<a href="https://realuptime.io/outages/roblox"><img src="https://realuptime.io/outages/roblox/badge.svg?days=30" alt="Roblox uptime by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Roblox down?", https://realuptime.io/outages/roblox. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional: live API
https://games.roblox.com/v1/games/multiget-playability-status?universeIds=13058
secondaryfunctional: live API
https://users.roblox.com/v1/users/1
secondary
https://www.roblox.com/

What our check can and cannot see

A pass means the service returned real data from its own backend, with the content we expect. It does not show that every feature, account type or region works, or that sign-in is healthy.

Host checked: games.roblox.com

RealUptime is not affiliated with Roblox; the name identifies what we checked, and nothing here speaks for Roblox's own team. We send a single web request to Roblox from 10 regions on our own schedule and time the response. We do not see inside Roblox's systems, do not use an account or real transaction, and are not the same signal Roblox's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Roblox is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.