Live  /  one.com  /  Incident

one.com: PHP vulnerability

one.com · one.comResolved2026-10-22 05:20 UTC
Public — what happened

Summary

one.com said it learned of two newly found security weaknesses in PHP, software used by many websites, and began investigating on 2026-10-21 at 10:55 UTC. It said that while it put protective measures in place, some services could be briefly disrupted, including website uploads, direct database access and calendar syncing with third-party email apps. The company reported that a PHP security update became available and that all currently supported versions (8.2 to 8.5) were patched by 14:52 UTC, with older versions still being worked on. By 16:44 UTC it said CalDAV and phpMyAdmin were back online, and the incident was marked resolved on 2026-10-22 at 05:20.

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 44, 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.