Live  /  one.com  /  Incident

one.com: Issue with the Companion app

one.com · one.comResolved2026-11-05 11:42 UTC
Public — what happened

Summary

one.com said some customers might not have been able to finish two-factor authentication sign-in in its Companion app, and it began investigating at 07:59 UTC on 2026-11-05. At 10:32 UTC the company said it had found the root cause and was working to restore normal service, without describing what the cause was. The incident was marked resolved at 11:42.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the one.com status & history page.

Related: one.com status & history. SquidGrid is not affiliated with one.com.