Skip to content

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

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

I'm having a problem

Checks passingchecked 3 minutes ago

Our checks of Riot Games (League of Legends / Valorant) pass from all 10 regions we check.

As of Nov 5, 2026, 2:48 PM UTC, RealUptime's checks of Riot Games (League of Legends / Valorant) passed in all 10 regions that returned a reading.

Front-door and live API checks

Our checks of Riot Games (League of Legends / Valorant) did not fail from two or more distant regions in the 89 days we have checked it (since Aug 8, 2026). This does not show Riot Games (League of Legends / Valorant) works for users.

Riot Games (League of Legends / Valorant)'s own status page reports "New Update Available." That is their claim, not our measurement: our probes are currently reaching Riot Games (League of Legends / Valorant), and an incident they declare can affect parts of the service our checks do not exercise. We show both and never merge them.

Email me when our checks of Riot Games (League of Legends / Valorant) fail from two or more distant regions

One email when our checks of Riot Games (League of Legends / Valorant) fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not Riot Games (League of Legends / Valorant)'s official status.

our check readinglive · checked Nov 5, 2026, 2:48 PM UTC
US-East860 msChecks passing
US-West1364 msChecks passing
Europe959 msChecks passing
Asia-Pacific873 msChecks passing
US-Central710 msChecks passing
Canada960 msChecks passing
UK123 msChecks passing
Southeast Asia1169 msChecks passing
Australia1851 msChecks passing
South America1404 msChecks passing
their status pagetheir claim, not our reading

Riot Games (League of Legends / Valorant) reports: Minor incident (“New Update Available”)

from Riot Games (League of Legends / Valorant)'s own status page, checked Nov 5, 2026, 1:56 PM UTC
Riot Games (League of Legends / Valorant)'s status page reports New Update Available. Our checks of Riot Games (League of Legends / Valorant) currently pass with normal latency. Our checks currently pass from all 10 regions. These observations can coexist: a partial error-rate degradation on their side does not have to affect every request. Our checks measure whether a single request succeeds, not the vendor's internal error rate, so this can happen when an issue affects only part of a service that our simple check does not exercise. We show the vendor's report and our check reading side by side. A check can miss problems that users see. Read both before you draw a conclusion.

This is Riot Games (League of Legends / Valorant)'s own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

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

US-East
2.2sp95 · latest
5s2.5s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 441ms2026-10-08 UTC: p95 327ms2026-10-09 UTC: p95 299ms2026-10-10 UTC: p95 304ms2026-10-11 UTC: p95 276ms2026-10-12 UTC: p95 241ms2026-10-13 UTC: p95 442ms2026-10-14 UTC: p95 462ms2026-10-15 UTC: p95 530ms2026-10-16 UTC: p95 548ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 685ms2026-10-23 UTC: p95 777ms2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 2.2s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 4.1s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 491ms2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 2.8s2026-11-05 UTC: p95 2.2s
Oct 7Oct 21Nov 5
US-West
1.9sp95 · 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-10-07 UTC: p95 578ms2026-10-08 UTC: p95 608ms2026-10-09 UTC: p95 638ms2026-10-10 UTC: p95 500ms2026-10-11 UTC: p95 361ms2026-10-12 UTC: p95 741ms2026-10-13 UTC: p95 867ms2026-10-14 UTC: p95 446ms2026-10-15 UTC: p95 445ms2026-10-16 UTC: p95 484ms2026-10-17 UTC: p95 995ms2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 1.6s2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 1.5s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 1.8s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.2s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
Europe
1.9sp95 · 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-10-07 UTC: p95 502ms2026-10-08 UTC: p95 504ms2026-10-09 UTC: p95 491ms2026-10-10 UTC: p95 584ms2026-10-11 UTC: p95 823ms2026-10-12 UTC: p95 777ms2026-10-13 UTC: p95 424ms2026-10-14 UTC: p95 608ms2026-10-15 UTC: p95 540ms2026-10-16 UTC: p95 386ms2026-10-17 UTC: p95 684ms2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 865ms2026-10-25 UTC: p95 840ms2026-10-26 UTC: p95 961ms2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.0s2026-10-31 UTC: p95 536ms2026-11-01 UTC: p95 575ms2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
Asia-Pacific
3.0sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 930ms2026-10-09 UTC: p95 905ms2026-10-10 UTC: p95 925ms2026-10-11 UTC: p95 867ms2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 984ms2026-10-14 UTC: p95 874ms2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.1s2026-10-21 UTC: p95 2.2s2026-10-22 UTC: p95 2.3s2026-10-23 UTC: p95 2.6s2026-10-24 UTC: p95 2.5s2026-10-25 UTC: p95 2.3s2026-10-26 UTC: p95 2.7s2026-10-27 UTC: p95 2.8s2026-10-28 UTC: p95 2.2s2026-10-29 UTC: p95 2.3s2026-10-30 UTC: p95 2.5s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.3s2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 2.3s2026-11-04 UTC: p95 2.7s2026-11-05 UTC: p95 3.0s
Oct 7Oct 21Nov 5
US-Central
1.3sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 377ms2026-10-08 UTC: p95 334ms2026-10-09 UTC: p95 445ms2026-10-10 UTC: p95 382ms2026-10-11 UTC: p95 359ms2026-10-12 UTC: p95 433ms2026-10-13 UTC: p95 587ms2026-10-14 UTC: p95 440ms2026-10-15 UTC: p95 524ms2026-10-16 UTC: p95 537ms2026-10-17 UTC: p95 639ms2026-10-18 UTC: p95 898ms2026-10-19 UTC: p95 970ms2026-10-20 UTC: p95 969ms2026-10-21 UTC: p95 861ms2026-10-22 UTC: p95 866ms2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.1s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 929ms2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 842ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 753ms2026-11-04 UTC: p95 873ms2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
Canada
994msp95 · 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-10-07 UTC: p95 365ms2026-10-08 UTC: p95 479ms2026-10-09 UTC: p95 480ms2026-10-10 UTC: p95 339ms2026-10-11 UTC: p95 420ms2026-10-12 UTC: p95 437ms2026-10-13 UTC: p95 608ms2026-10-14 UTC: p95 507ms2026-10-15 UTC: p95 411ms2026-10-16 UTC: p95 560ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 988ms2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 994ms
Oct 7Oct 21Nov 5
UK
835msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 504ms2026-10-08 UTC: p95 604ms2026-10-09 UTC: p95 496ms2026-10-10 UTC: p95 431ms2026-10-11 UTC: p95 544ms2026-10-12 UTC: p95 554ms2026-10-13 UTC: p95 362ms2026-10-14 UTC: p95 389ms2026-10-15 UTC: p95 386ms2026-10-16 UTC: p95 353ms2026-10-17 UTC: p95 788ms2026-10-18 UTC: p95 805ms2026-10-19 UTC: p95 1s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 834ms2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 943ms2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.0s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 201ms2026-11-01 UTC: p95 292ms2026-11-02 UTC: p95 629ms2026-11-03 UTC: p95 751ms2026-11-04 UTC: p95 832ms2026-11-05 UTC: p95 835ms
Oct 7Oct 21Nov 5
Southeast Asia
1.9sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 901ms2026-10-08 UTC: p95 628ms2026-10-09 UTC: p95 621ms2026-10-10 UTC: p95 833ms2026-10-11 UTC: p95 824ms2026-10-12 UTC: p95 883ms2026-10-13 UTC: p95 812ms2026-10-14 UTC: p95 916ms2026-10-15 UTC: p95 772ms2026-10-16 UTC: p95 827ms2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 3.1s2026-10-23 UTC: p95 2.1s2026-10-24 UTC: p95 2.0s2026-10-25 UTC: p95 2.1s2026-10-26 UTC: p95 2.2s2026-10-27 UTC: p95 2.0s2026-10-28 UTC: p95 1.9s2026-10-29 UTC: p95 2.0s2026-10-30 UTC: p95 2.1s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.2s2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 2.5s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
Australia
2.2sp95 · 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-10-07 UTC: p95 729ms2026-10-08 UTC: p95 563ms2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 937ms2026-10-14 UTC: p95 808ms2026-10-15 UTC: p95 867ms2026-10-16 UTC: p95 919ms2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.4s2026-10-19 UTC: p95 2.6s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 2.5s2026-10-22 UTC: p95 2.4s2026-10-23 UTC: p95 2.3s2026-10-24 UTC: p95 2.4s2026-10-25 UTC: p95 2.3s2026-10-26 UTC: p95 2.2s2026-10-27 UTC: p95 2.0s2026-10-28 UTC: p95 2.3s2026-10-29 UTC: p95 2.6s2026-10-30 UTC: p95 3.2s2026-10-31 UTC: p95 3.1s2026-11-01 UTC: p95 741ms2026-11-02 UTC: p95 818ms2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 2.6s2026-11-05 UTC: p95 2.2s
Oct 7Oct 21Nov 5
South America
2.6sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.6s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 2.4s2026-10-23 UTC: p95 8.3s2026-10-24 UTC: p95 2.2s2026-10-25 UTC: p95 2.3s2026-10-26 UTC: p95 2.6s2026-10-27 UTC: p95 2.5s2026-10-28 UTC: p95 2.4s2026-10-29 UTC: p95 2.8s2026-10-30 UTC: p95 2.5s2026-10-31 UTC: p95 3.0s2026-11-01 UTC: p95 3.0s2026-11-02 UTC: p95 2.7s2026-11-03 UTC: p95 2.7s2026-11-04 UTC: p95 2.5s2026-11-05 UTC: p95 2.6s
Oct 7Oct 21Nov 5

Check your own site while you wait on Riot Games (League of Legends / Valorant)

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 we measured, function by function

Riot Games (League of Legends / Valorant) 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 auth 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
  • AuthprimaryUS-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
  • Client configUS-East: Awaiting dataUS-West: Checks passingEurope: Awaiting dataAsia-Pacific: Checks passingUS-Central: Awaiting dataCanada: Checks passingUK: Checks passingSoutheast Asia: Awaiting dataAustralia: Checks passingSouth America: Checks passing
  • League dataUS-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
  • League of LegendsUS-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
  • VALORANTUS-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: 860msstatus code: 200checked: Nov 5, 2026, 2:44 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
      Checks passinglatency: 1364msstatus code: 200checked: Nov 5, 2026, 2:41 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
      Checks passinglatency: 710msstatus code: 200checked: Nov 5, 2026, 2:33 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
      Checks passinglatency: 960msstatus code: 200checked: Nov 5, 2026, 2:33 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
    Checks passinglatency: 1404msstatus code: 200checked: Nov 5, 2026, 2:33 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 959msstatus code: 200checked: Nov 5, 2026, 2:38 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
      Checks passinglatency: 123msstatus code: 200checked: Nov 5, 2026, 2:48 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 873msstatus code: 200checked: Nov 5, 2026, 2:38 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
      Checks passinglatency: 1169msstatus code: 200checked: Nov 5, 2026, 2:34 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
      Checks passinglatency: 1851msstatus code: 200checked: Nov 5, 2026, 2:35 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 probe events

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

check 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 check readings and Riot Games (League of Legends / Valorant)'s own claim at the time, side by side.

Full check history for Riot Games (League of Legends / Valorant): 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

Riot Games (League of Legends / Valorant) uptime by RealUptime's checksLive, from this page's own readings.
[![Riot Games (League of Legends / Valorant) uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Riot Games (League of Legends / Valorant) down?", https://realuptime.io/outages/riot-games. The readings change with every check, so give the date you read them.

How our checks compare with Riot Games (League of Legends / Valorant)'s stated SLA

At or above your target

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

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, 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: auth surface
https://auth.riotgames.com/.well-known/openid-configuration
secondary
https://status.riotgames.com/
secondary
https://lol.secure.dyn.riotcdn.net/channels/public/x/status/na1.json
secondary
https://valorant.secure.dyn.riotcdn.net/channels/public/x/status/na.json
secondary
https://clientconfig.rpg.riotgames.com/api/v1/config/public
secondary
https://ddragon.leagueoflegends.com/api/versions.json

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: auth.riotgames.com

RealUptime is not affiliated with Riot Games (League of Legends / Valorant); the name identifies what we checked, 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 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.