Live  /  amazee.io  /  Incident

amazee.io: CVE-2026-98432

amazee.io · amazee.ioidentified2026-11-02 00:47 UTC
Public — what happened

Summary

amazee.io said it learned of a newly disclosed Linux kernel security flaw, CVE-2026-98432, and planned emergency maintenance to install the needed updates, starting on 2026-10-30 at 04:11 UTC. The company said the work would fall in its usual maintenance hours but earlier than normal, and that customers' sites could see minor service disruption. On 2026-11-02 it reported a fix had been put in place and was being monitored, but a few minutes later said patching of all its clusters was still underway, and the incident is not marked resolved.

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 amazee.io 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 amazee.io: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the amazee.io report →

More from amazee.io

Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.

The full archive is on the amazee.io status & history page.

Related: amazee.io status & history. SquidGrid is not affiliated with amazee.io.