Live / Secomea / Incident
Secomea: Security maintenance: Possible service disruptions
Secomea · secomea.comMajor incidentResolved2026-11-10 09:01 UTC
Public — what happened
Summary
Secomea said it began security maintenance on 2026-10-30 at 13:06 UTC to apply updates for a vulnerability it identified as CVE-2026-98432. The company warned that users could see slower responses or brief interruptions when accessing the platform or making remote connections. It also said Secomea Prime is unavailable for the time being. The incident is still listed as investigating, and Secomea said it will post another update once the work is complete.
Affected
Knowledgebase, GateManager 00, Prime Platform, GateManager 01, FTP, GateManager 02, Mail Relay 1, GateManager 03, Mail Relay 2, GateManager 04, NTP, GateManager 06, GateManager 08, GateManager 10, GateManager 11, GateManager 12, GateManager 14, GateManager 16, GateManager 21, GateManager 22, GateManager 23, GateManager 41, GateManager 51, GateManager 52 and 16 more
Timeline
- Started — 2026-10-30 13:06 UTC
- Investigating — 2026-10-30 13:06 UTC (6 updates)
- Monitoring — 2026-11-06 17:15 UTC
- Resolved — 2026-11-10 09:01 UTC · 11 days 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 Secomea 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 Secomea: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Secomea report →
More from Secomea
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.