User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
easyjur.com · Cloud & developer
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
Source: the vendor's status page · We are not affiliated with Easyjur.
Estimated fix: Not enough Easyjur history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–9.5 h; 82 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 44 min ago. Last stored result reached it in 465 ms.
Minor incident
Some components degraded (no active incident posted) Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 650 ms | 0 |
| Tue 01 | 0 | 0.0 | 643 ms | 0 |
| Tue 03 | 0 | 0.0 | 618 ms | 0 |
| Tue 05 | 0 | 0.0 | 818 ms | 0 |
| Tue 07 | 0 | 0.0 | 582 ms | 0 |
| Tue 09 | 0 | 0.0 | 810 ms | 0 |
| Tue 11 | 0 | 0.0 | 619 ms | 0 |
| Tue 14 | 0 | 0.0 | 597 ms | 0 |
| Tue 16 | 0 | 0.0 | 650 ms | 0 |
| Tue 18 | 0 | 0.0 | 767 ms | 0 |
| Tue 20 | 0 | 0.0 | 645 ms | 0 |
| Tue 23 | 0 | 0.0 | 657 ms | 0 |
| Wed 01 | 0 | 0.0 | 577 ms | 0 |
| Wed 03 | 0 | 0.0 | 617 ms | 0 |
| Wed 05 | 0 | 0.0 | 606 ms | 0 |
| Wed 07 | 0 | 0.0 | 629 ms | 0 |
| Wed 10 | 0 | 0.0 | 640 ms | 0 |
| Wed 12 | 0 | 0.0 | 623 ms | 0 |
| Wed 14 | 0 | 0.0 | 487 ms | 0 |
| Wed 16 | 0 | 0.0 | 598 ms | 0 |
| Wed 18 | 0 | 0.0 | 523 ms | 0 |
| Wed 20 | 0 | 0.0 | 576 ms | 0 |
| Wed 23 | 0 | 0.0 | 635 ms | 0 |
| Thu 01 | 0 | 0.0 | 660 ms | 0 |
| Thu 03 | 0 | 0.0 | 569 ms | 0 |
| Thu 05 | 0 | 0.0 | 614 ms | 0 |
| Thu 07 | 0 | 0.0 | 507 ms | 0 |
| Thu 09 | 0 | 0.0 | 614 ms | 0 |
| Thu 11 | 0 | 0.0 | 586 ms | 0 |
| Thu 13 | 0 | 0.0 | 2208 ms | 0 |
| Thu 15 | 0 | 0.0 | 638 ms | 0 |
| Thu 17 | 0 | 0.0 | 489 ms | 0 |
| Thu 19 | 0 | 0.0 | 611 ms | 0 |
| Thu 21 | 0 | 0.0 | 659 ms | 0 |
| Thu 23 | 0 | 0.0 | 476 ms | 0 |
| Fri 01 | 0 | 0.0 | 589 ms | 0 |
| Fri 03 | 0 | 0.0 | 713 ms | 0 |
| Fri 05 | 0 | 0.0 | 599 ms | 0 |
| Fri 07 | 0 | 0.0 | 470 ms | 0 |
| Fri 09 | 0 | 0.0 | 582 ms | 0 |
| Fri 10 | 0 | 0.0 | 590 ms | 0 |
| Fri 12 | 0 | 0.0 | 620 ms | 0 |
| Fri 14 | 0 | 0.0 | 635 ms | 0 |
| Fri 16 | 0 | 0.0 | 622 ms | 0 |
| Fri 17 | 0 | 0.0 | 2510 ms | 0 |
| Fri 19 | 0 | 0.0 | 697 ms | 0 |
| Fri 21 | 0 | 0.0 | 495 ms | 0 |
| Fri 22 | 0 | 0.0 | 465 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 Easyjur 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 Easyjur goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Easyjur alerts to Slack, Discord or a webhook — free.
We track Easyjur (easyjur.com) as part of the Cloud & developer group. O novo sistema operacional jurídico executa o trabalho pelo advogado: Workflows integrados com agentes de IA, contexto privado e operação humana, em uma só plataforma completa.
Easyjur publishes an official status page at status.easyjur.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 717 ms average, 465–2510 ms range across 15 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
We have not recorded a public Easyjur incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
717 ms on average over the last 24 hours (465–2510 ms).
Yes, at https://status.easyjur.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 Easyjur here at once, the problem is on Easyjur'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 Easyjur. 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.