User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / 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 28 min ago. Last stored result reached it in 1862 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 1888 ms | 0 |
| Mon 23 | 0 | 0.0 | 1763 ms | 0 |
| Tue 01 | 0 | 0.0 | 1997 ms | 0 |
| Tue 03 | 0 | 0.0 | 2142 ms | 0 |
| Tue 05 | 0 | 0.0 | 2506 ms | 0 |
| Tue 07 | 0 | 0.0 | 2668 ms | 0 |
| Tue 09 | 0 | 0.0 | 2360 ms | 0 |
| Tue 11 | 0 | 0.0 | 1835 ms | 0 |
| Tue 14 | 0 | 0.0 | 2542 ms | 0 |
| Tue 16 | 0 | 0.0 | 1928 ms | 0 |
| Tue 18 | 0 | 0.0 | 1875 ms | 0 |
| Tue 20 | 0 | 0.0 | 2121 ms | 0 |
| Tue 23 | 0 | 0.0 | 1903 ms | 0 |
| Wed 01 | 0 | 0.0 | 1842 ms | 0 |
| Wed 03 | 0 | 0.0 | 1941 ms | 0 |
| Wed 05 | 0 | 0.0 | 2093 ms | 0 |
| Wed 07 | 0 | 0.0 | 1927 ms | 0 |
| Wed 10 | 0 | 0.0 | 2852 ms | 0 |
| Wed 12 | 0 | 0.0 | 2596 ms | 0 |
| Wed 14 | 0 | 0.0 | 1989 ms | 0 |
| Wed 16 | 0 | 0.0 | 2064 ms | 0 |
| Wed 18 | 0 | 0.0 | 2068 ms | 0 |
| Wed 20 | 0 | 0.0 | 2025 ms | 0 |
| Wed 23 | 0 | 0.0 | — | 0 |
| Thu 01 | 0 | 0.0 | 1937 ms | 0 |
| Thu 03 | 0 | 0.0 | 2024 ms | 0 |
| Thu 05 | 0 | 0.0 | 2144 ms | 0 |
| Thu 07 | 0 | 0.0 | 1944 ms | 0 |
| Thu 09 | 0 | 0.0 | 1910 ms | 0 |
| Thu 11 | 0 | 0.0 | 2005 ms | 0 |
| Thu 13 | 0 | 0.0 | 1982 ms | 0 |
| Thu 15 | 0 | 0.0 | 1876 ms | 0 |
| Thu 17 | 0 | 0.0 | 2868 ms | 0 |
| Thu 19 | 0 | 0.0 | 1992 ms | 0 |
| Thu 21 | 0 | 0.0 | 2070 ms | 0 |
| Thu 23 | 0 | 0.0 | 1954 ms | 0 |
| Fri 00 | 0 | 0.0 | 1824 ms | 0 |
| Fri 02 | 0 | 0.0 | 1929 ms | 0 |
| Fri 04 | 0 | 0.0 | 1947 ms | 0 |
| Fri 07 | 0 | 0.0 | 2185 ms | 0 |
| Fri 09 | 0 | 0.0 | 2048 ms | 0 |
| Fri 11 | 0 | 0.0 | 2003 ms | 0 |
| Fri 13 | 0 | 0.0 | 1928 ms | 0 |
| Fri 15 | 0 | 0.0 | 1856 ms | 0 |
| Fri 17 | 0 | 0.0 | 1890 ms | 0 |
| Fri 18 | 0 | 0.0 | 2199 ms | 0 |
| Fri 19 | 0 | 0.0 | 1728 ms | 0 |
| Fri 21 | 0 | 0.0 | 1862 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: 1958 ms average, 1728–2199 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Enpass incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
1958 ms on average over the last 24 hours (1728–2199 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.