Resolved -
Dear Members/Customers,
An internal investigation identified the root cause as a corrupt route server configuration file. We have taken actions to mitigate future occurrences.
After extensive monitoring of the BGP sessions and the route server reconfiguration process, both have been stable and operate as expected.
This incident is now resolved.
May 5, 16:33 CEST
Monitoring -
Dear Members/Customers,
We have identified and fixed the issue; BGP sessions are now established again. We are investigating the root cause.
Timeline:
Start: Sun, May 03, 22:12 CEST 2026
End: Sun, May 03, 23:07 CEST 2026
AMS-IX NOC
May 3, 23:28 CEST
Investigating -
Dear Members/Customers,
We are currently investigating an issue with BGP sessions to RS2.
Affected:
IPv6: 2001:43f8:41::a503:7728:252
ASN: 37728
May 3, 22:43 CEST
