Skip to main content

Is OpenVPN Down?

No — OpenVPN is up

Reachable from all 8 checked regions

Average response time: 61ms

Last checked · checks run every 6 hours

Official status page: https://status.openvpn.com/

OpenVPN uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
53ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 17 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

17-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: 100.00% uptime, 16 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 40 checks
Aug 13: 100.00% uptime, 37 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 32 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 32 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 24 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

bom
36ms
DNS 0ms TCP 2ms TLS 8ms TTFB 27ms
cdg
88ms
DNS 0ms TCP 2ms TLS 11ms TTFB 78ms
dfw
50ms
DNS 0ms TCP 1ms TLS 7ms TTFB 41ms
ewr
58ms
DNS 0ms TCP 3ms TLS 9ms TTFB 48ms
fra
53ms
DNS 0ms TCP 1ms TLS 9ms TTFB 48ms
gru
44ms
DNS 0ms TCP 3ms TLS 9ms TTFB 33ms
iad
52ms
DNS 0ms TCP 1ms TLS 7ms TTFB 44ms
jnb
32ms
DNS 0ms TCP 0ms TLS 5ms TTFB 27ms
lax
118ms
DNS 1ms TCP 1ms TLS 10ms TTFB 113ms

What OpenVPN does

OpenVPN is both an open source VPN protocol and a set of commercial products from OpenVPN Inc. CloudConnexa is the hosted service, where the company runs VPN infrastructure across regional points of presence, while Access Server and the community edition are installed and operated on the customer's own servers. Businesses use it mainly for remote access to internal networks.

What an outage looks like

VPN clients fail to connect or reconnect in a loop against one region while other regions work, since CloudConnexa is deployed city by city. Sessions drop and internal applications reached over the tunnel become unreachable, which usually looks like the application being down rather than the VPN. The administration console may be unavailable while established tunnels keep passing traffic normally.

What to do about it

Check status.openvpn.com, which lists CloudConnexa as individual regional components including Ashburn, Frankfurt, Amsterdam and around twenty more, so an incident in one city is visible rather than global. Identify which region your network connects through before assuming a full outage, since connecting via a different region is often the fastest workaround. A self-hosted Access Server is not covered by that page, because you operate it.

Is it down for everyone, or just you?

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

Test it yourself

Related services

OpenVPN outage FAQ

Is OpenVPN down, or is it my own server?
It depends which OpenVPN you run. The page at status.openvpn.com covers CloudConnexa, the hosted service OpenVPN Inc. operates, and reports it region by region. If you installed Access Server or the community edition on your own infrastructure, no vendor page can tell you whether it is up, because nobody but you is running it. Check your own host and its logs first in that case.
Why does the VPN fail for some staff and not others?
CloudConnexa is deployed as separate regional points of presence and each one is its own component on the status page, so an incident in a single city affects only the people routed through it. Staff connecting through another region carry on normally on the same account. Compare which region the affected and unaffected users are using before treating it as an account-wide problem.
Do existing VPN connections drop during an incident?
Not always. The status page separates regional connectivity from the wider service, so the administration console can be degraded while established tunnels keep passing traffic. What usually fails first is making a new connection or reconnecting after a drop. If your session is still working, avoid disconnecting until the affected component shows operational again.
Does an OpenVPN outage mean our internal applications are down?
No, though it looks that way from a laptop. Applications reachable only through the tunnel become unreachable when the VPN fails, while the servers themselves keep running and anyone on the office network can still use them normally. Test from inside the network, or from a region that is unaffected, before escalating to whoever owns the application.

How we measure this

  • We request OpenVPN's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • 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. We only change the 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 OpenVPN publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when OpenVPN goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required