Live / Transmit Security / Incident
Transmit Security: Service degradation in DRS
Transmit Security · transmitsecurity.ioMinor incidentResolved2026-10-12 09:38 UTC
Public — what happened
Summary
Transmit Security reported a minor degradation in its DRS service starting at 08:56 UTC on 2026-10-12. The company said customers calling the backend /trigger-action endpoint with SDK version 2.7.0 could sporadically get errors saying their session token had expired, and it indicated the problem seemed tied to how that release changed token expiration handling. Transmit Security said it had pinpointed the issue by 09:15 UTC, put a fix in place by 09:34 UTC, and marked the incident resolved at 09:38.
Affected
Detection and Response Europe, Detection and Response US, Detection and Response Canada, Detection and Response Australia, Detection and Response Sandbox
Timeline
- Started — 2026-10-12 08:56 UTC
- Investigating — 2026-10-12 08:56 UTC (2 updates)
- Identified — 2026-10-12 09:15 UTC
- Monitoring — 2026-10-12 09:34 UTC
- Resolved — 2026-10-12 09:38 UTC · 42 min 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 Transmit Security 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 Transmit Security: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Transmit Security report →
More from Transmit Security
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.