Live / Secomea / Incident
Secomea: Degraded Performance on GateManagers
Secomea · secomea.comMinor incidentResolved2026-10-23 08:11 UTC
Public — what happened
Summary
Secomea said it began looking into network disruptions on October 22, 2026 at 13:24 UTC that could make GateManagers briefly unresponsive when people tried to reach them. The company classed the issue as minor and described it as degraded performance. Its posted text said engineers were working on it and did not name a cause. The incident was marked resolved on October 23 at 08:11.
Affected
GateManager 00, GateManager 01, GateManager 02, GateManager 03, GateManager 04, 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, GateManager 100, GateManager 101, GateManager 102, GateManager 103, GateManager 104, GateManager 105 and 12 more
Timeline
- Started — 2026-10-22 13:24 UTC
- Investigating — 2026-10-22 13:24 UTC
- Resolved — 2026-10-23 08:11 UTC · 18h 47m 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 44, 2026, our weekly internet health report.