User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Food
resy.com · Food
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what 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, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 297 ms · 5 min ago.
No status feed
Resy does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 13:15 | 0 | 0.0 | 428 ms | 0 |
| 13:30 | 0 | 0.0 | 717 ms | 0 |
| 13:45 | 0 | 0.0 | 245 ms | 0 |
| 14:00 | 0 | 0.0 | 190 ms | 0 |
| 14:15 | 0 | 0.0 | 120 ms | 0 |
| 14:30 | 0 | 0.0 | 206 ms | 0 |
| 14:45 | 0 | 0.0 | 575 ms | 0 |
| 15:00 | 0 | 0.0 | 390 ms | 0 |
| 15:15 | 0 | 0.0 | 646 ms | 0 |
| 15:30 | 0 | 0.0 | 441 ms | 0 |
| 15:45 | 0 | 0.0 | 368 ms | 0 |
| 16:00 | 0 | 0.0 | 1416 ms | 0 |
| 16:15 | 0 | 0.0 | 252 ms | 0 |
| 16:30 | 0 | 0.0 | 505 ms | 0 |
| 16:45 | 0 | 0.0 | 535 ms | 0 |
| 17:00 | 0 | 0.0 | 462 ms | 0 |
| 17:15 | 0 | 0.0 | 292 ms | 0 |
| 17:30 | 0 | 0.0 | 528 ms | 0 |
| 17:45 | 0 | 0.0 | 265 ms | 0 |
| 18:00 | 0 | 0.0 | 842 ms | 0 |
| 18:15 | 0 | 0.0 | 424 ms | 0 |
| 18:30 | 0 | 0.0 | 382 ms | 0 |
| 18:45 | 0 | 0.0 | 585 ms | 0 |
| 19:00 | 0 | 0.0 | 213 ms | 0 |
| 19:15 | 0 | 0.0 | 663 ms | 0 |
| 19:30 | 0 | 0.0 | 646 ms | 0 |
| 19:45 | 0 | 0.0 | 640 ms | 0 |
| 20:00 | 0 | 0.0 | 706 ms | 0 |
| 20:15 | 0 | 0.0 | 446 ms | 0 |
| 20:30 | 0 | 0.0 | 162 ms | 0 |
| 20:45 | 0 | 0.0 | 397 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.
No outages on record for Resy 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 Resy goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Resy alerts to Slack, Discord or a webhook — free.
Resy is listed in our Food category and checked at resy.com. Live checks and user reports.
Resy has no official status feed we can read, so this page relies on our own checks and user reports.
What usually goes wrong with food services: ordering and checkout failures, delivery tracking stalling, and restaurant menus not loading at peak meal times.
Measured uptime from our checks: 100% over 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 496 ms average, 47–2482 ms range across 59 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public Resy incident since monitoring began 1 day ago.
From our own checks: 100% over 1 day of checks.
496 ms on average over the last 24 hours (47–2482 ms).
Not one we can read. This page uses independent checks of resy.com and user reports.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For food services, watch for ordering and checkout failures, delivery tracking stalling, and restaurant menus not loading at peak meal times. If many people report Resy here at once, the problem is on Resy's side.