- Level
- confirmed
- Worst impact
- Operational
What to do
Check whether your product depends on Twingate. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2022-08-09 17:44 UTC and 2022-08-09 05:00 UTC may need a replay.Subscribe to Twingate's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=twingate works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Twingate 1
- resolved
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 this period. Ingress changes are rare and no additional changes are planned. Looking ahead, we will schedule a brief downtime if future ingress updates are necessary.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-8dcd9e258d
Is Twingate still down?
No, this incident was resolved 2022-08-09 05:00 UTC. For Twingate's live state, see https://down.guide/providers/twingate.
How long did it last?
0m, from 2022-08-09 17:44 UTC to 2022-08-09 05:00 UTC, by the times Twingate posted.
What caused it?
Twingate hasn't published a root cause. If it does, it shows here.
Where does this come from?
Twingate's official status page, https://status.twingate.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.