- Level
- confirmed
- Worst impact
- Degraded
- Components
- Events Processing
- Down Index
- 17of 100
What to do
Check whether you use Twingate Events Processing. 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 33m it lasted.
Anything that failed between 2024-09-20 04:57 UTC and 2024-09-20 05:31 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 4
- investigating
We've detected an issue with DNS events ingestion affecting some of our customers who are not able to see DNS events when exporting to S3. We're currently looking for root cause.
provider
- identified
We've identified the issue and are working on a fix.
provider
- monitoring
DNS events are being ingested again and we're monitoring the system.
provider
- 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-4e7b0826fc
Is Twingate still down?
No, this incident was resolved 2024-09-20 05:31 UTC. For Twingate's live state, see https://down.guide/twingate.
How long did it last?
33m, from 2024-09-20 04:57 UTC to 2024-09-20 05:31 UTC, by the times Twingate posted.
What was affected?
Twingate named Events Processing.
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.