User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Food
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 37 min ago. Last stored result reached it in 193 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 193 ms | 0 |
| Tue 01 | 0 | 0.0 | 60 ms | 0 |
| Tue 03 | 0 | 0.0 | 91 ms | 0 |
| Tue 05 | 0 | 0.0 | 114 ms | 0 |
| Tue 07 | 0 | 0.0 | 133 ms | 0 |
| Tue 09 | 0 | 0.0 | 88 ms | 0 |
| Tue 11 | 0 | 0.0 | 79 ms | 0 |
| Tue 13 | 0 | 0.0 | 161 ms | 0 |
| Tue 16 | 0 | 0.0 | 180 ms | 0 |
| Tue 18 | 0 | 0.0 | 132 ms | 0 |
| Tue 20 | 0 | 0.0 | 145 ms | 0 |
| Tue 22 | 0 | 0.0 | 120 ms | 0 |
| Wed 01 | 0 | 0.0 | 121 ms | 0 |
| Wed 03 | 0 | 0.0 | 56 ms | 0 |
| Wed 05 | 0 | 0.0 | 143 ms | 0 |
| Wed 07 | 0 | 0.0 | 128 ms | 0 |
| Wed 10 | 0 | 0.0 | 168 ms | 0 |
| Wed 12 | 0 | 0.0 | 122 ms | 0 |
| Wed 14 | 0 | 0.0 | 140 ms | 0 |
| Wed 16 | 0 | 0.0 | 131 ms | 0 |
| Wed 18 | 0 | 0.0 | 186 ms | 0 |
| Wed 20 | 0 | 0.0 | 169 ms | 0 |
| Wed 23 | 0 | 0.0 | 142 ms | 0 |
| Thu 01 | 0 | 0.0 | 170 ms | 0 |
| Thu 03 | 0 | 0.0 | 253 ms | 0 |
| Thu 05 | 0 | 0.0 | 145 ms | 0 |
| Thu 07 | 0 | 0.0 | 34 ms | 0 |
| Thu 09 | 0 | 0.0 | 99 ms | 0 |
| Thu 11 | 0 | 0.0 | 55 ms | 0 |
| Thu 13 | 0 | 0.0 | 50 ms | 0 |
| Thu 15 | 0 | 0.0 | 186 ms | 0 |
| Thu 16 | 0 | 0.0 | 137 ms | 0 |
| Thu 18 | 0 | 0.0 | 134 ms | 0 |
| Thu 20 | 0 | 0.0 | 170 ms | 0 |
| Thu 22 | 0 | 0.0 | 142 ms | 0 |
| Fri 00 | 0 | 0.0 | 119 ms | 0 |
| Fri 02 | 0 | 0.0 | 168 ms | 0 |
| Fri 04 | 0 | 0.0 | 157 ms | 0 |
| Fri 06 | 0 | 0.0 | 170 ms | 0 |
| Fri 08 | 0 | 0.0 | 119 ms | 0 |
| Fri 10 | 0 | 0.0 | 96 ms | 0 |
| Fri 12 | 0 | 0.0 | 40 ms | 0 |
| Fri 14 | 0 | 0.0 | 192 ms | 0 |
| Fri 16 | 0 | 0.0 | 61 ms | 0 |
| Fri 18 | 0 | 0.0 | 171 ms | 0 |
| Fri 19 | 0 | 0.0 | 154 ms | 0 |
| Fri 20 | 0 | 0.0 | 41 ms | 0 |
| Fri 22 | 0 | 0.0 | 193 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 Flipdish 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 Flipdish goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Flipdish alerts to Slack, Discord or a webhook — free.
We track Flipdish (flipdish.com) as part of the Food group. Flipdish is the AI-first restaurant management platform trusted by 5,000+ brands. From AI phone agents and predictive analytics to POS, online ordering and kiosks, built for restaurants that want to lead.
Flipdish publishes an official status page at status.flipdish.com; when we can read it, its incident level is folded into the status shown here.
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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 127 ms average, 33–193 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 Flipdish incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
127 ms on average over the last 24 hours (33–193 ms).
Yes, at https://status.flipdish.com.
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 Flipdish here at once, the problem is on Flipdish'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 Flipdish. 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.