Suboptimal routing for a subset of prefixes from AMS
Network — transit & peering — AMS
Timeline
-
Resolved
Routing is back to normal from every probe location. Duration: 16 minutes. Latency on the affected path was up to 17 ms above normal; no connectivity was lost.
-
Identified
A transit provider two hops away leaked a more specific route for one of our /24s. We have announced the same more specific ourselves so that it wins on the shortest path, and we have asked Arelion to filter the leak upstream.
-
Investigating
A subset of our AMS prefixes is being reached over an unusually long path from Mexico. We see it in our external probes; users in other regions are not affected.
Times are shown in your time zone ().
Related pages
- Service statusLive status of every gpuserver.io component and data centre, probed every 60 seconds from five cities, with 90-day uptime and the incident log since 2022.
- Incident historyEvery incident and maintenance window on gpuserver.io since monitoring began in September 2022, month by month, with its timeline and post-incident review.
- Service level agreementThe 99.9% commitment: what counts as downtime, how it is measured from outside, five minutes of term back per minute lost, and the exclusions in full.
- NetworkUnmetered ports up to 25 Gbit/s, two carriers and an IX per site, always-on DDoS filtering, routed IPv6 — and the four things we do not offer, stated up front.