Live / Secomea / Incident
Secomea: Session Recording
Secomea · secomea.comMinor incidentResolved2026-11-09 08:37 UTC
Public — what happened
Summary
Secomea said it was looking into a problem with the Session Recording feature affecting roughly 10% of its GateManagers, where recordings might not start or might not be saved. The company said other GateManager functions, including remote access, kept working normally. It reported on 2026-11-06 at 13:01 UTC that it had found the root cause and was applying a fix, and at 17:14 UTC said its changes had restored all reported issues and it was monitoring. The incident was marked resolved on 2026-11-09 at 08:37.
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-11-06 11:14 UTC
- Investigating — 2026-11-06 11:14 UTC
- Identified — 2026-11-06 13:01 UTC
- Monitoring — 2026-11-06 17:14 UTC
- Resolved — 2026-11-09 08:37 UTC · 3 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 46, 2026, our weekly internet health report.