Twingate

Affected: Downloads

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-08 22:04 UTC

   Our upstream provider for Linux packages is having an issue impacting Twingate's Linux package downloads.

2. investigating 2026-07-08 22:06 UTC

   We are continuing to investigate this issue.

3. investigating 2026-07-08 22:07 UTC

   We are continuing to investigate this issue.

4. investigating 2026-07-09 00:24 UTC

   We are continuing to investigate this issue.

5. resolved 2026-07-09 00:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Authentication - Enterprise, Authentication - Social, MFA, Authorization, Connector Heartbeat

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-28 09:24 UTC

   We are currently investigating this issue.

2. investigating 2026-05-28 09:25 UTC

   We are continuing to investigate this issue.

3. investigating 2026-05-28 10:55 UTC

   We are continuing to investigate this issue. We have narrowed the scope of the issue to Control Plane - Authorization.

4. investigating 2026-05-28 10:57 UTC

   We are continuing to investigate this issue. We are seeing recovery and have updated the Control Plane - Authorization status to partial outage.

5. monitoring 2026-05-28 12:02 UTC

   The issue has been fixed. We are still working with cloud provider on root cause.

6. monitoring 2026-05-28 13:47 UTC

   We're continuing to work with our cloud provider to identify the root cause.

7. monitoring 2026-05-28 16:22 UTC

   We're continuing to work with our cloud provider to identify the root cause.

8. resolved 2026-05-28 17:27 UTC

   We are currently awaiting the completion of our cloud provider’s investigation into the issue. In the meantime, we continue to closely monitor the system, and all service metrics have returned to normal operating levels. At this time, we are closing this incident. We will...

9. postmortem 2026-06-03 16:39 UTC

   # Incident Report – Authorization Service Degradation ## Components Impacted Control Plane – Authorization Service ## Summary On May 28, 2026, between 10:00 UTC and 12:30 UTC, Twingate experienced a degradation of its Authorization service that affected approximately 15% of...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Americas Relays, EMEA Relays, APAC Relays

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-08 08:44 UTC

   We are seeing an issue with relay443. We are investigating. Note: These are special relays that offer connectivity over port 443 and are used by a subset of customers. So majority of customers shouldn't be seeing an issue,

2. identified 2026-05-08 10:28 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2026-05-08 10:55 UTC

   The fix has been rolled out and relays443 are now fully functional.

4. postmortem 2026-05-14 09:19 UTC

   **Components impacted** * Data Plane - Relay 443 flows only **Summary** On May 9, 2026, a subset of Twingate customers experienced an interruption to network access affecting Relay 443 connectivity. The disruption lasted approximately 2 hours and 10 minutes and was caused by a...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Downloads

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. monitoring 2025-10-20 15:49 UTC

   The AWS outage is affecting GemFury, a service we use to host our APT/RPM packages.

2. monitoring 2025-10-20 17:02 UTC

   Our testing indicates that APT/RPM packages are now operational, though Gemfury continues to report degraded performance. We will continue to monitor.

3. resolved 2025-10-20 22:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Reports Downloads, Admin Console, Network Dashboards

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-06-12 18:18 UTC

   We are currently investigating service issues related to our cloud provider. The disruption is affecting the Twingate service, including the Admin Console, Report Downloads, and Network Dashboards. We will continue to monitor the situation and provide updates as we learn more.

2. identified 2025-06-12 19:15 UTC

   Our cloud provider has acknowledged a service issue. We are continuing to monitor the situation and will provide updates as we learn more.

3. monitoring 2025-06-12 20:49 UTC

   Our cloud provider has indicated that their service is recovering. Impacted Twingate services are now back online, but we are currently processing a backlog of Events. We expect this to be fully resolved within the next few hours and will provide an update when processing is...

4. resolved 2025-06-12 23:49 UTC

   Our cloud provider has confirmed full recovery of their services, and our backlog of Events has now been fully processed. We consider this incident fully resolved.

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Authentication - Enterprise, Identity Providers Sync, Public API, Authentication - Social, Admin Console, MFA, Authorization, Realtime Updates, Connector Heartbeat, Client Log Upload, 3rd Party Integrations, Network Dashboards, DNS Filtering Dashboards

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-05-28 20:53 UTC

   The issue has been identified and a fix is being implemented.

2. monitoring 2025-05-28 21:16 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-05-28 21:32 UTC

   This incident is resolved now. We'll provide a post-mortem as soon as we have details.

4. postmortem 2025-06-16 18:26 UTC

   ### **Incident Duration** **UTC Time**: May 28, 2025, from **20:45 to 21:14** \(29 minutes\) ### **Components Impacted** **Control Plane Services** * Authentication \(Enterprise & Social\) * Multi-Factor Authentication \(MFA\) * Authorization * Connector Heartbeat **Management...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Events Processing, Reports Downloads, Network Dashboards, DNS Filtering Dashboards

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-04-02 16:19 UTC

   We are seeing higher latency than usual with our cloud provider's APIs to process data used for our dashboards and reports. They confirmed the issue with their service. We hope this should be resolved soon.

2. monitoring 2025-04-02 16:32 UTC

   The Big Query service latencies have dropped and we see improvements with our internal dashboards.

3. resolved 2025-04-02 17:25 UTC

   All of internal alerts are cleared. You should not see delays/errors with dashboards and reports any longer.

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Authentication - Enterprise, Identity Providers Sync, Public API, Authentication - Social, Admin Console, MFA, Authorization, Realtime Updates, Connector Heartbeat, Client Log Upload, 3rd Party Integrations, Network Dashboards, DNS Filtering Dashboards

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-03-21 20:10 UTC

   We are currently investigating this issue.

2. monitoring 2025-03-21 20:41 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-03-21 21:13 UTC

   This incident has been resolved.

4. postmortem 2025-03-28 15:14 UTC

   **Twingate Public RCA: March 21, 2025 Authentication/Authorization Incident** **Summary** On March 21, 2025, between 21:10 and 21:41 UTC, a subset of authentication and authorization requests to Twingate services experienced elevated error rates. The issue was mitigated by 21:41...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: DNS Filtering Dashboards

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-02-24 22:26 UTC

   We're currently experiencing a temporary disruption with the DNS Activity Reports. The team is working on restoring access, and we'll have them back up shortly.

2. monitoring 2025-02-25 01:28 UTC

   Recent DNS Activity is now restored and we are monitoring the system.

3. resolved 2025-02-25 01:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Identity Providers Sync

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-10-20 03:52 UTC

   We're seeing increased errors when syncing trusted devices from Jamf. We're currently investigating.

2. investigating 2024-10-20 12:12 UTC

   This incident is still being investigated. It started after a recent upgrade performed by Jamf. We have reached out to Jamf on the issue and working with them on resolution.

3. resolved 2024-10-21 21:01 UTC

   Issue with syncing trusted devices from Jamf has been fixed.

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Events Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-09-20 04:57 UTC

   We've detected an issue with DNS events ingestion affecting some of our customers who are not able to see DNS events when exporting to S3. We're currently looking for root cause.

2. identified 2024-09-20 05:22 UTC

   We've identified the issue and are working on a fix.

3. monitoring 2024-09-20 05:24 UTC

   DNS events are being ingested again and we're monitoring the system.

4. resolved 2024-09-20 05:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Authentication - Social

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. monitoring 2024-08-14 23:29 UTC

   GitHub is currently experiencing an incident affecting its authentication - https://www.githubstatus.com/incidents/kz4khcgdsfdv Social login via Github is therefore temporarily not working until GitHub resolves their issues.

2. resolved 2024-08-15 00:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: DNS Filtering Dashboards

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-07-29 21:27 UTC

   We are seeing issues with Secure DNS (Internet Security) Dashboards loading. We are investigating.

2. investigating 2024-07-29 21:32 UTC

   We are continuing to investigate this issue.

3. identified 2024-07-29 21:35 UTC

   Issue has been identified and we're working on a fix.

4. monitoring 2024-07-29 21:42 UTC

   Dashboards are gradually coming back online.

5. resolved 2024-07-29 22:11 UTC

   Dashboard are back to normal.

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Events Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-07-20 13:20 UTC

   We are having an issue with S3 Sync of Internet Security events. Team is engaged and issue is being investigated.

2. monitoring 2024-07-20 14:10 UTC

   There was an ingestion delay that's fixed . We see logs flowing again.

3. resolved 2024-07-20 14:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Events Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2024-07-19 20:42 UTC

   We are seeing issues with AWS S3 Sync of Internet Security events. We are currently investigating.

2. investigating 2024-07-19 20:42 UTC

   We are continuing to investigate this issue.

3. identified 2024-07-19 21:18 UTC

   We have identified the issue and working on a fix. Will update once fix is deployed.

4. resolved 2024-07-19 22:09 UTC

   The fix has been pushed to production and we confirmed Internet Security Events are now syncing to S3 buckets again.

Excerpts are shortened. Read the full incident on Twingate's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-07-11 12:47 UTC

   During the incident , some of our customers MFA tokens became invalid. Less than 15 of our customers were impacted by this incident. We identified the issue and will make this key rotation safer going forward so it doesn't impact any of our customers. Impact Duration: 12:47 -...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Public API, Admin Console, Connector Heartbeat

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2024-06-26 22:01 UTC

   On June 26, 2024, between 8:16 pm UTC and 8:28 pm UTC, Twingate experienced several database connectivity alerts due to a failed rollout of one of its components. The rollout was promptly reversed, and our existing reliability measures prevented any major disruption to customer...

2. postmortem 2024-06-29 08:28 UTC

   **Components impacted** Management: Public API Management: Admin Console ‌ **Summary** On June 26, 2024 between 20:16 and 20:24 UTC, Twingate’s SQL proxies restarted, causing a brief failure to a small percentage of calls made to our Public API \(Terraform, Pulumi, k8s Operator,...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Admin Console

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-05-14 23:38 UTC

   Recent DNS Activity screen on the Admin console isn't available.

2. monitoring 2024-05-14 23:43 UTC

   Recent DNS Activity screen on the Admin console is back up.

3. resolved 2024-05-14 23:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Authentication - Enterprise

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2024-04-30 18:03 UTC

   We are currently investigating this issue.

2. investigating 2024-04-30 18:03 UTC

   We are continuing to investigate this issue.

3. investigating 2024-04-30 18:05 UTC

   A software rollout has broken the logins with Github. We are working on rolling out a hotfix.

4. resolved 2024-04-30 18:38 UTC

   We have successfully rollout the HotFix for the issue with Github logins.

5. postmortem 2024-05-03 19:00 UTC

   **Components impacted** Control Plane: Authentication **Summary** On April 30, 2024, between 15:44 and 18:38 UTC, users were unable to login to Twingate through GitHub. The Twingate Engineering team investigated the issue upon receiving support communications and found that...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Admin Console

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-04-19 21:45 UTC

   Recent DNS Activity on admin is unavailable. We have identified the issue and working on a fix.

2. monitoring 2024-04-19 21:58 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-04-19 22:04 UTC

   This incident has been resolved.

4. postmortem 2024-04-25 14:44 UTC

   **Components impacted** Management: Admin Console **Summary** On April 20, 2024, between 5:32 GMT and 6:57 GMT, Recent DNS Activity on the Admin Console became unavailable. Shortly after the incident began, the Twingate on-call team received alerts regarding abnormal database...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Admin Console

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-01-31 20:29 UTC

   We’re currently investigating an issue where DNS filtering logs are sometimes empty.

2. identified 2024-02-01 00:14 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2024-02-01 03:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Twingate's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2023-12-11 17:00 UTC

   Summary On Dec 11, 2023 between the hours of 5:02 pm UTC and 6:24 pm UTC, Twingate received network connectivity alerts at 3 distinct times, each for a few minutes. After investigation, it was identified that a change in our application had caused our connections to exceed the...

2. postmortem 2023-12-12 05:44 UTC

   **Components impacted** Control Plane: Authn, Authz, Connector Heartbeat Management: Admin Console, Public API, Identity Providers Sync **Summary** On Dec 11, 2023 between the hours of 5:02 pm UTC and 6:24 pm UTC, Twingate received network connectivity alerts at 3 distinct...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Authentication - Enterprise, Public API, Admin Console, Authorization, Connector Heartbeat

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2023-08-19 08:01 UTC

   We are seeing issues with Twingate service and investigating.

2. investigating 2023-08-19 08:01 UTC

   We are continuing to investigate this issue.

3. resolved 2023-08-19 08:21 UTC

   This incident has been resolved. We'll publish RCA as soon as we can.

4. postmortem 2023-08-23 06:11 UTC

   **Summary** On August 19 at 7:51 AM UTC, Twingate received alerts of issues with the login services. Within a few minutes, the Twingate engineering team began investigating. The team quickly identified that our backend was seeing excessive timeouts from a 3rd-party API,...

Excerpts are shortened. Read the full incident on Twingate's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2023-06-22 12:30 UTC

   Admin Console Authentication is broken for our tenants that utilize JumpCloud IDP integration. This was due to a bug in authentication flows with our latest software that was deployed at 15:24 UTC on June 21st. Resolution was accomplished by reverting to the previous software at...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Admin Console

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2023-06-07 17:42 UTC

   We are seeing issues with our admin consoles not loading properly. It's been investigated.

2. resolved 2023-06-07 17:51 UTC

   This incident has been resolved. It's due to an issue with a software update. We are working on a plan to avoid this in the future. This impacted authentication flow too. Already authenticated flows continued to function.

3. postmortem 2023-06-16 01:05 UTC

   **Summary** On June 7th 17:08 UTC, a new version of our Controller software was rolled out. Shortly after the rollout completed, our on-call team received automated exception alerts and began investigating. The new version had inadvertently included changes to clean up our...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Authentication - Enterprise, Public API, Admin Console, Authorization, Connector Heartbeat

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2023-04-25 15:57 UTC

   Our cloud provider is having a networking issue in us-east4 region that caused 500 errors for our customers hitting that region. Due to retry logic in our service, this shouldn't have caused issues for our customers. We diverted traffic to other regions and no traffic is handled...

2. resolved 2023-04-25 17:14 UTC

   Our cloud provider has announced that the issue with us-east4 region has been resolved. We will be monitoring a little bit more before re-enabling traffic on that region.

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Americas Relays, Peer-to-Peer

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2023-02-14 02:06 UTC

   We see issues with one of our relay clusters (US relay cluster 2) and investigating.

2. identified 2023-02-14 02:37 UTC

   We found issues with 2 of our relay clusters, one in US (region: Virgina and one in Europe (region: Zurich). While we are working on bringing them up, the connectors and clients should have automatically reconnected to the other relay clusters, which may cause some slowness for...

3. resolved 2023-02-14 03:34 UTC

   We have identified the issue and a fix is implemented. Both relays clusters are healthy and processing requests.

4. postmortem 2023-02-17 16:46 UTC

   **Components impacted** Relay clusters in us-east4 \(Ashburn, Virginia\) and europe-west6 \(Zurich, Switzerland\) ‌ **Summary** We’ve recently been working on adding spot instance scaling to our Relay cluster infrastructure. On Feb 14th at 01:00 UTC, we initiated this upgrade...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Authentication - Enterprise, Public API, Admin Console, Downloads, Authorization, Connector Heartbeat

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-01-24 20:09 UTC

   We are currently investigating this issue.

2. investigating 2023-01-24 20:44 UTC

   Twingate Engineering is fully engaged and we are still investigating the issue. We'll provide further updates as soon as we can.

3. investigating 2023-01-24 21:20 UTC

   Twingate engineering is still working on identifying the root cause of the issue. We'll continue to provide updates as we find out more. - Public-api is disabled. - Admins and Logins should work. - Still seeing issue with Authorization.

4. investigating 2023-01-24 21:30 UTC

   We are continuing to investigate this issue.

5. monitoring 2023-01-24 22:05 UTC

   We have identified the issue and Twingate system looks healthy since 1:48 pm PST. We are still monitoring the issue. Public-API is still being kept down for the time being.

6. monitoring 2023-01-24 22:32 UTC

   Public-API (Admin-API) has been brought up too. While all the metrics for the service looks healthy, we will continue to monitor them.

7. resolved 2023-01-25 01:03 UTC

   We are marking the issue as resolved. The system works as expected with healthy metrics.

8. postmortem 2023-01-28 00:55 UTC

   **Summary** On January 24 at 19:58 UTC, our on-call team started to receive automated alerts regarding system performance degradation. The team began an investigation and, by 20:02 UTC, the degradation had escalated to a point where some Twingate Clients began to experience...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Admin Console

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2022-09-26 21:59 UTC

   Currently Twingate admin is broken. We have identified the issue and rolling out the fix.

2. resolved 2022-09-26 22:03 UTC

   Twingate admin is fully functional again.

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Authentication - Enterprise, Authorization, Connector Heartbeat

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2022-09-20 08:05 UTC

   We are currently investigating this issue.

2. investigating 2022-09-20 08:05 UTC

   We are continuing to investigate this issue.

3. investigating 2022-09-20 08:56 UTC

   We are working with our cloud provider to identify the issue

4. identified 2022-09-20 09:32 UTC

   The issue has been identified and a fix is being implemented. the system is slowly recovering. We will keep update.

5. identified 2022-09-20 10:17 UTC

   We are still working on the fix. It takes a bit longer then we expected.

6. investigating 2022-09-20 11:07 UTC

   Although we identified a problem earlier it appears that it was not the root cause of the issue. We are serving some customer requests but there remains an ongoing impact to service availability that we are investigating.

7. monitoring 2022-09-20 11:40 UTC

   We have restored service for all customers but are verifying each of our internal services in-turn and checking for any residual issues

8. resolved 2022-09-21 04:04 UTC

   This incident has been resolved.

9. postmortem 2022-09-23 18:42 UTC

   **Summary** On September 21 at 4:14am UTC, Twingate released a new controller version as part of improvements to the authorization engine. This new release contained both code changes and involved data migration. The change caused an unexpectedly significant increase in load on...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Admin Console

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2022-09-19 21:48 UTC

   Our infrastructure is running behind which is causing delays in our display of network events in the admin console. No data has been lost and the system should be caught up shortly.

2. resolved 2022-09-20 00:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Docs

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2022-08-24 00:21 UTC

   Twingate docs site (docs.twingate.com) is down due to issues with our vendor.

2. monitoring 2022-08-24 00:53 UTC

   Twingate docs site is up now but we are still monitoring the issue as our docs hosting provider hasn't released an update yet on the resolution of the issue.

3. resolved 2022-08-24 04:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Twingate's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2022-08-17 10:20 UTC

   We are investigating an issue with our third-party repository provider for Linux packages. While it is not impacting Twingate clients or connectors it does appear to be preventing download or update of client/connector packages.

2. identified 2022-08-17 10:40 UTC

   The issue is due to a third party incorrect infrastructure upgrade

3. monitoring 2022-08-17 12:14 UTC

   Our repository third party is recovering.

4. resolved 2022-08-17 12:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: www.twingate.com

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2022-08-16 14:53 UTC

   Due to an issue with our service provider, our homepage (www.twingate.com) is down. There should be no impact to service for our customers.

2. monitoring 2022-08-16 15:06 UTC

   Our service provider still reports an issue with their network however our web site came back up and has been operational. We'll continue to monitor.

3. monitoring 2022-08-16 15:14 UTC

   We are continuing to monitor for any further issues.

4. resolved 2022-08-16 15:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Twingate's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2022-08-09 05:00 UTC

   Due to unexpected delays associated with a planned ingress update, Twingate’s controller was partially unavailable for ~2.5 minutes between 10:15 pm and 10:18 pm PST. During this short window, no existing network connections were interrupted. New connections were blocked during...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Americas Relays

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2022-07-19 20:42 UTC

   Our cloud provider (Google) is experiencing an incident affecting multiple services in their eu-west2 (London) region. Our service spans multiple regions but users may experience intermittent slowness.

2. monitoring 2022-07-20 06:10 UTC

   Our cloud provider (Google) is continuing to experience the outage in Europe-west2 (London) region. This is not directly impacting Twingate service as our clients and connectors have built-in redundancy by connecting to multiple regions but users in that region may experience...

3. resolved 2022-07-20 09:06 UTC

   Our cloud provider (Google) incident is now resolved, and our services in eu-west2 (London) are fully operational.

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Docs

Failure mode: CDN or edge layer failed or served bad content. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2022-06-21 07:11 UTC

   The issue has been identified by our vendor as a CDN issue, we will continue to monitor and provide updates.

2. identified 2022-06-21 07:34 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2022-06-21 07:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Authentication - Enterprise, Public API, Admin Console, Authorization, Connector Heartbeat

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2022-06-03 04:16 UTC

   Controller is currently experiencing an outage. Our team is investigating the issue.

2. investigating 2022-06-03 04:54 UTC

   During a planned Kubernetes version upgrade, our application started to fail. We failed to our standby region/cluster, but it has the same issue. We are downgrading Kubernetes version and continuing to working on the issue.

3. monitoring 2022-06-03 05:13 UTC

   After reverting back the Kubernetes version and failing back to our previously Active cluster, we see Twingate Service recovered. We continue to monitor.

4. resolved 2022-06-03 06:49 UTC

   We are marking the incident as resolved. We will provide post-mortem notes as soon as we have them.

5. postmortem 2022-06-10 00:05 UTC

   **Summary** On June 3rd at 3 AM UTC, Twingate started a regular Kubernetes upgrade on its main cluster. This maintenance is usually done once a month and has been performed successfully many times prior to this upgrade. It includes a version upgrade of the cluster followed by a...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Authentication - Enterprise, Public API, Admin Console, MFA, Authorization, Connector Heartbeat

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2022-05-13 15:38 UTC

   We are currently investigating the incident.

2. investigating 2022-05-13 15:48 UTC

   We have seen improvements; we are monitoring the situation. We'll update as we find out more details on the issue.

3. investigating 2022-05-13 15:55 UTC

   We are continuing to investigate this issue.

4. investigating 2022-05-13 15:57 UTC

   The system is fully up. We will continue to monitor.

5. resolved 2022-05-13 17:17 UTC

   We are marking this issue resolved. The impact was between 8:31 am to 8:44 am. We will add the post mortem to the incident as soon as we have it ready.

6. postmortem 2022-05-18 00:01 UTC

   **Summary** At approximately 15:31 UTC on May 13, 2022, we received alerts from our monitoring systems pointing to a problem with Twingate. Our cloud provider’s load balancer started to return 502 \(Bad Gateway Error\) due to issues with our backend system. Looking into our...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Americas Relays, Admin Console, Connector Heartbeat

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2022-01-19 14:47 UTC

   We are aware of an incident affecting our production system and are currently actively investigating the issue. We will be posting regular updates pertaining to this incident.

2. investigating 2022-01-19 15:23 UTC

   Our engineers have isolated the problem to a network connectivity issue between our application servers and our database infrastructure. Our team is working to restore network connectivity and we will continue to post regular updates.

3. monitoring 2022-01-19 15:52 UTC

   We have re-established connectivity and Twingate services have been restored. We are continuing to monitor our systems.

4. resolved 2022-01-19 17:16 UTC

   We are continuing to monitor the system, and it remains stable and available. We are closing out this incident and we will follow up with a post mortem here.

5. postmortem 2022-01-23 07:19 UTC

   **Summary** At approximately 02:26 UTC on January 19th, we observed an increase in latency between our API layer and our backend database system. Within a few minutes, this spike in latency developed into an outage that resulted in 90% of requests returning one of two responses...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Connector Heartbeat

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2022-01-14 22:31 UTC

   We are currently investigating degraded performance of loading the MFA page of Twingate. Customers are experiencing slower page load times due to a CDN issue but services are still functional and available. We will be posting regular updates pertaining to this incident.

2. identified 2022-01-14 22:41 UTC

   We have identified the issue and are currently switching to our backup CDN.

3. monitoring 2022-01-14 22:58 UTC

   We have switched to our backup CDN and will continue to monitor the system.

4. resolved 2022-01-15 01:38 UTC

   We are closing this incident as the MFA challenge page has been operating normally since our last update.

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Admin Console

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2021-12-15 19:12 UTC

   The admin console is currently experiencing an outage caused by our 3rd party billing system being unavailable. Our team is investigating the issue and working on a fix currently. This issue is isolated to loading the admin console and does not affect any resource access or end...

2. identified 2021-12-15 19:13 UTC

   The root cause of the issue has been identified and a fix is in progress. We will post another update shortly.

3. monitoring 2021-12-15 19:33 UTC

   A fix has been deployed and the admin console is now available to all customers. We'll continue to monitor the system for the next 30 minutes before marking this incident as resolved.

4. monitoring 2021-12-15 20:05 UTC

   We have received confirmation from our 3rd party billing provider that they are aware of their system outage and are working on a fix. We will resolve this incident when the 3rd party system is available. Until this incident is marked as resolved, no billing functionality will...

5. resolved 2021-12-15 21:22 UTC

   Our 3rd party billing system is now available and we are marking this incident as resolved. We will follow up with a post mortem update.

6. postmortem 2021-12-15 21:27 UTC

   **Components impacted** * Admin console **Summary** At 18:59 UTC we received an automated alert that requests to our 3rd party billing system \(Chargebee\) were failing. A few minutes later we confirmed that this was causing the Twingate admin console interface to fail to load...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Connector Heartbeat

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2021-12-15 15:54 UTC

   We are aware of and investigating reports that customers using Okta for authentication are unable to login. It appears that customers' Okta domains are not reachable. At this stage, we are not aware of any issue affecting Twingate services itself and are working to restore...

2. monitoring 2021-12-15 16:01 UTC

   We are observing that Okta appears available again. Customers that use Okta as their Identity Provider should try again to login if they have experienced trouble logging in.

3. resolved 2021-12-15 16:54 UTC

   Customers using Okta should now be able to login without issue. We understand that the problem was related to an internet connectivity issue unrelated to Twingate that is now resolved.

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Connector Heartbeat

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2021-12-13 17:08 UTC

   We are currently investigating this issue.

2. investigating 2021-12-13 17:41 UTC

   We are continuing to investigate this issue.

3. investigating 2021-12-13 18:07 UTC

   We are continuing to investigate this issue. We will be posting regular updates pertaining to this incident.

4. investigating 2021-12-13 18:38 UTC

   We are continuing to investigate this issue. We will be posting regular updates pertaining to this incident.

5. investigating 2021-12-13 19:08 UTC

   We are continuing to investigate this issue. We have narrowed the source of the problem to the public-facing frontend servers that handle requests inbound to our service. As a result, this is broadly affecting our public API, the private API calls used by Clients and Connectors,...

6. investigating 2021-12-13 19:12 UTC

   Inbound requests are now being accepted and the service is operational again. We have verified that all operational tests are succeeding. We are continuing to investigate to determine the root cause of this incident.

7. monitoring 2021-12-13 19:21 UTC

   We are continuing to monitor the system, and we are still investigating the root cause of the outage. We will continue to post additional updates regularly.

8. monitoring 2021-12-13 20:39 UTC

   We are continuing to monitor the system, and it remains stable and available. We are investigating the root cause of the outage. We will continue to post additional updates regularly.

9. monitoring 2021-12-13 22:12 UTC

   We are continuing to monitor the system, and it remains stable and available. We are investigating the root cause of the outage. We will post our next update at 17:00 PST / 01:00 UTC.

10. monitoring 2021-12-14 01:07 UTC

    We are continuing to monitor the system, and it remains stable and available. We are investigating the root cause of the outage. We will post our next update at 21:00 PST / 05:00 UTC.

11. monitoring 2021-12-14 05:21 UTC

    We are continuing to monitor the system, and it remains stable and available. We are investigating the root cause of the outage. We will post our next update at 09:00 PST / 17:00 UTC.

12. resolved 2021-12-14 17:42 UTC

    We are continuing to monitor the system, and it remains stable and available. We are closing out this incident, and we will continue to post updates and follow up with a post mortem here.

13. postmortem 2021-12-21 04:35 UTC

    **Components impacted** * Controller **Summary** At approximately 17:06 UTC on December 13th, we observed an increase in latency between our API layer and our backend database system. Within a few minutes, this spike in latency developed into an outage that resulted in 90-95% of...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Americas Relays, Connector Heartbeat

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2021-11-16 17:53 UTC

   We are investigating an outage report with regards to Twingate. At this time we suspect it is an issue affecting broader Internet services and is not isolated to Twingate. We will continue to post regular updates as we learn more.

2. investigating 2021-11-16 18:06 UTC

   We are continuing to investigate this issue.

3. investigating 2021-11-16 18:16 UTC

   The Twingate admin console is now accessible and the Twingate Controller is operational. Customers may need to restart Connectors to restore connectivity to resources due to the nature of the networking outage. The originating cause appears to be related to an outage in Google...

4. monitoring 2021-11-16 18:29 UTC

   We are continuing to monitor the status of the service. Customers may need to restart Connectors to restore connectivity to resources due to the nature of the networking outage.

5. monitoring 2021-11-16 18:29 UTC

   We are continuing to monitor for any further issues.

6. monitoring 2021-11-16 19:08 UTC

   We have verified that all of our infrastructure is fully operational at this time and will continue to monitor for any changes. Until our service provider (Google Cloud Platform) has closed their incident, we will leave this incident open in Monitoring status and provide regular...

7. monitoring 2021-11-16 20:16 UTC

   Google Cloud Platform has marked their Cloud Networking issue as resolved and has posted a status update: https://status.cloud.google.com/incidents/6PM5mNd43NbMqjCZ5REh We are continuing to monitor our infrastructure and will mark this incident as resolved when we are confident...

8. resolved 2021-11-16 22:41 UTC

   We are marking this issue as resolved as our monitoring shows that our infrastructure is operating normally and Google Cloud Platform has resolved the incident on their network. We will be following up with a post-mortem shortly.

9. postmortem 2021-11-19 23:53 UTC

   **Components impacted** Controller Relays **Summary** Twingate services were unavailable to service requests from approximately 17:48 to 20:09 UTC on November 16th. The result was that during this period of time, access to Twingate and protected resources was limited, existing...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Connector Heartbeat

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2021-11-05 18:37 UTC

   We are looking into it we will provide more info as soon as we have it

2. investigating 2021-11-05 18:49 UTC

   We are continuing to investigate this issue.

3. investigating 2021-11-05 18:53 UTC

   We are back and operational now. We are still investigating the root cause.

4. investigating 2021-11-05 18:54 UTC

   We are continuing to investigate this issue.

5. monitoring 2021-11-05 21:05 UTC

   We are still investigating the root cause of the incident. We didn't find any issue on our side, and we are working with our cloud provider support team to investigate the matter further.

6. resolved 2021-11-06 06:30 UTC

   This incident has been resolved.

7. postmortem 2021-11-09 04:15 UTC

   **Components impacted** Relay Controller **Summary** A physical hardware failure occurred in a node within one of our Eastern US Relay clusters at approximately 18:19 UTC. Connectors and Clients attached to this node automatically failed over to a new node. This failover process...

Excerpts are shortened. Read the full incident on Twingate's status page.

Failure mode: A schema or data migration caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2021-08-13 07:45 UTC

   Connectors older than v1.26.0 require a restart due to a database update. You can find Connector version information in the Connector detail page in the Twingate Admin console. We are currently in the process of contacting Twingate admins.

2. resolved 2021-08-13 08:16 UTC

   All admins with affected Connectors were notified.

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Connector Heartbeat

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2021-08-10 20:00 UTC

   The Controller infrastucture was experiencing degraded availability. The issue began at 19:39 UTC and continued until 19:47 UTC. Our team is currently investigating the root cause of the issue, and we will post additional updates here.

2. monitoring 2021-08-10 20:11 UTC

   The Controller is currently fully available, and we are actively investigating the root cause of the issue.

3. resolved 2021-08-10 21:24 UTC

   This incident has been resolved. We will be posting a post mortem description shortly.

4. postmortem 2021-08-12 23:37 UTC

   **Components impacted** Controller **Summary** The Controller was partially unavailable to service requests from approximately 19:39 to 19:46 UTC. The result was that during this period of time access to protected resources was limited, some existing connections were dropped,...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Connector Heartbeat

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2021-07-29 15:15 UTC

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

2. monitoring 2021-07-29 15:17 UTC

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

3. monitoring 2021-07-29 16:00 UTC

   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 2021-07-29 17:00 UTC

   This incident has been resolved.

5. postmortem 2021-07-30 00:57 UTC

   **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...

Excerpts are shortened. Read the full incident on Twingate's status page.

Affected: Americas Relays

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. identified 2021-07-13 16:58 UTC

   We have identified an issue with our Relay cluster in Mumbai (GCP region asia-south1-a) and are working to fix it.

2. monitoring 2021-07-13 18:31 UTC

   Engineering has a fix in place. We are currently monitoring the cluster and expect it to be back up by 21:00 PST.

3. resolved 2021-07-14 03:58 UTC

   Relay cluster in Mumbai (GCP region asia-south1-a) is now fully operational.

4. postmortem 2021-07-29 18:33 UTC

   **Components impacted** Relay **Summary** We encountered an issue during an upgrade to our relay cluster monitoring infrastructure. As a result, we were unable to bring the Mumbai regional cluster up during this maintenance window, and so it was left down. There was no customer...

Excerpts are shortened. Read the full incident on Twingate's status page.