User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Shopping
ubereats.com · Shopping
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Tests ubereats.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 542 ms · 4 min ago.
No status feed
Uber Eats does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 11:30 | 0 | 0.0 | 448 ms | 0 |
| 11:45 | 0 | 0.0 | 340 ms | 0 |
| 12:00 | 0 | 0.0 | 390 ms | 0 |
| 12:15 | 0 | 0.0 | 439 ms | 0 |
| 12:30 | 0 | 0.0 | 367 ms | 0 |
| 12:45 | 0 | 0.0 | 424 ms | 0 |
| 13:00 | 0 | 0.0 | 409 ms | 0 |
| 13:15 | 0 | 0.0 | 430 ms | 0 |
| 13:30 | 0 | 0.0 | 396 ms | 0 |
| 13:45 | 0 | 0.0 | 326 ms | 0 |
| 14:00 | 0 | 0.0 | 403 ms | 0 |
| 14:15 | 0 | 0.0 | 453 ms | 0 |
| 14:30 | 0 | 0.0 | 357 ms | 0 |
| 14:45 | 0 | 0.0 | 549 ms | 0 |
| 15:00 | 0 | 0.0 | 493 ms | 0 |
| 15:15 | 0 | 0.0 | 412 ms | 0 |
| 15:30 | 0 | 0.0 | 477 ms | 0 |
| 15:45 | 0 | 0.0 | 448 ms | 0 |
| 16:00 | 0 | 0.0 | 444 ms | 0 |
| 16:15 | 0 | 0.0 | 597 ms | 0 |
| 16:30 | 0 | 0.0 | 427 ms | 0 |
| 16:45 | 0 | 0.0 | 502 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed this status badge · JSON
No outages on record for Uber Eats 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 Uber Eats goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Checks are succeeding and user reports are near the baseline.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.