BGP session instability with Arelion in AMS
Network — transit & peering — AMS
Timeline
-
Resolved
Stable since 04:04 UTC. Outbound traffic is back on its normal paths. Duration: 23 minutes. Impact was limited to brief latency spikes on some routes; no session to a machine was reset.
-
Identified
The resets coincide with a route-refresh storm on the Arelion side. We have applied dampening on our end and shifted outbound traffic to Lumen while Arelion investigates.
-
Investigating
The BGP session with Arelion in AMS has reset 8 times since 03:41 UTC. Each reset causes a few seconds of reconvergence for traffic that prefers that path. We are looking at our side of the session first.
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.