Live / F5 / Incident
F5: F5 Distributed Cloud – Non-Disruptive - Remote Reset Response Issue - INC-20261029-538
F5 · volterra.ioResolved2026-11-05 22:22 UTC
Public — what happened
Summary
F5 said it was looking into a reporting oddity in F5 Distributed Cloud in which some web responses showed a reset notice (http2.remote_reset) next to a normal success code, first seen on October 17 and posted about on October 30. The company said end users were not affected and the services kept working normally throughout. F5 said its teams tested a hotfix to correct how these responses are labeled, and on November 4 it said testing was done and rollout would be gradual. By November 5 F5 said the fix had reached all Regional Edges, and the incident was later marked resolved after monitoring.
Affected
HTTP Load Balancer
Timeline
- Started — 2026-10-30 06:07 UTC
- Investigating — 2026-10-30 06:07 UTC (5 updates)
- Identified — 2026-11-04 07:51 UTC
- Monitoring — 2026-11-05 10:49 UTC
- Resolved — 2026-11-05 22:22 UTC · 7 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach F5 against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for F5: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the F5 report →
More from F5
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.