User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
pritunl.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 36 min ago. Last stored result reached it in 1584 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 10 | 0 | 0.0 | 325 ms | 0 |
| Tue 12 | 0 | 0.0 | 1847 ms | 0 |
| Tue 14 | 0 | 0.0 | 1438 ms | 0 |
| Tue 16 | 0 | 0.0 | 1355 ms | 0 |
| Tue 19 | 0 | 0.0 | 3794 ms | 0 |
| Tue 21 | 0 | 0.0 | 1327 ms | 0 |
| Tue 23 | 0 | 0.0 | 1552 ms | 0 |
| Wed 01 | 0 | 0.0 | 1947 ms | 0 |
| Wed 04 | 0 | 0.0 | 1480 ms | 0 |
| Wed 06 | 0 | 0.0 | 1378 ms | 0 |
| Wed 08 | 0 | 0.0 | 2248 ms | 0 |
| Wed 10 | 0 | 0.0 | 2452 ms | 0 |
| Wed 13 | 0 | 0.0 | 1432 ms | 0 |
| Wed 15 | 0 | 0.0 | 1892 ms | 0 |
| Wed 17 | 0 | 0.0 | 2129 ms | 0 |
| Wed 18 | 0 | 0.0 | 1199 ms | 0 |
| Wed 21 | 0 | 0.0 | 1426 ms | 0 |
| Wed 23 | 0 | 0.0 | 382 ms | 0 |
| Thu 01 | 0 | 0.0 | 1887 ms | 0 |
| Thu 03 | 0 | 0.0 | 2172 ms | 0 |
| Thu 05 | 0 | 0.0 | 1463 ms | 0 |
| Thu 07 | 0 | 0.0 | 1079 ms | 0 |
| Thu 09 | 0 | 0.0 | 1384 ms | 0 |
| Thu 11 | 0 | 0.0 | 1261 ms | 0 |
| Thu 13 | 0 | 0.0 | 2616 ms | 0 |
| Thu 15 | 0 | 0.0 | 3477 ms | 0 |
| Thu 17 | 0 | 0.0 | 3267 ms | 0 |
| Thu 20 | 0 | 0.0 | 1581 ms | 0 |
| Thu 22 | 0 | 0.0 | 1523 ms | 0 |
| Fri 00 | 0 | 0.0 | 1326 ms | 0 |
| Fri 02 | 0 | 0.0 | 643 ms | 0 |
| Fri 04 | 0 | 0.0 | 2709 ms | 0 |
| Fri 06 | 0 | 0.0 | 1603 ms | 0 |
| Fri 08 | 0 | 0.0 | 1715 ms | 0 |
| Fri 10 | 0 | 0.0 | 1307 ms | 0 |
| Fri 12 | 0 | 0.0 | 1198 ms | 0 |
| Fri 14 | 0 | 0.0 | 2347 ms | 0 |
| Fri 15 | 0 | 0.0 | 1383 ms | 0 |
| Fri 17 | 0 | 0.0 | 3437 ms | 0 |
| Fri 18 | 0 | 0.0 | 2060 ms | 0 |
| Fri 19 | 0 | 0.0 | 3520 ms | 0 |
| Fri 21 | 0 | 0.0 | 1234 ms | 0 |
| Fri 23 | 0 | 0.0 | 1418 ms | 0 |
| Sat 01 | 0 | 0.0 | 1653 ms | 0 |
| Sat 02 | 0 | 0.0 | 1475 ms | 0 |
| Sat 03 | 0 | 0.0 | 1443 ms | 0 |
| Sat 05 | 0 | 0.0 | 1279 ms | 0 |
| Sat 07 | 0 | 0.0 | 1584 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Pritunl yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Pritunl goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Pritunl alerts to Slack, Discord or a webhook — free.
We track Pritunl (pritunl.com) as part of the Cloud & developer group. Free open source enterprise distributed VPN server. Virtualize your private networks across datacenters and provide simple remote access in minutes.
Pritunl publishes an official status page at status.pritunl.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 1751 ms average, 461–3520 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Pritunl incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
1751 ms on average over the last 24 hours (461–3520 ms).
Yes, at https://status.pritunl.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Pritunl here at once, the problem is on Pritunl's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Pritunl. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.