Railway - A small subset of requests ingested at our us-east edge failed with a 503 error – Incident details

A small subset of requests ingested at our us-east edge failed with a 503 error

Resolved
Partial outage
Started 12 months agoLasted less than a minute

Affected

Legacy Edge Network

Updates
  • Resolved
    Resolved

    We experienced a high volume of connections from AWS directed at a single tenant via our us-east edge between 19:55 UTC and 20:20UTC. This traffic caused resource exhaustion on our proxies and led to a small subset of connections being terminated. We have mitigated this temporarily and are provisioning more proxy nodes to handle the load in us-east.