Skip to content

Outage tracker / Riot Games (League of Legends / Valorant)

Is Riot Games (League of Legends / Valorant) down?

I'm having a problem

Operationalchecked 4 minutes ago

We reached Riot Games (League of Legends / Valorant) from all 10 regions we check.

As of Oct 5, 2026, 9:01 PM UTC, Riot Games (League of Legends / Valorant) answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 58 days we have measured Riot Games (League of Legends / Valorant) (since Aug 8, 2026).

Email me the next time we see Riot Games (League of Legends / Valorant) go down

Measured by our own probes from ten regions, not Riot Games (League of Legends / Valorant)'s status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

our independent probeslive · checked Oct 5, 2026, 9:01 PM UTC
US-East192 msOperational
US-West216 msOperational
Europe301 msOperational
Asia-Pacific864 msOperational
US-Central380 msOperational
Canada278 msOperational
UK389 msOperational
Southeast Asia628 msOperational
Australia315 msOperational
South America846 msOperational
their status pagetheir claim, not our reading

Riot Games (League of Legends / Valorant) publishes no status feed we can read, so the only independent reading here is ours on the left.

Riot Games (League of Legends / Valorant) response time, by region

US-East
313msp95 · 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-06 UTC: p95 302ms2026-09-07 UTC: p95 332ms2026-09-08 UTC: p95 325ms2026-09-09 UTC: p95 356ms2026-09-10 UTC: p95 322ms2026-09-11 UTC: p95 366ms2026-09-12 UTC: p95 247ms2026-09-13 UTC: p95 248ms2026-09-14 UTC: p95 243ms2026-09-15 UTC: p95 306ms2026-09-16 UTC: p95 345ms2026-09-17 UTC: p95 373ms2026-09-18 UTC: p95 363ms2026-09-19 UTC: p95 380ms2026-09-20 UTC: p95 316ms2026-09-21 UTC: p95 326ms2026-09-22 UTC: p95 332ms2026-09-23 UTC: p95 766ms2026-09-24 UTC: p95 729ms2026-09-25 UTC: p95 410ms2026-09-26 UTC: p95 436ms2026-09-27 UTC: p95 278ms2026-09-28 UTC: p95 317ms2026-09-29 UTC: p95 363ms2026-09-30 UTC: p95 328ms2026-10-01 UTC: p95 339ms2026-10-02 UTC: p95 291ms2026-10-03 UTC: p95 258ms2026-10-04 UTC: p95 345ms2026-10-05 UTC: p95 313ms
Sep 6Sep 20Oct 5
US-West
429msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 384ms2026-09-07 UTC: p95 255ms2026-09-08 UTC: p95 318ms2026-09-09 UTC: p95 413ms2026-09-10 UTC: p95 319ms2026-09-11 UTC: p95 224ms2026-09-12 UTC: p95 256ms2026-09-13 UTC: p95 232ms2026-09-14 UTC: p95 362ms2026-09-15 UTC: p95 521ms2026-09-16 UTC: p95 428ms2026-09-17 UTC: p95 339ms2026-09-18 UTC: p95 433ms2026-09-19 UTC: p95 401ms2026-09-20 UTC: p95 432ms2026-09-21 UTC: p95 512ms2026-09-22 UTC: p95 609ms2026-09-23 UTC: p95 549ms2026-09-24 UTC: p95 453ms2026-09-25 UTC: p95 685ms2026-09-26 UTC: p95 715ms2026-09-27 UTC: p95 610ms2026-09-28 UTC: p95 655ms2026-09-29 UTC: p95 677ms2026-09-30 UTC: p95 534ms2026-10-01 UTC: p95 635ms2026-10-02 UTC: p95 653ms2026-10-03 UTC: p95 693ms2026-10-04 UTC: p95 600ms2026-10-05 UTC: p95 429ms
Sep 6Sep 20Oct 5
Europe
411msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 672ms2026-09-07 UTC: p95 789ms2026-09-08 UTC: p95 768ms2026-09-09 UTC: p95 902ms2026-09-10 UTC: p95 780ms2026-09-11 UTC: p95 629ms2026-09-12 UTC: p95 521ms2026-09-13 UTC: p95 569ms2026-09-14 UTC: p95 662ms2026-09-15 UTC: p95 786ms2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 928ms2026-09-19 UTC: p95 984ms2026-09-20 UTC: p95 865ms2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 890ms2026-09-24 UTC: p95 996ms2026-09-25 UTC: p95 913ms2026-09-26 UTC: p95 757ms2026-09-27 UTC: p95 631ms2026-09-28 UTC: p95 799ms2026-09-29 UTC: p95 847ms2026-09-30 UTC: p95 505ms2026-10-01 UTC: p95 677ms2026-10-02 UTC: p95 492ms2026-10-03 UTC: p95 526ms2026-10-04 UTC: p95 526ms2026-10-05 UTC: p95 411ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.2sp95 · 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-06 UTC: p95 1.0s2026-09-07 UTC: p95 927ms2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 888ms2026-09-12 UTC: p95 948ms2026-09-13 UTC: p95 808ms2026-09-14 UTC: p95 1.0s2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 848ms2026-09-20 UTC: p95 559ms2026-09-21 UTC: p95 936ms2026-09-22 UTC: p95 998ms2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 925ms2026-09-25 UTC: p95 970ms2026-09-26 UTC: p95 895ms2026-09-27 UTC: p95 519ms2026-09-28 UTC: p95 454ms2026-09-29 UTC: p95 431ms2026-09-30 UTC: p95 498ms2026-10-01 UTC: p95 689ms2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5
US-Central
324msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 431ms2026-09-07 UTC: p95 523ms2026-09-08 UTC: p95 494ms2026-09-09 UTC: p95 510ms2026-09-10 UTC: p95 309ms2026-09-11 UTC: p95 357ms2026-09-12 UTC: p95 292ms2026-09-13 UTC: p95 324ms2026-09-14 UTC: p95 342ms2026-09-15 UTC: p95 375ms2026-09-16 UTC: p95 281ms2026-09-17 UTC: p95 310ms2026-09-18 UTC: p95 314ms2026-09-19 UTC: p95 304ms2026-09-20 UTC: p95 269ms2026-09-21 UTC: p95 296ms2026-09-22 UTC: p95 383ms2026-09-23 UTC: p95 569ms2026-09-24 UTC: p95 461ms2026-09-25 UTC: p95 333ms2026-09-26 UTC: p95 346ms2026-09-27 UTC: p95 362ms2026-09-28 UTC: p95 394ms2026-09-29 UTC: p95 441ms2026-09-30 UTC: p95 409ms2026-10-01 UTC: p95 426ms2026-10-02 UTC: p95 245ms2026-10-03 UTC: p95 285ms2026-10-04 UTC: p95 351ms2026-10-05 UTC: p95 324ms
Sep 6Sep 20Oct 5
Canada
420msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 617ms2026-09-07 UTC: p95 528ms2026-09-08 UTC: p95 636ms2026-09-09 UTC: p95 628ms2026-09-10 UTC: p95 640ms2026-09-11 UTC: p95 610ms2026-09-12 UTC: p95 575ms2026-09-13 UTC: p95 619ms2026-09-14 UTC: p95 598ms2026-09-15 UTC: p95 552ms2026-09-16 UTC: p95 526ms2026-09-17 UTC: p95 496ms2026-09-18 UTC: p95 513ms2026-09-19 UTC: p95 530ms2026-09-20 UTC: p95 466ms2026-09-21 UTC: p95 569ms2026-09-22 UTC: p95 485ms2026-09-23 UTC: p95 494ms2026-09-24 UTC: p95 399ms2026-09-25 UTC: p95 718ms2026-09-26 UTC: p95 363ms2026-09-27 UTC: p95 364ms2026-09-28 UTC: p95 377ms2026-09-29 UTC: p95 334ms2026-09-30 UTC: p95 467ms2026-10-01 UTC: p95 449ms2026-10-02 UTC: p95 442ms2026-10-03 UTC: p95 349ms2026-10-04 UTC: p95 296ms2026-10-05 UTC: p95 420ms
Sep 6Sep 20Oct 5
UK
424msp95 · 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-06 UTC: p95 271ms2026-09-07 UTC: p95 249ms2026-09-08 UTC: p95 243ms2026-09-09 UTC: p95 386ms2026-09-10 UTC: p95 546ms2026-09-11 UTC: p95 429ms2026-09-12 UTC: p95 388ms2026-09-13 UTC: p95 420ms2026-09-14 UTC: p95 397ms2026-09-15 UTC: p95 443ms2026-09-16 UTC: p95 527ms2026-09-17 UTC: p95 677ms2026-09-18 UTC: p95 506ms2026-09-19 UTC: p95 628ms2026-09-20 UTC: p95 437ms2026-09-21 UTC: p95 555ms2026-09-22 UTC: p95 520ms2026-09-23 UTC: p95 548ms2026-09-24 UTC: p95 684ms2026-09-25 UTC: p95 550ms2026-09-26 UTC: p95 652ms2026-09-27 UTC: p95 644ms2026-09-28 UTC: p95 662ms2026-09-29 UTC: p95 652ms2026-09-30 UTC: p95 526ms2026-10-01 UTC: p95 670ms2026-10-02 UTC: p95 750ms2026-10-03 UTC: p95 635ms2026-10-04 UTC: p95 593ms2026-10-05 UTC: p95 424ms
Sep 6Sep 20Oct 5
Southeast Asia
1.1sp95 · 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-06 UTC: p95 647ms2026-09-07 UTC: p95 829ms2026-09-08 UTC: p95 711ms2026-09-09 UTC: p95 908ms2026-09-10 UTC: p95 784ms2026-09-11 UTC: p95 946ms2026-09-12 UTC: p95 876ms2026-09-13 UTC: p95 821ms2026-09-14 UTC: p95 906ms2026-09-15 UTC: p95 794ms2026-09-16 UTC: p95 791ms2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.5s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 2.0s2026-09-28 UTC: p95 1.8s2026-09-29 UTC: p95 1.7s2026-09-30 UTC: p95 1.7s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
Australia
616msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.7s2026-09-07 UTC: p95 1.8s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.5s2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 1.7s2026-09-12 UTC: p95 2.0s2026-09-13 UTC: p95 1.9s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.5s2026-09-16 UTC: p95 877ms2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 563ms2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 862ms2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 602ms2026-09-30 UTC: p95 320ms2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 979ms2026-10-05 UTC: p95 616ms
Sep 6Sep 20Oct 5
South America
1.1sp95 · 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-06 UTC: p95 894ms2026-09-07 UTC: p95 979ms2026-09-08 UTC: p95 951ms2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.7s2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.3s2026-09-20 UTC: p95 810ms2026-09-21 UTC: p95 870ms2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 1s2026-09-25 UTC: p95 835ms2026-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.2s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5

Is it Riot Games (League of Legends / Valorant), or is it you?

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 Riot Games (League of Legends / Valorant) -- it cannot diagnose Riot Games (League of Legends / Valorant)'s own systems.

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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 192msstatus code: 200checked: Oct 5, 2026, 9:01 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Riot Games (League of Legends / Valorant) normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 216msstatus code: 200checked: Oct 5, 2026, 8:59 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Riot Games (League of Legends / Valorant) normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 380msstatus code: 200checked: Oct 5, 2026, 8:46 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Riot Games (League of Legends / Valorant) normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 278msstatus code: 200checked: Oct 5, 2026, 9:00 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Riot Games (League of Legends / Valorant) normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 846msstatus code: 200checked: Oct 5, 2026, 8:46 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Riot Games (League of Legends / Valorant) normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 301msstatus code: 200checked: Oct 5, 2026, 9:00 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Riot Games (League of Legends / Valorant) normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 389msstatus code: 200checked: Oct 5, 2026, 8:49 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Riot Games (League of Legends / Valorant) normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 864msstatus code: 200checked: Oct 5, 2026, 9:01 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Riot Games (League of Legends / Valorant) normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 628msstatus code: 200checked: Oct 5, 2026, 8:58 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Riot Games (League of Legends / Valorant) normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 315msstatus code: 200checked: Oct 5, 2026, 8:49 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Riot Games (League of Legends / Valorant) 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 Riot Games (League of Legends / Valorant), 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 Riot Games (League of Legends / Valorant) on September 16, 2026.

Recent outages

No outages on record yet for Riot Games (League of Legends / Valorant).

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

We have been measuring Riot Games (League of Legends / Valorant) since August 8, 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 Riot Games (League of Legends / Valorant) covering any window you pick, with our measurements and Riot Games (League of Legends / Valorant)'s own claim at the time, side by side.

Full availability history for Riot Games (League of Legends / Valorant): 90-day availability by region, month-by-month uptime, and every incident on record.

Put this badge in your README

Riot Games (League of Legends / Valorant) uptime measured by RealUptimeLive, from this page's own readings.
[![Riot Games (League of Legends / Valorant) uptime measured by RealUptime](https://realuptime.io/outages/riot-games/badge.svg?days=30)](https://realuptime.io/outages/riot-games)
<a href="https://realuptime.io/outages/riot-games"><img src="https://realuptime.io/outages/riot-games/badge.svg?days=30" alt="Riot Games (League of Legends / Valorant) uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and 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: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Riot Games (League of Legends / Valorant)'s SLA implies, from our measurement

At or above your target

We measured none of downtime for Riot Games (League of Legends / Valorant) over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Riot Games (League of Legends / Valorant)'s SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://valorant-api.com/v1/version
secondary
https://status.riotgames.com/
RealUptime is not affiliated with Riot Games (League of Legends / Valorant); the name identifies what we measured, and nothing here speaks for Riot Games (League of Legends / Valorant)'s own team. We send a single web request to Riot Games (League of Legends / Valorant) from 10 regions on our own schedule and time the response. We do not see inside Riot Games (League of Legends / Valorant)'s systems, do not use an account or real transaction, and are not the same signal Riot Games (League of Legends / Valorant)'s own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Riot Games (League of Legends / Valorant) is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.