User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Degraded Service: Support Email
Source: the vendor's status page · We are not affiliated with Enpass.
Estimated fix: Not enough Enpass history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–12 h; 78 outages).
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 31 min ago. Last stored result reached it in 2185 ms.
Minor incident
Degraded Service: Support Email Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 09:30 | 0 | 0.0 | 1910 ms | 0 |
| 11:30 | 0 | 0.0 | 2005 ms | 0 |
| 13:30 | 0 | 0.0 | 1982 ms | 0 |
| 15:45 | 0 | 0.0 | 1876 ms | 0 |
| 17:45 | 0 | 0.0 | 2868 ms | 0 |
| 19:45 | 0 | 0.0 | 1992 ms | 0 |
| 21:45 | 0 | 0.0 | 2070 ms | 0 |
| 23:45 | 0 | 0.0 | 1954 ms | 0 |
| 00:00 | 0 | 0.0 | 1824 ms | 0 |
| 02:00 | 0 | 0.0 | 1929 ms | 0 |
| 04:00 | 0 | 0.0 | 1928 ms | 0 |
| 04:45 | 0 | 0.0 | 1966 ms | 0 |
| 07:00 | 0 | 0.0 | 2185 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Enpass 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 Enpass goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Enpass alerts to Slack, Discord or a webhook — free.
We track Enpass (enpass.io) as part of the Cloud & developer group. Enpass keeps your passwords and passkeys in your own trusted environment, never ours. See why data sovereignty changes everything for your security.
Enpass publishes an official status page at status.enpass.io; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 2031 ms average, 1824–2868 ms range across 14 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Degraded Service: Support Email
We have not recorded a public Enpass incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
2031 ms on average over the last 24 hours (1824–2868 ms).
Yes, at https://status.enpass.io.
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 Enpass here at once, the problem is on Enpass'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 Enpass. 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.