Live / one.com / Incident
one.com: Increased processing times
one.com · one.comMinor incidentResolved2026-11-05 15:44 UTC
Public — what happened
Summary
one.com reported a minor incident beginning at 13:54 UTC on 2026-11-05, in which several of its systems were responding more slowly than normal. The company said services stayed available, but tasks such as placing orders, resetting passwords for user and email accounts, and creating MySQL databases could take longer to finish. At the start, one.com said it had no estimate for a fix and was still working to find the underlying cause. The incident is now marked resolved as of 15:44 UTC, and the text provided does not say what caused it.
Affected
Filemanager, Controlpanel
Timeline
- Started — 2026-11-05 13:54 UTC
- Investigating — 2026-11-05 13:54 UTC
- Resolved — 2026-11-05 15:44 UTC · 1h 50m 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 46, 2026, our weekly internet health report.