Skip to main content
Twingate

Temporary Disruption in DNS Activity Reports

Partial outage Lasted 17h 39m · started · Twingate's page

Level
confirmed
Worst impact
Partial outage
Components
DNS Filtering Dashboards
Down Index
34of 100

What to do

  • Check whether you use Twingate DNS Filtering Dashboards. 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 17h 39m it lasted.

    Anything that failed between 2025-02-24 08:00 UTC and 2025-02-25 01:39 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 experiencing a temporary disruption with the DNS Activity Reports. The team is working on restoring access, and we'll have them back up shortly.

    provider

  2. monitoring

    Recent DNS Activity is now restored and we are monitoring the system.

    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-d74b7ab859

Is Twingate still down?

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

How long did it last?

17h 39m, from 2025-02-24 08:00 UTC to 2025-02-25 01:39 UTC, by the times Twingate posted.

What was affected?

Twingate named DNS Filtering Dashboards.

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.