Rewindex

CompaniesTwingateIncidents

Twingate: Controller downtime

CriticalStatus: postmortemStarted Resolved (1.8 h)5 updatesstspg.io (opens in new tab)

Affected components: Connector HeartbeatTwingate Controller

Timeline of updates

  1. identified

    We've identified the issue, which is being caused by excessive memory usage on our infrastructure.

  2. monitoring

    We're resolved the immediate issue by adding additional processing capacity and increasing memory limits on our controller infrastructructure.

  3. monitoring

    The system is now confirmed as fully operational. We are working on an incident report and taking steps to ensure that this issue will not happen in the future.

  4. resolved

    This incident has been resolved.

  5. postmortem

    **Components impacted** Controller **Summary** The controller was unavailable to service new authentication requests from approximately 15:17 to 15:19 UTC. The result was that during this period of time, new connection requests were rejected. Existing connections were not impacted. At the end of the outage period, normal service resumed with no remediation required. **Root cause** Leading up to the start of the outage period, automated monitoring alerted us to spikes in memory usage. At approximately 15:16 UTC we introduced a change to our cluster that was intended to increase memory availability. At approximately 15:17 UTC as this change was rolled out, it had the unintended consequence that resulted in a decrease in service availability, with the resulting rejection of most requests. **Corrective actions** At 15:18 UTC, seeing the decrease in service availability, we reverted the change and simultaneously made additional hardware available to the cluster. Normal service resumed approximately 45 seconds later as the change propagated. Looking ahead, we plan to: 1. Investigate introducing decoupling between inbound requests and our backend as the likely cause of the memory spikes that triggered the change that caused the outage.

Changes Rewindex caught on this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Twingate profileRecent Twingate incidentsMarkdownJSON