Twingate status history

Current state: operational — “All Systems Operational” per https://status.twingate.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

0incidents, last 30 days

1incidents, last 90 days

4incidents on record

Incidents per week, last 12 weeks:

Get Twingate alerts in your Slack — free template RSS for Twingate

How long do Twingate incidents last?

4.6 hmedian incident duration4 measured

8.0 h90th percentile1 in 10 ran longer

5.1 hmedian, major/critical only2 incidents

From 4 incidents with a vendor-posted start and resolve time. Longest on record: Twingate Service Incident — 8.0 h (2026-05-28 09:24 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (4)

Started	Incident	Status	Impact	Duration
2026-07-08 22:04 UTC	Linux Package Downloads Down	resolved	minor	2 h 20 min
2026-05-28 09:24 UTC	Twingate Service Incident	postmortem	critical	8 h 02 min
2026-05-08 08:44 UTC	Relays443 Down	postmortem	major	2 h 10 min
2025-10-20 15:49 UTC	AWS Outage Impacting APT/RPM Package Repository (packages.twingate.com)	resolved	none	6 h 55 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Twingate with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "twingate"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}