Network outage ham1
Resolved
Nov 6, 2026 at 7:55am UTC
We are resolving this incident for now. A post-incident report will be posted on the blog later today.
Affected services
Updated
Nov 5, 2026 at 10:24pm UTC
We are - again - seeing recovery of the important services. We will keep this incident open until we can confirm with our upstream that all measurements are in effect and we ourselves can confirm that recovery is rolled out at full.
Affected services
Updated
Nov 5, 2026 at 9:36pm UTC
It's now a Layer 7 HTTP DDoS, so only web-service are affected right now.
Affected services
Updated
Nov 5, 2026 at 9:24pm UTC
Traffic is flooding in from the other uplink that's currently not being filtered. We've once again reached out to our upstream and asked them to pull the route there.
Affected services
Updated
Nov 5, 2026 at 8:15pm UTC
Traffic is now being filtered by the upstream scrubbing center so we declare this resolved
Affected services
Updated
Nov 5, 2026 at 7:29pm UTC
We are still working on recovery with the upstream provider
Affected services
Updated
Nov 5, 2026 at 6:58pm UTC
We've identified a UDP flood as the source of the outage. We are working on getting things back up.
Affected services
Updated
Nov 5, 2026 at 6:08pm UTC
We've identified this outage to be at our upstream provider and are waiting for confirmation on the issue.
Affected services
Created
Nov 5, 2026 at 6:04pm UTC
We are investigating degraded availability in the whole ham1 region.
Affected services