Major incident
TCPShield: Forwarding degradation in Amsterdam
Mar 30, 2026, 21:02 UTC
started
19:42 UTC
resolved
—
duration
Current status of TCPShield: Operational — live TCPShield status
Timeline
- Mar 30, 2026, 19:42 UTCresolvedAt 19:42:10 UTC, our Amsterdam location experienced forwarding degradation lasting approximately 1 minute. The root cause is being investigated by GSL at this time, as the issue is external to our own infrastructure. We will share updates as we learn more, and will pull routing from Amsterdam to alternate locations in the event of a recurrence. In the meantime, we continue to monitor.
Updates as published by TCPShield (original).
Other services with incidents at the same time
- Red Hat 20:11 UTC · quay.io API failures
- University of Waterloo 20:07 UTC · Emergency: A reboot of the ADFS DB server is required for Veeam backup - Outage
More TCPShield incidents
- October 25, 2026 Brief partial disconnect in Frankfurt
- September 6, 2026 Seoul optical issue
- July 6, 2026 Tokyo Hardware Failure
- June 30, 2026 Sydney outage