User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
encrypt.me · 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 2 hr ago. Last stored result reached it in 347 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 464 ms | 0 |
| Tue 02 | 0 | 0.0 | 345 ms | 0 |
| Tue 04 | 0 | 0.0 | 297 ms | 0 |
| Tue 06 | 0 | 0.0 | 222 ms | 0 |
| Tue 08 | 0 | 0.0 | 463 ms | 0 |
| Tue 10 | 0 | 0.0 | 317 ms | 0 |
| Tue 12 | 0 | 0.0 | 321 ms | 0 |
| Tue 15 | 0 | 0.0 | 553 ms | 0 |
| Tue 17 | 0 | 0.0 | 305 ms | 0 |
| Tue 19 | 0 | 0.0 | 333 ms | 0 |
| Tue 21 | 0 | 0.0 | 308 ms | 0 |
| Wed 00 | 0 | 0.0 | 328 ms | 0 |
| Wed 02 | 0 | 0.0 | 317 ms | 0 |
| Wed 04 | 0 | 0.0 | 323 ms | 0 |
| Wed 06 | 0 | 0.0 | 335 ms | 0 |
| Wed 08 | 0 | 0.0 | 243 ms | 0 |
| Wed 11 | 0 | 0.0 | 241 ms | 0 |
| Wed 13 | 0 | 0.0 | 180 ms | 0 |
| Wed 15 | 0 | 0.0 | 289 ms | 0 |
| Wed 17 | 0 | 0.0 | 251 ms | 0 |
| Wed 19 | 0 | 0.0 | 805 ms | 0 |
| Wed 21 | 0 | 0.0 | 291 ms | 0 |
| Thu 00 | 0 | 0.0 | 901 ms | 0 |
| Thu 02 | 0 | 0.0 | 1164 ms | 0 |
| Thu 04 | 0 | 0.0 | 264 ms | 0 |
| Thu 06 | 0 | 0.0 | 188 ms | 0 |
| Thu 08 | 0 | 0.0 | 262 ms | 0 |
| Thu 10 | 0 | 0.0 | 310 ms | 0 |
| Thu 12 | 0 | 0.0 | 251 ms | 0 |
| Thu 14 | 0 | 0.0 | 245 ms | 0 |
| Thu 16 | 0 | 0.0 | 248 ms | 0 |
| Thu 17 | 0 | 0.0 | 295 ms | 0 |
| Thu 19 | 0 | 0.0 | 249 ms | 0 |
| Thu 21 | 0 | 0.0 | 486 ms | 0 |
| Thu 23 | 0 | 0.0 | 820 ms | 0 |
| Fri 01 | 0 | 0.0 | 342 ms | 0 |
| Fri 03 | 0 | 0.0 | 438 ms | 0 |
| Fri 05 | 0 | 0.0 | 1036 ms | 0 |
| Fri 07 | 0 | 0.0 | 277 ms | 0 |
| Fri 09 | 0 | 0.0 | 313 ms | 0 |
| Fri 10 | 0 | 0.0 | 659 ms | 0 |
| Fri 11 | 0 | 0.0 | 264 ms | 0 |
| Fri 13 | 0 | 0.0 | 190 ms | 0 |
| Fri 15 | 0 | 0.0 | 269 ms | 0 |
| Fri 17 | 0 | 0.0 | 331 ms | 0 |
| Fri 19 | 0 | 0.0 | 264 ms | 0 |
| Fri 20 | 0 | 0.0 | 189 ms | 0 |
| Fri 21 | 0 | 0.0 | 347 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Encrypt.me 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 Encrypt.me goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Encrypt.me alerts to Slack, Discord or a webhook — free.
We track Encrypt.me (encrypt.me) as part of the Cloud & developer group. Encrypt everything and stay safe online with the most trusted and secure VPN on the market.
Encrypt.me publishes an official status page at status.encrypt.me; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 403 ms average, 189–1036 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 Encrypt.me incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
403 ms on average over the last 24 hours (189–1036 ms).
Yes, at https://status.encrypt.me.
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 Encrypt.me here at once, the problem is on Encrypt.me'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 Encrypt.me. 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.