Live / Seravo / Incident
Seravo: Critical PHP vulnerabilities
Seravo · seravo.comResolved2026-10-22 05:48 UTC
Public — what happened
Summary
Seravo said it was aware of serious security weaknesses in PHP, announced on 2026-10-20, that affect all PHP versions and could put customer websites at risk. Starting 2026-10-21 at 07:35 UTC, the company said it applied initial protective measures for all customers, though it noted that none gave full protection, and it offered to take sites offline temporarily on request. Seravo said it began rolling out updated PHP versions once the upstream developers released them, and by 21:34 UTC reported the update had been applied and that it was monitoring the situation. The incident was marked resolved at 05:48 on 2026-10-22.
Timeline
- Started — 2026-10-21 07:35 UTC
- Identified — 2026-10-21 07:35 UTC (7 updates)
- Monitoring — 2026-10-21 21:34 UTC
- Resolved — 2026-10-22 05:48 UTC · 22h 13m 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 Seravo 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 Seravo: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Seravo report →
More from Seravo
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.