Live / one.com / Incident
one.com: Issues with website access
one.com · one.comMinor incidentResolved2026-10-07 00:35 UTC
Public — what happened
Summary
one.com said that starting at 19:12 UTC on 2026-10-06, some of its customers were having trouble reaching websites, with pages timing out or loading blank. The company stated that no data would be lost as a result. By 19:47 UTC it said it had found the problem, though it did not describe what it was, and it reported putting a fix in place at 20:21 UTC. After a period of monitoring, the incident was marked resolved at 00:35 on 2026-10-07.
Affected
Webhosting
Timeline
- Started — 2026-10-06 19:12 UTC
- Investigating — 2026-10-06 19:12 UTC
- Identified — 2026-10-06 19:47 UTC
- Monitoring — 2026-10-06 20:21 UTC (2 updates)
- Resolved — 2026-10-07 00:35 UTC · 5h 22m 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 one.com 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 one.com: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the one.com report →
More from one.com
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.