TCPShield incident

New York connection issues

Resolved on March 5, 2025.

resolved Mar 06, 2025, 01:24 AM UTC

At 17:46 UTC, there was a drop in Ashburn due to incorrectly applied mitigation configs in New York. This resulted in attacks originated in this metro to leak towards Ashburn. The attack, while laughably small, was enough to cause impact due to the device in New York not knowing what to do with the traffic. We've now confirmed configs are applied correctly and can see traffic has normalized.

Started
Mar 05, 2025, 10:30 PM UTC
Resolved
Mar 05, 2025, 10:30 PM UTC
Duration
–
Detected by Pingoru
Mar 05, 2025, 10:30 PM UTC

Update timeline

  1. resolved Mar 06, 2025, 01:24 AM UTC

    At 17:46 UTC, there was a drop in Ashburn due to incorrectly applied mitigation configs in New York. This resulted in attacks originated in this metro to leak towards Ashburn. The attack, while laughably small, was enough to cause impact due to the device in New York not knowing what to do with the traffic. We've now confirmed configs are applied correctly and can see traffic has normalized.

Your product runs on more than TCPShield

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →