Firecrawl Alexandria

Railway

Railway's public content through the sources Railway publishes for agents: the docs index and any docs page as Markdown (docs.railway.com), blog posts (blog.railway.com), live platform status and incident history from the status page's documented JSON API (api.railwaystatus.com, behind status.railway.com), pricing, company and legal pages, the product changelog, and one-click deploy templates with their machine-readable manifests (railway.com). No login or key.

Try in Agent

Use Railway for Get blog post. Inspect the Alexandria inputs, ask for any missing required details, and return a small sample with sources.

Try Railway now.

Choose an example or ask your own question.

What do you want to do with Railway?

Railway

TRY ASKING

Codefollows the fields above

const result = await firecrawl.scrape({
  alexandria: {
    provider: "railway-com",
    capability: "developer-documentation/get_blog_post",
    options: {
      max_chars: 1500,
      slug: "incident-report-sept-30-2026-routing-disruption",
    },
  },
});

2Response example

This is a sample shape. Press Run to see live data from Railway.

{
  "authors": [
    "Angelo Saraceno"
  ],
  "category": "Engineering",
  "chars": 7541,
  "content": "# Incident Report: September 30, 2026: Domain Routing Disruption\n\nOn September 30, 2026, domains hosted on Railway returned 404 not found errors for new connections for a five minute period for all customers.\n\nWhile rolling out a change to our distributed routing control plane, the new deployment didn’t wait for the schema updates needed to support new functionality. Our distributed routing control plane is the system that tells our origin proxies how to route user requests to the workloads behind every domain.\n\nBecause of this mismatch, route lookups failed, and any attempt to reach a domain served by Railway-hosted workloads returned an error. During the incident period, our origin proxies treated each failed lookup as if \"this domain doesn't exist\" instead of falling back to the last route it knew.\n\nAfter five minutes of the system automatically reconciling to the intended working state - it restored most traffic; then routing recovered on its own as soon as the schema update finished.\n\n## Impact\n\nOn September 30, 2026, between roughly 07:35 and 07:40 UTC, new connections to domains hosted on Railway (which include custom domains and `*.up.railway.app` domains) returned HTTP 404 in all regions.\n\nPublic access and some private networking lookups between services failed during this window. User service uptime was not impacted, only access as workloads kept running throughout we are able to confirm that no data was lost.\n\n## Incident Timeline\n\n*All times are UTC on September ",
  "date": "2026-09-30T22:42:12.172Z",
  "description": "Railway experienced a platform-wide disruption to domain routing on September 30, 2026. For roughly five minutes, between about 07:35 and 07:40 UTC, new connections to domains hosted on Railway returned 404 errors.",
  "markdown_url": "https://blog.railway.com/p/incident-report-sept-30-2026-routing-disruption.md",
  "observed_at_ms": 1792695886426,
  "outline": [
    {
      "level": 2,
      "text": "Impact"
    },
    {
      "level": 2,
      "text": "Incident Timeline"
    },
    {
      "level": 2,
      "text": "What Happened?"
    },
    {
      "level": 3,
      "text": "1) A schema update and a binary rollout in the wrong order"
    },
    {
      "level": 3,
      "text": "2) Joint impact and blast radius"
    },
    {
      "level": 2,
      "text": "Preventative Measures"
    },
    {
      "level": 2,
      "text": "Our Incident Procedure"
    }
  ],
  "slug": "incident-report-sept-30-2026-routing-disruption",
  "title": "Incident Report: September 30, 2026: Domain Routing Disruption",
  "truncated": true,
  "url": "https://blog.railway.com/p/incident-report-sept-30-2026-routing-disruption"
}

Browse the library

Railway

Try Railway now.

Related providers