User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Shopping
Is Judge.me 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 → judge.me—
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 59 min ago. Last stored result reached it in 90 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 |
|---|---|---|---|---|
| Tue 07 | 0 | 0.0 | 90 ms | 0 |
| Tue 09 | 0 | 0.0 | 269 ms | 0 |
| Tue 11 | 0 | 0.0 | 471 ms | 0 |
| Tue 13 | 0 | 0.0 | 112 ms | 0 |
| Tue 15 | 0 | 0.0 | 217 ms | 0 |
| Tue 17 | 0 | 0.0 | 486 ms | 0 |
| Tue 20 | 0 | 0.0 | 212 ms | 0 |
| Tue 22 | 0 | 0.0 | 480 ms | 0 |
| Wed 00 | 0 | 0.0 | 102 ms | 0 |
| Wed 02 | 0 | 0.0 | 434 ms | 0 |
| Wed 05 | 0 | 0.0 | 277 ms | 0 |
| Wed 07 | 0 | 0.0 | 135 ms | 0 |
| Wed 09 | 0 | 0.0 | — | 0 |
| Wed 11 | 0 | 0.0 | 253 ms | 0 |
| Wed 13 | 0 | 0.0 | 89 ms | 0 |
| Wed 16 | 0 | 0.0 | 282 ms | 0 |
| Wed 18 | 0 | 0.0 | 103 ms | 0 |
| Wed 20 | 0 | 0.0 | 266 ms | 0 |
| Wed 22 | 0 | 0.0 | 245 ms | 0 |
| Thu 00 | 0 | 0.0 | 199 ms | 0 |
| Thu 02 | 0 | 0.0 | 272 ms | 0 |
| Thu 04 | 0 | 0.0 | 98 ms | 0 |
| Thu 06 | 0 | 0.0 | 125 ms | 0 |
| Thu 08 | 0 | 0.0 | 111 ms | 0 |
| Thu 11 | 0 | 0.0 | 224 ms | 0 |
| Thu 13 | 0 | 0.0 | 84 ms | 0 |
| Thu 15 | 0 | 0.0 | 86 ms | 0 |
| Thu 17 | 0 | 0.0 | 588 ms | 0 |
| Thu 19 | 0 | 0.0 | 90 ms | 0 |
| Thu 21 | 0 | 0.0 | 471 ms | 0 |
| Thu 23 | 0 | 0.0 | 217 ms | 0 |
| Fri 01 | 0 | 0.0 | 227 ms | 0 |
| Fri 03 | 0 | 0.0 | 86 ms | 0 |
| Fri 05 | 0 | 0.0 | 229 ms | 0 |
| Fri 06 | 0 | 0.0 | 54 ms | 0 |
| Fri 08 | 0 | 0.0 | 238 ms | 0 |
| Fri 10 | 0 | 0.0 | 231 ms | 0 |
| Fri 11 | 0 | 0.0 | 298 ms | 0 |
| Fri 13 | 0 | 0.0 | 130 ms | 0 |
| Fri 15 | 0 | 0.0 | 193 ms | 0 |
| Fri 17 | 0 | 0.0 | 113 ms | 0 |
| Fri 18 | 0 | 0.0 | 217 ms | 0 |
| Fri 20 | 0 | 0.0 | 217 ms | 0 |
| Fri 22 | 0 | 0.0 | 279 ms | 0 |
| Fri 23 | 0 | 0.0 | 107 ms | 0 |
| Sat 01 | 0 | 0.0 | 161 ms | 0 |
| Sat 02 | 0 | 0.0 | 235 ms | 0 |
| Sat 03 | 0 | 0.0 | 91 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 9 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Judge.me 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 Judge.me yet. Outages of 10 minutes or more get their own page here.
Having trouble with Judge.me?
One report per service every 10 minutes from this network. No account.
Follow Judge.me
Get an email when Judge.me goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Judge.me alerts to Slack, Discord or a webhook — free.
About Judge.me
We track Judge.me (judge.me) as part of the Shopping group. Judge.me helps you collect, showcase, and share product and store reviews with high-converting widgets and integrations. Build trust and boost sales.
Judge.me publishes an official status page at status.judge.me; when we can read it, its incident level is folded into the status shown here.
Common problems for shopping services: checkout and payment errors, carts not loading, and order tracking problems.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 185 ms average, 54–298 ms range across 19 successful checks.
Questions
Is Judge.me down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Judge.me last down?
We have not recorded a public Judge.me incident since monitoring began 9 days ago.
What is Judge.me's uptime?
From our own checks: 100% over 9 days of checks.
How fast does Judge.me respond?
185 ms on average over the last 24 hours (54–298 ms).
Does Judge.me have an official status page?
Yes, at https://status.judge.me.
Judge.me 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 shopping services, watch for checkout and payment errors, carts not loading, and order tracking problems. If many people report Judge.me here at once, the problem is on Judge.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 Judge.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.