Skip to content
UpButler
ProductAgentsStatus pagesDocsPricing
Sign inStart free

Is Fastly London (LCY) down?

Fastly London (LCY) is under maintenance

Right now

Maintenance. Fastly London (LCY): Under maintenance.

Last checked (2026-10-10 08:11 UTC) from status.rubygems.org · every 180s

For agents

pause

Pause, next attempt in 300s.

Up right now, same job: npm, jsDelivr, unpkg, PyPI.

GET upbutler.com/status/rubygems/fastly-london-lcy/status.agent.json

MCP: upstream_status {"service":"rubygems","component":"fastly-london-lcy"}

Fastly London (LCY) is one of the components RubyGems.org reports on its status page. The Ruby gem registry. An outage fails bundle install in CI and image builds.

Part of RubyGems.org status.

What RubyGems.org says

Maintenance

Taken as is from RubyGems.org's own status page API. Incident titles and component names below are theirs. Narrowed to what concerns Fastly London (LCY).

Open status.rubygems.org

What UpButler measured

API is answeringHTTP 200 · 28 ms

One request without credentials to rubygems.org every two minutes, from eu-central (one location, not a global view). An answer shows the edge, TLS and routing work. It does not prove that authenticated calls succeed. The probe is for RubyGems.org as a whole, not for Fastly London (LCY) specifically.

Checked · up since 2026-10-10 06:09 UTC

Fastly London (LCY): what RubyGems.org lists

1 of 1 not operational

Upstream Provider: Fastly

  • Fastly London (LCY)Maintenance

Fastly London (LCY) incidents, last 90 days

  1. 2026-07-13: no record
  2. 2026-07-14: no record
  3. 2026-07-15: no record
  4. 2026-07-16: no record
  5. 2026-07-17: no record
  6. 2026-07-18: no record
  7. 2026-07-19: no record
  8. 2026-07-20: no record
  9. 2026-07-21: no record
  10. 2026-07-22: no record
  11. 2026-07-23: no record
  12. 2026-07-24: no record
  13. 2026-07-25: no record
  14. 2026-07-26: no record
  15. 2026-07-27: no record
  16. 2026-07-28: no record
  17. 2026-07-29: no record
  18. 2026-07-30: no record
  19. 2026-07-31: no record
  20. 2026-08-01: no record
  21. 2026-08-02: no record
  22. 2026-08-03: no record
  23. 2026-08-04: no record
  24. 2026-08-05: no record
  25. 2026-08-06: no record
  26. 2026-08-07: no record
  27. 2026-08-08: no record
  28. 2026-08-09: no record
  29. 2026-08-10: no record
  30. 2026-08-11: no record
  31. 2026-08-12: no record
  32. 2026-08-13: no record
  33. 2026-08-14: no record
  34. 2026-08-15: no record
  35. 2026-08-16: no record
  36. 2026-08-17: no record
  37. 2026-08-18: no record
  38. 2026-08-19: no record
  39. 2026-08-20: no record
  40. 2026-08-21: no record
  41. 2026-08-22: no record
  42. 2026-08-23: no record
  43. 2026-08-24: no record
  44. 2026-08-25: no record
  45. 2026-08-26: no record
  46. 2026-08-27: no record
  47. 2026-08-28: no record
  48. 2026-08-29: no record
  49. 2026-08-30: no record
  50. 2026-08-31: no record
  51. 2026-09-01: no record
  52. 2026-09-02: no record
  53. 2026-09-03: no record
  54. 2026-09-04: no record
  55. 2026-09-05: no record
  56. 2026-09-06: no record
  57. 2026-09-07: no record
  58. 2026-09-08: no record
  59. 2026-09-09: no record
  60. 2026-09-10: no record
  61. 2026-09-11: no record
  62. 2026-09-12: no record
  63. 2026-09-13: no record
  64. 2026-09-14: no record
  65. 2026-09-15: no record
  66. 2026-09-16: no record
  67. 2026-09-17: no record
  68. 2026-09-18: no record
  69. 2026-09-19: no record
  70. 2026-09-20: no record
  71. 2026-09-21: no record
  72. 2026-09-22: no record
  73. 2026-09-23: no record
  74. 2026-09-24: no record
  75. 2026-09-25: no record
  76. 2026-09-26: no record
  77. 2026-09-27: no record
  78. 2026-09-28: no record
  79. 2026-09-29: no record
  80. 2026-09-30: no record
  81. 2026-10-01: no record
  82. 2026-10-02: no record
  83. 2026-10-03: no record
  84. 2026-10-04: no record
  85. 2026-10-05: no record
  86. 2026-10-06: no record
  87. 2026-10-07: no record
  88. 2026-10-08: no record
  89. 2026-10-09: no record
  90. 2026-10-10: no incident reported
2026-07-130 of 1 days with an incidenttoday

Each bar is a day, coloured by the worst incident RubyGems.org reported for Fastly London (LCY). It is their incident record, not a measurement of uptime.

No finished incidents on record yet since 2026-10-10. UpButler keeps what RubyGems.org publishes for 90 days from the day it starts tracking a service.

Get alerted when Fastly London (LCY) goes down

No account. One email when RubyGems.org reports an incident that affects Fastly London (LCY), one when it is over. You confirm the address first, and every email has a one-click unsubscribe.

Or follow the RSS feed. On UpButler? Add RubyGems.org as a dependency to route it to Slack, Teams or a webhook.

Status badge

Show Fastly London (LCY)'s current status in a README or an internal wiki. It updates by itself.

Fastly London (LCY) status badge

[![Fastly London (LCY) status](https://upbutler.com/status/rubygems/badge.svg?component=fastly-london-lcy)](https://upbutler.com/status/rubygems/fastly-london-lcy)

Tell your outage from RubyGems.org's

Declare that your project depends on Fastly London (LCY). When one of your monitors fails while RubyGems.org has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start freeHow it works
upbutler.yaml
# upbutler.yaml
dependencies:
  - service: rubygems
    components: ["Fastly London (LCY)"]
Ask before you retry
curl -s https://upbutler.com/status/rubygems/fastly-london-lcy/status.agent.json
status.agent.json (live)
{
  "schema": "upbutler.upstream-status/v1",
  "service": "rubygems",
  "component": {
    "slug": "fastly-london-lcy",
    "name": "Fastly London (LCY)"
  },
  "verdict": "pause",
  "status": "maintenance",
  "reason": "Fastly London (LCY): Under maintenance",
  "retryAfterSec": 300,
  "incident": null,
  "alternatives": [
    "npm",
    "jsdelivr",
    "unpkg",
    "pypi"
  ],
  "probe": {
    "state": "up",
    "statusCode": 200
  }
}

Questions

Is Fastly London (LCY) down right now?
Maintenance. As of 2026-10-10 08:11 UTC, Fastly London (LCY) is under maintenance. This page reads the status again every 3 minutes.
Where does this status come from?
From RubyGems.org's own status page API at https://status.rubygems.org. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are RubyGems.org's words. Their page covers more than this page shows; it is narrowed to the parts that concern Fastly London (LCY).
What does UpButler's own RubyGems.org check prove?
Every two minutes UpButler sends one request without credentials to the RubyGems.org API (rubygems.org) from eu-central. Any answer from the edge, usually HTTP 200, shows that DNS, TLS and routing work from there. It does not prove that authenticated requests succeed, and it is one location, not a global view. It is most useful when it fails before their status page changes; the page then says so.
Can I get an alert when Fastly London (LCY) goes down?
Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when RubyGems.org reports an incident that affects Fastly London (LCY) and one when it is over. There is also an RSS feed at https://upbutler.com/status/rubygems/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.
How can my agent or app check Fastly London (LCY) status?
Fetch https://upbutler.com/status/rubygems/fastly-london-lcy/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"rubygems","component":"fastly-london-lcy"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or RubyGems.org's?
Add "rubygems" to the dependencies of your UpButler workspace. When one of your monitors fails while RubyGems.org has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Also check

UpButler is not affiliated with RubyGems.org. Status and incident text belong to RubyGems.org and are read from their public status source; the probe result is UpButler's own measurement.