Skip to main content
down.guideby Sazabi
Twingate
DWN-6b4258344fTwingateResolved

Database Connection Issues

Degraded Lasted 0m · started · Twingate's page

Level
confirmed
Worst impact
Degraded
Components
Public API, Admin Console, Connector Heartbeat
Down Index
10of 100

What to do

  • Check whether you use Twingate Public API, Admin Console, Connector Heartbeat. 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 0m it lasted.

    Anything that failed between 2024-06-26 22:01 UTC and 2024-06-26 22:01 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. resolved

    On June 26, 2024, between 8:16 pm UTC and 8:28 pm UTC, Twingate experienced several database connectivity alerts due to a failed rollout of one of its components. The rollout was promptly reversed, and our existing reliability measures prevented any major disruption to customer traffic.

    provider

  2. postmortem

    **Components impacted** Management: Public API Management: Admin Console ‌ **Summary** On June 26, 2024 between 20:16 and 20:24 UTC, Twingate’s SQL proxies restarted, causing a brief failure to a small percentage of calls made to our Public API \(Terraform, Pulumi, k8s Operator, etc.\) and to the Admin console. There was no impact to Clients or Connectors. A change to our SQL proxy deployments that was targeting staging and development environments was pushed to production due to a misconfiguration, causing our SQL proxy instances to restart. ‌ **Root cause** Due to a misconfiguration, a change to our SQL proxy deployments intended for staging and development environments was pushed to production, causing them to restart. ‌ **Corrective actions** Short Term: * Ensure that SQL proxy deployments are only pushed in a controlled manner by resuming the GitOps workflow manually. * Fix the misconfiguration in our GitOps deployment mechanism for our SQL proxy deployments and set the Helm chart version to a static value so that all upgrades are done in a controlled manner. * Enhance our SQL proxy Helm chart to reduce the impact to services during updates and upgrades.

    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-6b4258344f

Is Twingate still down?

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

How long did it last?

0m, from 2024-06-26 22:01 UTC to 2024-06-26 22:01 UTC, by the times Twingate posted.

What was affected?

Twingate named Public API, Admin Console, Connector Heartbeat.

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.

Sources

Feed