Elevated latency to India from YUL
Network — transit & peering — YUL
Timeline
-
Resolved
Latency to India is back to its usual level. Duration: 28 minutes. Throughput was not affected; only the round trip on that path was.
-
Monitoring
The direct peering route has been re-announced. We have removed our preference and are watching latency settle.
-
Identified
A peer on QIX has withdrawn its direct route to India and traffic is taking a detour via Cogent. This is a routing choice on their side, not a fault on ours. We have preferred Zayo for those prefixes, which brings the round trip back within 10 ms of normal.
-
Investigating
Round-trip times from YUL to India are 77 ms above their usual level. The path goes over QIX; nothing has changed on our side. We are checking whether a peer has moved traffic onto a longer 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.