User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Juro down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → juro.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 37 min ago. Last stored result reached it in 72 ms.
Official status
All clear
All systems operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 68 ms | 0 |
| Mon 22 | 0 | 0.0 | 91 ms | 0 |
| Tue 00 | 0 | 0.0 | 66 ms | 0 |
| Tue 02 | 0 | 0.0 | 179 ms | 0 |
| Tue 04 | 0 | 0.0 | 87 ms | 0 |
| Tue 06 | 0 | 0.0 | 76 ms | 0 |
| Tue 08 | 0 | 0.0 | 107 ms | 0 |
| Tue 11 | 0 | 0.0 | 73 ms | 0 |
| Tue 13 | 0 | 0.0 | 55 ms | 0 |
| Tue 15 | 0 | 0.0 | 126 ms | 0 |
| Tue 17 | 0 | 0.0 | 43 ms | 0 |
| Tue 19 | 0 | 0.0 | 29 ms | 0 |
| Tue 22 | 0 | 0.0 | 94 ms | 0 |
| Wed 00 | 0 | 0.0 | 108 ms | 0 |
| Wed 02 | 0 | 0.0 | 36 ms | 0 |
| Wed 04 | 0 | 0.0 | 45 ms | 0 |
| Wed 07 | 0 | 0.0 | 61 ms | 0 |
| Wed 09 | 0 | 0.0 | 57 ms | 0 |
| Wed 11 | 0 | 0.0 | 93 ms | 0 |
| Wed 13 | 0 | 0.0 | 43 ms | 0 |
| Wed 15 | 0 | 0.0 | 72 ms | 0 |
| Wed 17 | 0 | 0.0 | 54 ms | 0 |
| Wed 20 | 0 | 0.0 | 74 ms | 0 |
| Wed 22 | 0 | 0.0 | 70 ms | 0 |
| Thu 00 | 0 | 0.0 | 51 ms | 0 |
| Thu 02 | 0 | 0.0 | 75 ms | 0 |
| Thu 04 | 0 | 0.0 | 150 ms | 0 |
| Thu 06 | 0 | 0.0 | 88 ms | 0 |
| Thu 08 | 0 | 0.0 | 79 ms | 0 |
| Thu 10 | 0 | 0.0 | 36 ms | 0 |
| Thu 12 | 0 | 0.0 | 60 ms | 0 |
| Thu 15 | 0 | 0.0 | 51 ms | 0 |
| Thu 17 | 0 | 0.0 | 66 ms | 0 |
| Thu 19 | 0 | 0.0 | 74 ms | 0 |
| Thu 21 | 0 | 0.0 | 89 ms | 0 |
| Thu 23 | 0 | 0.0 | 41 ms | 0 |
| Fri 01 | 0 | 0.0 | 84 ms | 0 |
| Fri 03 | 0 | 0.0 | 39 ms | 0 |
| Fri 05 | 0 | 0.0 | 45 ms | 0 |
| Fri 07 | 0 | 0.0 | 31 ms | 0 |
| Fri 09 | 0 | 0.0 | 72 ms | 0 |
| Fri 10 | 0 | 0.0 | 34 ms | 0 |
| Fri 12 | 0 | 0.0 | 71 ms | 0 |
| Fri 14 | 0 | 0.0 | 52 ms | 0 |
| Fri 16 | 0 | 0.0 | 102 ms | 0 |
| Fri 18 | 0 | 0.0 | 106 ms | 0 |
| Fri 19 | 0 | 0.0 | 86 ms | 0 |
| Fri 21 | 0 | 0.0 | 72 ms | 0 |
Reliability
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.
Embed this status: free live Juro badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Juro yet. Outages of 10 minutes or more get their own page here.
Having trouble with Juro?
One report per service every 10 minutes from this network. No account.
Follow Juro
Get an email when Juro goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Juro alerts to Slack, Discord or a webhook — free.
About Juro
We track Juro (juro.com) as part of the AI group. Intelligent contracting is here. Juro empowers your team to agree and manage contracts end-to-end with flexible AI automation that lives where you live.
Juro publishes an official status page at status.juro.com; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 63 ms average, 20–106 ms range across 14 successful checks.
Questions
Is Juro down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Juro last down?
We have not recorded a public Juro incident since monitoring began 8 days ago.
What is Juro's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Juro respond?
63 ms on average over the last 24 hours (20–106 ms).
Does Juro have an official status page?
Yes, at https://status.juro.com.
Juro not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Juro here at once, the problem is on Juro'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 Juro. 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.