Status
eu-waw gateway
Measured from three external probes in Frankfurt, Amsterdam and Warsaw, one sample per minute. A day counts as degraded if any probe saw more than 60 seconds of failed connects.
Now
operational
30 days
99.97%
90 days
99.91%
Last incident
—
Checked
—
WebSocket connects
90 days agotoday
Publish API
90 days agotoday
Incidents
| When | Duration | What happened |
|---|---|---|
| — | 34 min | Upstream network maintenance at the facility dropped transit for one of two uplinks. Connects failed for clients routed over the affected path; publishes queued and drained without loss. resolved |
| — | 6 min | Same maintenance window, first pass. resolved |
| — | 11 min | A deploy rolled with an undersized connection table; sockets above the cap were refused with
4503 until the previous build was restored. resolved |
Maintenance
Rolling restarts land on Tuesdays between 02:00 and 04:00 UTC. Clients see close code
4503 and should reconnect with last_seq; nothing inside the retention
window is lost. Windows that need more than a rolling restart are announced here at least 48 hours
ahead — none is scheduled at the moment.
This page is generated from the probe database and is not a contractual SLA.
The numbers we do commit to are on limits.