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 25 min ago. Last stored result reached it in 162 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 | 74 ms | 0 |
| Mon 23 | 0 | 0.0 | 1225 ms | 0 |
| Tue 01 | 0 | 0.0 | 209 ms | 0 |
| Tue 03 | 0 | 0.0 | 163 ms | 0 |
| Tue 05 | 0 | 0.0 | 110 ms | 0 |
| Tue 07 | 0 | 0.0 | 59 ms | 0 |
| Tue 09 | 0 | 0.0 | 219 ms | 0 |
| Tue 12 | 0 | 0.0 | 71 ms | 0 |
| Tue 14 | 0 | 0.0 | 1519 ms | 0 |
| Tue 16 | 0 | 0.0 | 81 ms | 0 |
| Tue 18 | 0 | 0.0 | 159 ms | 0 |
| Tue 21 | 0 | 0.0 | 197 ms | 0 |
| Tue 23 | 0 | 0.0 | 1142 ms | 0 |
| Wed 01 | 0 | 0.0 | 158 ms | 0 |
| Wed 03 | 0 | 0.0 | 1480 ms | 0 |
| Wed 06 | 0 | 0.0 | 74 ms | 0 |
| Wed 08 | 0 | 0.0 | 50 ms | 0 |
| Wed 10 | 0 | 0.0 | 985 ms | 0 |
| Wed 12 | 0 | 0.0 | 169 ms | 0 |
| Wed 14 | 0 | 0.0 | 129 ms | 0 |
| Wed 16 | 0 | 0.0 | 171 ms | 0 |
| Wed 19 | 0 | 0.0 | 46 ms | 0 |
| Wed 21 | 0 | 0.0 | 167 ms | 0 |
| Wed 23 | 0 | 0.0 | 167 ms | 0 |
| Thu 01 | 0 | 0.0 | 1478 ms | 0 |
| Thu 03 | 0 | 0.0 | 1677 ms | 0 |
| Thu 05 | 0 | 0.0 | 2193 ms | 0 |
| Thu 07 | 0 | 0.0 | 145 ms | 0 |
| Thu 09 | 0 | 0.0 | 123 ms | 0 |
| Thu 11 | 0 | 0.0 | 165 ms | 0 |
| Thu 14 | 0 | 0.0 | 47 ms | 0 |
| Thu 16 | 0 | 0.0 | 149 ms | 0 |
| Thu 18 | 0 | 0.0 | 62 ms | 0 |
| Thu 20 | 0 | 0.0 | 157 ms | 0 |
| Thu 22 | 0 | 0.0 | 1442 ms | 0 |
| Fri 00 | 0 | 0.0 | 155 ms | 0 |
| Fri 02 | 0 | 0.0 | 223 ms | 0 |
| Fri 04 | 0 | 0.0 | 314 ms | 0 |
| Fri 06 | 0 | 0.0 | 112 ms | 0 |
| Fri 08 | 0 | 0.0 | 157 ms | 0 |
| Fri 10 | 0 | 0.0 | 1850 ms | 0 |
| Fri 12 | 0 | 0.0 | 1953 ms | 0 |
| Fri 14 | 0 | 0.0 | 192 ms | 0 |
| Fri 16 | 0 | 0.0 | 69 ms | 0 |
| Fri 18 | 0 | 0.0 | 201 ms | 0 |
| Fri 19 | 0 | 0.0 | 197 ms | 0 |
| Fri 20 | 0 | 0.0 | 162 ms | 0 |
| Fri 22 | 0 | 0.0 | 83 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 Jüsto 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 Jüsto goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Jüsto alerts to Slack, Discord or a webhook — free.
Jüsto, at justo.mx, is one of the Cloud & developer services we monitor. Haz tu súper desde casa con Jüsto, el primer supermercado 100% digital de México. Frutas, verduras, despensa y más — entrega el mismo día.
Jüsto publishes an official status page at status.justo.mx; when we can read it, its incident level is folded into the status shown here.
Typical issues with 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: 411 ms average, 14–1953 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Jüsto incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
411 ms on average over the last 24 hours (14–1953 ms).
Yes, at https://status.justo.mx.
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 Jüsto here at once, the problem is on Jüsto'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 Jüsto. 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.