Paris
nky-par-01 · CET- Reachability (90d)
- 99.991%
- Ping (probe avg)
- 6.2 ms
- Jitter
- 0.3 ms
- Packet loss
- 0.00%
- Edge capacity
- 10G ×2
- Peering
- FR-IX · EQUINIX FR5
Live status across our four regions, the last 90 days of uptime, and every incident we've had since launch — including the small ones nobody noticed.
4 of 4 regions reporting normal. Last full sweep .
One row per service. If anything is degraded, you'll see it here before you see it in your inbox.
One cell per day. Green is full reachability across all external probes; amber is partial degradation; red is a real outage. Planned maintenance is hatched, and excluded from SLA calculations.
We publish every incident, including the small ones nobody noticed. Outages get a written post-mortem within seven days. We do not retroactively delete entries.
Hardware ASIC fault on a top-of-rack switch caused intermittent packet drops escalating to total loss. Failover to redundant ToR completed in 34 minutes (manual cable swap required after the failover ports also showed errors). Switch replaced.
Rolling microcode update across the NVMe controller fleet. Each node drained, updated, and returned with a baked-in 15-minute soak before the next.
False-positive cascade on the storage probe cluster after one probe lost its NTP source. Affected metrics only — the underlying storage pool was nominal throughout. Probe replaced; alarm threshold tightened.
~340 Gbps attack targeted a neighbouring customer in the same upstream /20. Mitigated upstream by transit provider scrubbing; our prefixes saw no measurable impact.
Major-version OS upgrade on the redundant pair of border routers. Drained sequentially; BGP sessions re-established cleanly.
Single tenant's mis-configured guest caused an ARP storm. Suppression kicked in after 16 minutes; segment isolated. Affected tenant notified, no other tenants impacted.
Planned, announced 14 days in advance. Single-link bond drained, upgraded, returned; second link upgraded after a one-hour bake. No customer downtime.
Provisioning API returned 5xx for ~18 minutes after a misconfigured rate-limiter deploy. Existing VMs unaffected; new deployments queued and replayed once the deploy was rolled back. SLA-eligible for customers attempting provisioning during the window.