Skip to main content
Twingate

Connector restart may be required

Degraded Lasted 31m · started · Twingate's page

Level
confirmed
Worst impact
Degraded
Down Index
16of 100

What to do

  • Check whether your product depends on Twingate. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 31m it lasted.

    Anything that failed between 2021-08-13 07:45 UTC and 2021-08-13 08:16 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 2

  1. monitoring

    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.

    provider

  2. resolved

    All admins with affected Connectors were notified.

    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-07de55377c

Is Twingate still down?

No, this incident was resolved 2021-08-13 08:16 UTC. For Twingate's live state, see https://down.guide/twingate.

How long did it last?

31m, from 2021-08-13 07:45 UTC to 2021-08-13 08:16 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.