Minor incident

TCPShield: Brief partial disconnect in Frankfurt

Affected: Frankfurt (Anycast)

Current status of TCPShield: Operational — live TCPShield status

Timeline

1. Oct 25, 2026, 18:41 UTC
   identified
   From 18:17 to 18:19 UTC, a single node in our Frankfurt fleet experienced an OOM (ran out of memory). Some traffic routed through Frankfurt saw a brief disruption of about 2 minutes. Service automatically failed over to other nodes in the process, and all other locations were unaffected. We have identified the root cause and deployed a corrective fix. No further impact is expected, and no action is needed from end users.
2. Oct 25, 2026, 18:46 UTC
   monitoring
   A fix has been implemented and we are monitoring the results.
3. Oct 26, 2026, 04:28 UTC
   monitoring
   The affected node has been put back in rotation at approximately 03:30 UTC. A partial disconnect is expected in the process due to ECMP.
4. Oct 26, 2026, 04:28 UTC
   monitoring
   We are continuing to monitor for any further issues.
5. Oct 26, 2026, 04:29 UTC
   resolved
   This incident has been resolved.

Updates as published by TCPShield (original).