Brief latency increase during DDoS mitigation in YUL
Network — transit & peering — YUL
Timeline
-
Resolved
The attack ended at 11:30 UTC. Duration: 14 minutes. Legitimate sessions were not reset at any point; other machines in the site saw at most 23 ms of added latency during the first minute.
-
Identified
The attack peaks at a level the filtering handles comfortably. The latency increase for other machines came from the re-steering itself, not from saturation, and has already subsided.
-
Investigating
A volumetric attack against one customer address in YUL is being filtered. Mitigation engaged within ten seconds of the first anomalous packets; some other machines in the site saw a short latency increase while traffic was steered into the scrubbing path.
Times are shown in your time zone ().
Related pages
- Service statusLive status of every gpuserver.io component and data centre, probed every 60 seconds from five cities, with 90-day uptime and the incident log since 2022.
- Incident historyEvery incident and maintenance window on gpuserver.io since monitoring began in September 2022, month by month, with its timeline and post-incident review.
- Service level agreementThe 99.9% commitment: what counts as downtime, how it is measured from outside, five minutes of term back per minute lost, and the exclusions in full.
- NetworkUnmetered ports up to 25 Gbit/s, two carriers and an IX per site, always-on DDoS filtering, routed IPv6 — and the four things we do not offer, stated up front.