Twingate Outage History

12 incidents recorded over the last 365 days, 3 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded Twingate Incident

Twingate incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 14, 2026Routine database maintenance scheduledWe anticipate approximately 2-5 minutes of impact time while routine maintenance (version upgrade) takes place on our database backend. During this short window, no existing network connections will be interrupted. New…1h 30mScheduled
Aug 29, 2026Migration to Regional Service ShardThe scheduled maintenance has been completed.1h 30mScheduled
Jul 11, 2026Twingate Network MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Jul 8, 2026Linux Package Downloads DownThis incident has been resolved.2h 20mResolved
Jun 20, 2026Database Capacity Increase maintenance scheduledThis maintenance is completed. All Twingate services are operational.1h 0mScheduled
May 28, 2026Twingate Service Incident# 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…8h 1mResolved
May 8, 2026Relays443 Down**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…2h 10mResolved
Apr 9, 2026Support (Ticketing) service migration to a new providerThe scheduled maintenance has been completed.4h 0mScheduled
Mar 7, 2026Scheduled Maintenance on DownloadsThe scheduled maintenance has been completed.30 minScheduled
Mar 1, 2026Scheduled Maintenance on Reports DownloadsThe scheduled maintenance has been completed.3h 0mScheduled
Dec 21, 2025Database Upgrade maintenance scheduledThe scheduled maintenance has been completed.3h 0mScheduled
Nov 9, 2025Routine database maintenance scheduledThe scheduled maintenance has been completed.1h 30mScheduled

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Twingate incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Twingate Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Twingate acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Twingate outage in this window ran 8h 1m, against a mean recovery of 2h 28m. If you depend on Twingate in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.