User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 15 min ago. Last stored result reached it in 298 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 08 | 0 | 0.0 | 319 ms | 0 |
| Tue 11 | 0 | 0.0 | 288 ms | 0 |
| Tue 13 | 0 | 0.0 | 327 ms | 0 |
| Tue 15 | 0 | 0.0 | 170 ms | 0 |
| Tue 17 | 0 | 0.0 | 395 ms | 0 |
| Tue 20 | 0 | 0.0 | 302 ms | 0 |
| Tue 22 | 0 | 0.0 | 346 ms | 0 |
| Wed 00 | 0 | 0.0 | 390 ms | 0 |
| Wed 02 | 0 | 0.0 | 126 ms | 0 |
| Wed 05 | 0 | 0.0 | 305 ms | 0 |
| Wed 07 | 0 | 0.0 | 266 ms | 0 |
| Wed 09 | 0 | 0.0 | 140 ms | 0 |
| Wed 11 | 0 | 0.0 | 162 ms | 0 |
| Wed 13 | 0 | 0.0 | 372 ms | 0 |
| Wed 15 | 0 | 0.0 | 322 ms | 0 |
| Wed 18 | 0 | 0.0 | 368 ms | 0 |
| Wed 20 | 0 | 0.0 | 191 ms | 0 |
| Wed 22 | 0 | 0.0 | 349 ms | 0 |
| Thu 00 | 0 | 0.0 | 294 ms | 0 |
| Thu 02 | 0 | 0.0 | 292 ms | 0 |
| Thu 04 | 0 | 0.0 | 325 ms | 0 |
| Thu 06 | 0 | 0.0 | 285 ms | 0 |
| Thu 09 | 0 | 0.0 | 309 ms | 0 |
| Thu 11 | 0 | 0.0 | 328 ms | 0 |
| Thu 13 | 0 | 0.0 | 309 ms | 0 |
| Thu 15 | 0 | 0.0 | 328 ms | 0 |
| Thu 17 | 0 | 0.0 | 211 ms | 0 |
| Thu 19 | 0 | 0.0 | 167 ms | 0 |
| Thu 21 | 0 | 0.0 | 165 ms | 0 |
| Thu 23 | 0 | 0.0 | 227 ms | 0 |
| Fri 01 | 0 | 0.0 | 347 ms | 0 |
| Fri 03 | 0 | 0.0 | 261 ms | 0 |
| Fri 05 | 0 | 0.0 | 280 ms | 0 |
| Fri 07 | 0 | 0.0 | 368 ms | 0 |
| Fri 09 | 0 | 0.0 | 349 ms | 0 |
| Fri 11 | 0 | 0.0 | 202 ms | 0 |
| Fri 13 | 0 | 0.0 | 361 ms | 0 |
| Fri 15 | 0 | 0.0 | 331 ms | 0 |
| Fri 17 | 0 | 0.0 | 359 ms | 0 |
| Fri 19 | 0 | 0.0 | 354 ms | 0 |
| Fri 21 | 0 | 0.0 | 165 ms | 0 |
| Fri 22 | 0 | 0.0 | 348 ms | 0 |
| Fri 23 | 0 | 0.0 | 297 ms | 0 |
| Sat 01 | 0 | 0.0 | 339 ms | 0 |
| Sat 04 | 0 | 0.0 | 289 ms | 0 |
| Sat 06 | 0 | 0.0 | 207 ms | 0 |
| Sat 07 | 0 | 0.0 | 298 ms | 0 |
| Sat 08 | 0 | 0.0 | 176 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Ordergroove 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 Ordergroove goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Ordergroove alerts to Slack, Discord or a webhook — free.
We track Ordergroove (ordergroove.com) as part of the AI group. Migrate to Ordergroove's enterprise autonomous eCommerce subscription platform. AI-powered optimization and tools to drive recurring revenue and reduce churn.
Ordergroove publishes an official status page at status.ordergroove.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 291 ms average, 165–361 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 Ordergroove incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
291 ms on average over the last 24 hours (165–361 ms).
Yes, at https://status.ordergroove.com.
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 Ordergroove here at once, the problem is on Ordergroove'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 Ordergroove. 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.