Skip to main content
Twingate

Empty DNS filtering logs

Degraded Lasted 6h 53m · started · Twingate's page

Level
confirmed
Worst impact
Degraded
Components
Admin Console
Down Index
23of 100

What to do

  • Check whether you use Twingate Admin Console. 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 6h 53m it lasted.

    Anything that failed between 2024-01-31 20:29 UTC and 2024-02-01 03:22 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 3

  1. investigating

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

    provider

  2. identified

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

    provider

  3. resolved

    This incident has been resolved.

    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-33c6266055

Is Twingate still down?

No, this incident was resolved 2024-02-01 03:22 UTC. For Twingate's live state, see https://down.guide/twingate.

How long did it last?

6h 53m, from 2024-01-31 20:29 UTC to 2024-02-01 03:22 UTC, by the times Twingate posted.

What was affected?

Twingate named Admin Console.

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.