Skip to content

Outage tracker / RubyGems

Is RubyGems down?

I'm having a problem

Operationalchecked 5 minutes ago

We reached RubyGems from all 10 regions we check.

As of Oct 5, 2026, 8:59 PM UTC, RubyGems answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 44 days we have measured RubyGems (since Aug 22, 2026).

our independent probeslive · checked Oct 5, 2026, 8:59 PM UTC
US-East332 msOperational
US-West582 msOperational
Europe177 msOperational
Asia-Pacific105 msOperational
US-Central504 msOperational
Canada303 msOperational
UK428 msOperational
Southeast Asia324 msOperational
Australia542 msOperational
South America427 msOperational
their status pagetheir claim, not our reading

RubyGems reports: Minor incident (“Partially Degraded Service”)

from RubyGems's own status page, checked Sep 6, 2026, 3:39 PM UTC
RubyGems's status page reports Partially Degraded Service. Our probes are currently reaching RubyGems successfully with normal latency. RealUptime's independent checks are currently succeeding 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 what we measured, not what they report: differences can mean a partial or user-specific issue that a simple reachability check won't catch. Read both before you draw a conclusion.

RubyGems's own component breakdown, as they publish it (our last read of their page failed, so this is the previous reading)

  • Fastly Frankfurt (FRA)Operational
  • Gem DownloadsOperational
  • ApplicationOperational
  • Dependency APIOperational
  • Fastly Sydney (SYD)Operational
  • Fastly Amsterdam (AMS)Operational
  • Gem Index APIOperational
  • Fastly Ashburn (IAD)Operational
  • Upstream Provider: AWSOperational
  • Fastly Singapore (SIN)Operational
  • Upstream Provider: DNSimple Name ServersDegraded performance
  • Fastly London (LCY)Under maintenance
  • Fastly Denver (DEN)Operational
  • Fastly London (LHR)Operational
  • Fastly New Zealand (AKL)Operational
  • Fastly Chicago (ORD)Operational
  • Fastly New Zealand (WLG)Operational
  • Fastly Stockholm (BMA)Operational
  • Fastly Hong Kong (HKG)Operational
  • Fastly Miami (MIA)Operational
  • Fastly Dallas (DFW)Operational
  • Fastly Melbourne (MEL)Operational
  • Fastly Osaka (ITM)Operational
  • Fastly San Jose (SJC)Operational
  • Fastly Brisbane (BNE)Operational
  • Fastly Seattle (SEA)Operational
  • Fastly Dubai (FJR)Operational
  • Fastly Perth (PER)Operational
  • Fastly Frankfurt (HHN)Operational
  • Fastly Paris (CDG)Operational
  • Fastly Madrid (MAD)Operational
  • Fastly Boston (BOS)Operational
  • Fastly Minneapolis (MSP)Operational
  • Fastly Johannesburg (JNB)Operational
  • Fastly Montreal (YUL)Operational
  • Fastly Toronto (YYZ)Operational
  • Fastly Sāo Paulo (GRU)Operational
  • Fastly Tokyo (HND)Operational
  • Fastly Tokyo (TYO)Operational
  • Fastly Singapore (QPG)Operational
  • Fastly Tokyo (NRT)Operational
  • Fastly Copenhagen (CPH)Operational
  • Fastly Dublin (DUB)Operational
  • Fastly Helsinki (HEL)Operational
  • Fastly London (LON)Operational
  • Fastly Manchester (MAN)Operational
  • Fastly Marseille (MRS)Operational
  • Fastly Milan (MXP)Operational
  • Fastly Oslo (OSL)Operational
  • Fastly Vienna (VIE)Operational
  • Fastly Munich (MUC)Operational
  • Fastly Chennai (MAA)Operational
  • Fastly Mumbai (BOM)Operational
  • Fastly New Delhi (DEL)Operational
  • Fastly Ashburn (BWI)Operational
  • Fastly Ashburn (DCA)Operational
  • Fastly Ashburn (WDC)Operational
  • Fastly Atlanta (FTY)Operational
  • Fastly Atlanta (PDK)Operational
  • Fastly Chicago (CHI)Operational
  • Fastly Chicago (MDW)Operational
  • Fastly Chicago (PWK)Operational
  • Fastly Columbus (CMH)Operational
  • Fastly Columbus (LCK)Operational
  • Fastly Dallas (DAL)Operational
  • Fastly Houston (IAH)Operational
  • Fastly Jacksonville (JAX)Operational
  • Fastly Kansas City (MCI)Operational
  • Fastly Los Angeles (BUR)Operational
  • Fastly Los Angeles (LGB)Operational
  • Fastly Minneapolis (STP)Operational
  • Fastly New York (LGA)Operational
  • Fastly Newark (EWR)Operational
  • Fastly Palo Alto (PAO)Operational
  • Fastly Phoenix (PHX)Operational
  • Fastly Portland (PDX)Operational
  • Fastly St. Louis (STL)Operational
  • Fastly Vancouver (YVR)Operational
  • Fastly Cape Town (CPT)Operational
  • Fastly Buenos Aires (EZE)Operational
  • Fastly Bogota (BOG)Operational
  • Fastly Curitiba (CWB)Operational
  • Fastly Rio de Janeiro (GIG)Operational
  • Fastly Santiago (SCL)Operational
  • Fastly Sāo Paulo (CGH)Operational
  • Fastly Lima (LIM)Operational

These are RubyGems's components, named and scored by RubyGems. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is RubyGems'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.

RubyGems response time, by region

US-East
444msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 728ms2026-09-07 UTC: p95 796ms2026-09-08 UTC: p95 982ms2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 767ms2026-09-11 UTC: p95 825ms2026-09-12 UTC: p95 798ms2026-09-13 UTC: p95 853ms2026-09-14 UTC: p95 726ms2026-09-15 UTC: p95 778ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 833ms2026-09-24 UTC: p95 846ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 691ms2026-09-27 UTC: p95 949ms2026-09-28 UTC: p95 993ms2026-09-29 UTC: p95 824ms2026-09-30 UTC: p95 971ms2026-10-01 UTC: p95 734ms2026-10-02 UTC: p95 450ms2026-10-03 UTC: p95 678ms2026-10-04 UTC: p95 434ms2026-10-05 UTC: p95 444ms
Sep 6Sep 20Oct 5
US-West
928msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 787ms2026-09-07 UTC: p95 734ms2026-09-08 UTC: p95 953ms2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 855ms2026-09-11 UTC: p95 913ms2026-09-12 UTC: p95 891ms2026-09-13 UTC: p95 958ms2026-09-14 UTC: p95 993ms2026-09-15 UTC: p95 972ms2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 629ms2026-09-18 UTC: p95 641ms2026-09-19 UTC: p95 599ms2026-09-20 UTC: p95 644ms2026-09-21 UTC: p95 587ms2026-09-22 UTC: p95 654ms2026-09-23 UTC: p95 610ms2026-09-24 UTC: p95 666ms2026-09-25 UTC: p95 653ms2026-09-26 UTC: p95 939ms2026-09-27 UTC: p95 771ms2026-09-28 UTC: p95 810ms2026-09-29 UTC: p95 763ms2026-09-30 UTC: p95 776ms2026-10-01 UTC: p95 709ms2026-10-02 UTC: p95 626ms2026-10-03 UTC: p95 572ms2026-10-04 UTC: p95 821ms2026-10-05 UTC: p95 928ms
Sep 6Sep 20Oct 5
Europe
651msp95 · 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-06 UTC: p95 397ms2026-09-07 UTC: p95 409ms2026-09-08 UTC: p95 377ms2026-09-09 UTC: p95 368ms2026-09-10 UTC: p95 544ms2026-09-11 UTC: p95 556ms2026-09-12 UTC: p95 509ms2026-09-13 UTC: p95 563ms2026-09-14 UTC: p95 507ms2026-09-15 UTC: p95 523ms2026-09-16 UTC: p95 507ms2026-09-17 UTC: p95 552ms2026-09-18 UTC: p95 564ms2026-09-19 UTC: p95 547ms2026-09-20 UTC: p95 582ms2026-09-21 UTC: p95 577ms2026-09-22 UTC: p95 629ms2026-09-23 UTC: p95 561ms2026-09-24 UTC: p95 624ms2026-09-25 UTC: p95 599ms2026-09-26 UTC: p95 617ms2026-09-27 UTC: p95 496ms2026-09-28 UTC: p95 752ms2026-09-29 UTC: p95 729ms2026-09-30 UTC: p95 724ms2026-10-01 UTC: p95 610ms2026-10-02 UTC: p95 584ms2026-10-03 UTC: p95 599ms2026-10-04 UTC: p95 609ms2026-10-05 UTC: p95 651ms
Sep 6Sep 20Oct 5
Asia-Pacific
242msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 522ms2026-09-07 UTC: p95 330ms2026-09-08 UTC: p95 404ms2026-09-09 UTC: p95 359ms2026-09-10 UTC: p95 414ms2026-09-11 UTC: p95 430ms2026-09-12 UTC: p95 524ms2026-09-13 UTC: p95 422ms2026-09-14 UTC: p95 571ms2026-09-15 UTC: p95 434ms2026-09-16 UTC: p95 423ms2026-09-17 UTC: p95 334ms2026-09-18 UTC: p95 382ms2026-09-19 UTC: p95 423ms2026-09-20 UTC: p95 520ms2026-09-21 UTC: p95 479ms2026-09-22 UTC: p95 306ms2026-09-23 UTC: p95 364ms2026-09-24 UTC: p95 320ms2026-09-25 UTC: p95 423ms2026-09-26 UTC: p95 425ms2026-09-27 UTC: p95 481ms2026-09-28 UTC: p95 327ms2026-09-29 UTC: p95 343ms2026-09-30 UTC: p95 351ms2026-10-01 UTC: p95 281ms2026-10-02 UTC: p95 296ms2026-10-03 UTC: p95 225ms2026-10-04 UTC: p95 254ms2026-10-05 UTC: p95 242ms
Sep 6Sep 20Oct 5
US-Central
720msp95 · 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-09-06 UTC: p95 739ms2026-09-07 UTC: p95 821ms2026-09-08 UTC: p95 712ms2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 906ms2026-09-11 UTC: p95 896ms2026-09-12 UTC: p95 686ms2026-09-13 UTC: p95 580ms2026-09-14 UTC: p95 662ms2026-09-15 UTC: p95 740ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 907ms2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 831ms2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 915ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 921ms2026-09-27 UTC: p95 904ms2026-09-28 UTC: p95 841ms2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 953ms2026-10-01 UTC: p95 774ms2026-10-02 UTC: p95 691ms2026-10-03 UTC: p95 901ms2026-10-04 UTC: p95 913ms2026-10-05 UTC: p95 720ms
Sep 6Sep 20Oct 5
Canada
926msp95 · 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-06 UTC: p95 745ms2026-09-07 UTC: p95 807ms2026-09-08 UTC: p95 670ms2026-09-09 UTC: p95 760ms2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 830ms2026-09-12 UTC: p95 732ms2026-09-13 UTC: p95 879ms2026-09-14 UTC: p95 828ms2026-09-15 UTC: p95 789ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 843ms2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 974ms2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 657ms2026-10-02 UTC: p95 717ms2026-10-03 UTC: p95 889ms2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 926ms
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 796ms2026-09-07 UTC: p95 505ms2026-09-08 UTC: p95 911ms2026-09-09 UTC: p95 871ms2026-09-10 UTC: p95 875ms2026-09-11 UTC: p95 649ms2026-09-12 UTC: p95 710ms2026-09-13 UTC: p95 814ms2026-09-14 UTC: p95 825ms2026-09-15 UTC: p95 436ms2026-09-16 UTC: p95 417ms2026-09-17 UTC: p95 445ms2026-09-18 UTC: p95 427ms2026-09-19 UTC: p95 426ms2026-09-20 UTC: p95 352ms2026-09-21 UTC: p95 701ms2026-09-22 UTC: p95 797ms2026-09-23 UTC: p95 592ms2026-09-24 UTC: p95 887ms2026-09-25 UTC: p95 826ms2026-09-26 UTC: p95 459ms2026-09-27 UTC: p95 480ms2026-09-28 UTC: p95 663ms2026-09-29 UTC: p95 967ms2026-09-30 UTC: p95 853ms2026-10-01 UTC: p95 733ms2026-10-02 UTC: p95 450ms2026-10-03 UTC: p95 795ms2026-10-04 UTC: p95 904ms2026-10-05 UTC: p95 424ms
Sep 6Sep 20Oct 5
Southeast Asia
402msp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 506ms2026-09-07 UTC: p95 1.0s2026-09-08 UTC: p95 886ms2026-09-09 UTC: p95 999ms2026-09-10 UTC: p95 498ms2026-09-11 UTC: p95 902ms2026-09-12 UTC: p95 387ms2026-09-13 UTC: p95 536ms2026-09-14 UTC: p95 544ms2026-09-15 UTC: p95 499ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 743ms2026-09-18 UTC: p95 363ms2026-09-19 UTC: p95 401ms2026-09-20 UTC: p95 943ms2026-09-21 UTC: p95 559ms2026-09-22 UTC: p95 729ms2026-09-23 UTC: p95 979ms2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 932ms2026-09-27 UTC: p95 988ms2026-09-28 UTC: p95 628ms2026-09-29 UTC: p95 565ms2026-09-30 UTC: p95 557ms2026-10-01 UTC: p95 460ms2026-10-02 UTC: p95 430ms2026-10-03 UTC: p95 573ms2026-10-04 UTC: p95 352ms2026-10-05 UTC: p95 402ms
Sep 6Sep 20Oct 5
Australia
1.1sp95 · 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 511ms2026-09-07 UTC: p95 399ms2026-09-08 UTC: p95 364ms2026-09-09 UTC: p95 648ms2026-09-10 UTC: p95 459ms2026-09-11 UTC: p95 945ms2026-09-12 UTC: p95 756ms2026-09-13 UTC: p95 298ms2026-09-14 UTC: p95 511ms2026-09-15 UTC: p95 447ms2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 953ms2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 640ms2026-09-22 UTC: p95 533ms2026-09-23 UTC: p95 667ms2026-09-24 UTC: p95 845ms2026-09-25 UTC: p95 419ms2026-09-26 UTC: p95 948ms2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 587ms2026-09-29 UTC: p95 944ms2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 590ms2026-10-02 UTC: p95 554ms2026-10-03 UTC: p95 434ms2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
South America
1.7sp95 · 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 1.2s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 1.5s2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.3s2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.8s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.7s2026-10-05 UTC: p95 1.7s
Sep 6Sep 20Oct 5

Is it RubyGems, 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 RubyGems -- it cannot diagnose RubyGems's own systems.

What we measured, function by function

RubyGems 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: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see RubyGems go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching RubyGems, and again when they can reach it again. That is our own measurement from ten regions, not RubyGems's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

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: 332msstatus code: 200checked: Oct 5, 2026, 8:50 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach RubyGems normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 582msstatus code: 200checked: Oct 5, 2026, 8:47 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach RubyGems normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 504msstatus code: 200checked: Oct 5, 2026, 8:20 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach RubyGems normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 303msstatus code: 200checked: Oct 5, 2026, 8:32 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach RubyGems normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 427msstatus code: 200checked: Oct 5, 2026, 8:30 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach RubyGems normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 177msstatus code: 200checked: Oct 5, 2026, 8:59 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach RubyGems normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 428msstatus code: 200checked: Oct 5, 2026, 8:55 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach RubyGems 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: 105msstatus code: 200checked: Oct 5, 2026, 8:36 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach RubyGems normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 324msstatus code: 200checked: Oct 5, 2026, 8:47 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach RubyGems normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 542msstatus code: 200checked: Oct 5, 2026, 8:54 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach RubyGems 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 RubyGems, 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 have not received any reports for RubyGems yet, which is not evidence that nothing is wrong.

Recent outages

Elevated Errors, 2h 29mdeclared on their status page2026-08-19
Degraded service on RubyGems.org, 37mdeclared on their status page2026-07-24
Temporarily disabling new user registrations, 92h 18mdeclared on their status page2026-05-12
Rubygems.org is experiencing a partial outage, 30mdeclared on their status page2026-04-06
Degraded performance, 1h 1mdeclared on their status page2026-03-31
Search degredation, 2h 14mdeclared on their status page2026-02-12
Gem pushes with attestation failing, 302h 10mdeclared on their status page2025-10-15
Google Safe Browsing flag as malware, 3h 16mdeclared on their status page2023-05-11

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

We have been measuring RubyGems since August 22, 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 RubyGems covering any window you pick, with our measurements and RubyGems's own claim at the time, side by side.

Full availability history for RubyGems: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

RubyGems uptime measured by RealUptimeLive, from this page's own readings.
[![RubyGems uptime measured by RealUptime](https://realuptime.io/outages/rubygems/badge.svg?days=30)](https://realuptime.io/outages/rubygems)
<a href="https://realuptime.io/outages/rubygems"><img src="https://realuptime.io/outages/rubygems/badge.svg?days=30" alt="RubyGems 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 RubyGems's SLA implies, from our measurement

At or above your target

We measured none of downtime for RubyGems 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 RubyGems'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: live API
https://rubygems.org/api/v1/gems/rails.json
secondary
https://rubygems.org/
secondary
https://status.rubygems.org/api/v2/status.json
RealUptime is not affiliated with RubyGems; the name identifies what we measured, and nothing here speaks for RubyGems's own team. We send a single web request to RubyGems from 10 regions on our own schedule and time the response. We do not see inside RubyGems's systems, do not use an account or real transaction, and are not the same signal RubyGems's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for RubyGems 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.