TCPShield Outage History

TCPShield is up right now

Pingoru has recorded 32 incidents for TCPShield: 20 in the last 12 months and 4 in the last 90 days.

Source: status.tcpshield.com

32incidents recorded
20last 12 months
4last 90 days
4 hourstypical duration

Incidents, newest first

Minor March 23, 2025 Gravelines network issues 52m Gravelines (Cloudflare)

Started Mar 23, 2025, 05:29 PM UTC· resolved Mar 23, 2025, 06:21 PM UTC

  1. identified Mar 23, 2025, 05:29 PM UTC

    At 17:21 UTC, Gravelines experienced a series of internal attacks sourced from a downstream BGP customer of OVH: https://bgp.tools/prefix/146.103.40.0/22#connectivity This is unfortunately a rare case where a BGP customer of OVH exploits their connectivity as a means to bypass volumetric protection. We await response from the culprit network.

  2. identified Mar 23, 2025, 05:35 PM UTC

    We are continuing to work on a fix for this issue.

  3. resolved Mar 23, 2025, 06:21 PM UTC

    The culprit network (Regexa / AS215311) has informed us corrective actions have been taken for the abuse at 18:21. We continue to monitor the results.

Read the full incident report →

Notice March 5, 2025 New York connection issues –

Started Mar 05, 2025, 10:30 PM UTC· resolved Mar 05, 2025, 10:30 PM UTC

  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.

Read the full incident report →

Minor January 30, 2025 Pittsburgh <> Chicago backbone flapping 55m Dallas

Started Jan 30, 2025, 07:32 AM UTC· resolved Jan 30, 2025, 08:27 AM UTC

  1. investigating Jan 30, 2025, 08:22 AM UTC

    We are currently investigating a backbone incident impacting Pittsburgh and Chicago causing certain players near these regions to unexpectedly divert between Ashburn and Dallas.

  2. investigating Jan 30, 2025, 08:23 AM UTC

    We are continuing to investigate this issue.

  3. identified Jan 30, 2025, 08:23 AM UTC

    The issue has been identified and a fix is being implemented.

  4. resolved Jan 30, 2025, 08:27 AM UTC

    Cogent has confirmed ongoing construction near the cable which has resulted in partial outages. We have disabled Dallas until the construction subsides.

Read the full incident report →

Minor January 14, 2025 Network congestion between Amsterdam and Frankfurt –

Started Jan 14, 2025, 04:00 PM UTC· resolved Jan 14, 2025, 04:00 PM UTC

  1. resolved Jan 14, 2025, 11:58 PM UTC

    We are currently aware of network congestion impacting FRA <> AMS. Traffic has been re-routed to alternate available paths at this time. Users may experience increased latency as we work to divert traffic.

  2. postmortem Jan 14, 2025, 11:59 PM UTC

    Traffic has been restored back to its original path as of 00:01 UTC. We continue to monitor results.

Read the full incident report →