Skip to content

Outage tracker / RubyGems

Is RubyGems down?

I'm having a problem

Vendor reports no incidentWhat RubyGems reports

RubyGems reports no incident on its status page.

As of the last successful poll, 2026-10-14 13:24 UTC.

RubyGems'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 2 minutes ago

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

As of Oct 14, 2026, 1:26 PM UTC, RealUptime's checks of RubyGems passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 14, 2026, 1:26 PM UTC
US-East348 msChecks passing
US-West346 msChecks passing
Europe106 msChecks passing
Asia-Pacific91 msChecks passing
US-Central829 msChecks passing
Canada638 msChecks passing
UK263 msChecks passing
Southeast Asia358 msChecks passing
Australia463 msChecks passing
South America492 msChecks passing
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 checks of RubyGems 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.

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
508msp95 · 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-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 498ms2026-10-06 UTC: p95 752ms2026-10-07 UTC: p95 737ms2026-10-08 UTC: p95 760ms2026-10-09 UTC: p95 668ms2026-10-10 UTC: p95 687ms2026-10-11 UTC: p95 707ms2026-10-12 UTC: p95 655ms2026-10-13 UTC: p95 691ms2026-10-14 UTC: p95 508ms
Sep 15Sep 29Oct 14
US-West
629msp95 · 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-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 924ms2026-10-06 UTC: p95 911ms2026-10-07 UTC: p95 941ms2026-10-08 UTC: p95 1.0s2026-10-09 UTC: p95 938ms2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 952ms2026-10-12 UTC: p95 880ms2026-10-13 UTC: p95 749ms2026-10-14 UTC: p95 629ms
Sep 15Sep 29Oct 14
Europe
548msp95 · 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-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 629ms2026-10-06 UTC: p95 704ms2026-10-07 UTC: p95 665ms2026-10-08 UTC: p95 606ms2026-10-09 UTC: p95 560ms2026-10-10 UTC: p95 517ms2026-10-11 UTC: p95 489ms2026-10-12 UTC: p95 542ms2026-10-13 UTC: p95 465ms2026-10-14 UTC: p95 548ms
Sep 15Sep 29Oct 14
Asia-Pacific
633msp95 · 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-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 239ms2026-10-06 UTC: p95 289ms2026-10-07 UTC: p95 329ms2026-10-08 UTC: p95 229ms2026-10-09 UTC: p95 321ms2026-10-10 UTC: p95 372ms2026-10-11 UTC: p95 283ms2026-10-12 UTC: p95 306ms2026-10-13 UTC: p95 413ms2026-10-14 UTC: p95 633ms
Sep 15Sep 29Oct 14
US-Central
728msp95 · 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-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 717ms2026-10-06 UTC: p95 593ms2026-10-07 UTC: p95 788ms2026-10-08 UTC: p95 850ms2026-10-09 UTC: p95 732ms2026-10-10 UTC: p95 864ms2026-10-11 UTC: p95 708ms2026-10-12 UTC: p95 758ms2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 728ms
Sep 15Sep 29Oct 14
Canada
941msp95 · 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-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 911ms2026-10-06 UTC: p95 784ms2026-10-07 UTC: p95 844ms2026-10-08 UTC: p95 820ms2026-10-09 UTC: p95 719ms2026-10-10 UTC: p95 842ms2026-10-11 UTC: p95 662ms2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 941ms
Sep 15Sep 29Oct 14
UK
489msp95 · 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-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 449ms2026-10-06 UTC: p95 508ms2026-10-07 UTC: p95 844ms2026-10-08 UTC: p95 753ms2026-10-09 UTC: p95 645ms2026-10-10 UTC: p95 474ms2026-10-11 UTC: p95 497ms2026-10-12 UTC: p95 458ms2026-10-13 UTC: p95 469ms2026-10-14 UTC: p95 489ms
Sep 15Sep 29Oct 14
Southeast Asia
851msp95 · 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-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 399ms2026-10-06 UTC: p95 418ms2026-10-07 UTC: p95 425ms2026-10-08 UTC: p95 507ms2026-10-09 UTC: p95 403ms2026-10-10 UTC: p95 548ms2026-10-11 UTC: p95 399ms2026-10-12 UTC: p95 441ms2026-10-13 UTC: p95 920ms2026-10-14 UTC: p95 851ms
Sep 15Sep 29Oct 14
Australia
636msp95 · 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-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.1s2026-10-06 UTC: p95 772ms2026-10-07 UTC: p95 552ms2026-10-08 UTC: p95 980ms2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 810ms2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 913ms2026-10-13 UTC: p95 348ms2026-10-14 UTC: p95 636ms
Sep 15Sep 29Oct 14
South America
1.4sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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.6s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 1.6s2026-10-10 UTC: p95 1.6s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 2.1s2026-10-14 UTC: p95 1.4s
Sep 15Sep 29Oct 14

Check your own site while you wait on RubyGems

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: 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

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

Get an email when RubyGems reports an incident

Email me when RubyGems reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

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

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: 348msstatus code: 200checked: Oct 14, 2026, 1:00 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
      Checks passinglatency: 346msstatus code: 200checked: Oct 14, 2026, 1:26 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
      Checks passinglatency: 829msstatus code: 200checked: Oct 14, 2026, 1:23 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
      Checks passinglatency: 638msstatus code: 200checked: Oct 14, 2026, 12:36 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
    Checks passinglatency: 492msstatus code: 200checked: Oct 14, 2026, 12:35 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 106msstatus code: 200checked: Oct 14, 2026, 1:22 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
      Checks passinglatency: 263msstatus code: 200checked: Oct 14, 2026, 1:00 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 91msstatus code: 200checked: Oct 14, 2026, 1:18 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
      Checks passinglatency: 358msstatus code: 200checked: Oct 14, 2026, 12:53 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
      Checks passinglatency: 463msstatus code: 200checked: Oct 14, 2026, 1:00 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 probe events

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

check 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 check readings and RubyGems's own claim at the time, side by side.

Full check history for RubyGems: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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 by RealUptime's checksLive, from this page's own readings.
[![RubyGems uptime by RealUptime's checks](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 by RealUptime's checks"></a>

The badge shows the share of our checks that passed 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 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 RubyGems down?", https://realuptime.io/outages/rubygems. 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://rubygems.org/api/v1/gems/rails.json
secondary
https://rubygems.org/
secondary
https://status.rubygems.org/api/v2/status.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: rubygems.org

RealUptime is not affiliated with RubyGems; the name identifies what we checked, 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 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.