Is Twingate Down?

No — Twingate is up

Twingate's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 299 ms

Right now

The verdict is the worse of these two. How we decide

Twingate's status page

status.twingate.com · read 3 minutes ago · checked every 3 minutes

Operational

Twingate's components, as its status page reports them
Component	Status
www.twingate.com	Operational
Docs	Operational
Downloads	Operational
Americas Relays	Operational
EMEA Relays	Operational
APAC Relays	Operational
Peer-to-Peer	Operational
DNS Filtering	Operational
Events Processing	Operational
Reports Downloads	Operational
Realtime Exports	Operational
Authentication - Enterprise	Operational

12 more, all operational · show all 24

All of Twingate's components
Component	Status
Homepage
www.twingate.com	Operational
Docs	Operational
Downloads	Operational
Data Plane
Americas Relays	Operational
EMEA Relays	Operational
APAC Relays	Operational
Peer-to-Peer	Operational
DNS Filtering	Operational
Analytics
Events Processing	Operational
Reports Downloads	Operational
Realtime Exports	Operational
Control Plane
Authentication - Enterprise	Operational
Authentication - Social	Operational
MFA	Operational
Authorization	Operational
Connector Heartbeat	Operational
Management
Identity Providers Sync	Operational
Public API	Operational
Admin Console	Operational
Realtime Updates	Operational
Client Log Upload	Operational
3rd Party Integrations	Operational
Network Dashboards	Operational
DNS Filtering Dashboards	Operational

Open their status page

FlareWarden checks

twingate.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 299 ms
Checked: 2 hours ago

By region

Ashburn reachable, 230 ms
Dallas reachable, 403 ms
Frankfurt reachable, 116 ms
Johannesburg reachable, 733 ms
Newark reachable, 213 ms
Paris reachable, 143 ms
Stockholm reachable, 182 ms
São Paulo reachable, 373 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	164 ms	1 ms	6 ms	201 ms
Dallas	252 ms	2 ms	8 ms	381 ms
Frankfurt	53 ms	2 ms	7 ms	89 ms
Johannesburg	440 ms	2 ms	6 ms	549 ms
Newark	62 ms	8 ms	11 ms	152 ms
Paris	41 ms	2 ms	8 ms	110 ms
Stockholm	71 ms	5 ms	9 ms	136 ms
São Paulo	301 ms	3 ms	8 ms	341 ms

We check that twingate.com loads, not every feature behind it. Test it yourself

History

Incidents Twingate reported

Since Oct 25, 12 days · from status.twingate.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Twingate website availability

Measured by FlareWarden · twingate.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 292ms

Last 30 days

12-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of twingate.com from multiple regions every 6 hours. Twingate's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 12 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Twingate does

Twingate is a zero trust network access service that companies use in place of a traditional VPN to reach private networks. Admins install Connectors inside each Remote Network, users run the Twingate Client, and a Twingate-hosted Controller checks identity through a third-party identity provider before signing each user's access list. Traffic goes peer to peer between Client and Connector when it can, and through Twingate Relays when it cannot.

What an outage looks like

Users cannot sign in through their identity provider, Resources fail with intermittent authorization failures, or the Admin Console and network dashboards will not load. Twingate's status page splits the Control Plane (authentication, MFA, authorization, Connector heartbeat) from the Data Plane (Relays by region, peer to peer). On May 28, 2026 authorization trouble hit about 15% of active connections at peak; on May 8, 2026 only port 443 Relays failed.

What to do about it

Check status.twingate.com and see which plane is affected: Control Plane rows cover sign-in and authorization, Data Plane rows cover Relays in the Americas, EMEA and APAC. If the page is clear, confirm Clients and Connectors can reach *.twingate.com on TCP 443 and Relays on TCP 30000-31000. Run two Connectors per Remote Network; when one fails, Clients move to the next. Business and Enterprise accounts can open a support request.

Is it down for everyone, or just you?

If this page says Twingate is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Twingate outage FAQ

What happens to connected users when Twingate's Controller is degraded?

Twingate's docs do not say whether established connections survive a Controller outage. The Controller carries no traffic, but it signs each user's access list and connection token, and Control Plane incidents have reached users: on May 28, 2026 authorization degradation affected about 15% of active connections at peak, with intermittent failures from 10:00 to 12:30 UTC. A May 28, 2025 routing error took authentication and authorization down for 29 minutes.

Does a Twingate Relay outage affect every user?

No. Twingate's docs say it always tries a peer-to-peer connection between Client and Connector first and uses Relays as a backup, so only relayed connections depend on them. On May 8, 2026 Twingate's port 443 Relays, used by a subset of customers, failed for about two hours after a configuration change, and Twingate said most customers should not see an issue.

Does an Okta or other identity provider outage affect Twingate?

It can. Twingate's docs say the Controller always delegates user authentication to a third-party identity provider, so a user who needs to sign in depends on that provider answering. Twingate tracks Authentication - Enterprise, Authentication - Social and Identity Providers Sync as separate status rows; on August 14, 2024 GitHub social login failed for about 50 minutes.

How do I get Twingate support during an outage?

It depends on your plan. Twingate's docs say break-fix technical support is offered to Business and Enterprise accounts, which open a support request through the Help Center. Starter and Teams accounts do not get product support or troubleshooting and are pointed to the docs, Help Center and the r/twingate subreddit; self-serve trial customers can email onboarding@twingate.com.

What does the check on this page measure?

It loads www.twingate.com, Twingate's public website, which its status page tracks as the www.twingate.com and Homepage rows. It does not sign in, reach the Controller, test a Relay or open a Resource through a Connector. A green result here means the website answers, not that authentication, authorization or relayed connections work.

How we measure this

We request Twingate's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Twingate publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Twingate itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Twingate goes down

We check Twingate every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required