User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Food
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Microsoft 365 disturbance preventing tickets from being created
Source: the vendor's status page · We are not affiliated with Future Ordering.
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.
Reachable from all 4 regions we check from.
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 1 hr ago. Last stored result reached it in 57 ms.
Minor incident
Microsoft 365 disturbance preventing tickets from being created Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 8 | 0 | 0.0 | 58 ms | 0 |
| Nov 8 | 0 | 0.0 | 96 ms | 0 |
| Nov 8 | 0 | 0.0 | 71 ms | 0 |
| Nov 8 | 0 | 0.0 | 72 ms | 0 |
| Nov 9 | 0 | 0.0 | 113 ms | 0 |
| Nov 9 | 0 | 0.0 | 75 ms | 0 |
| Nov 9 | 0 | 0.0 | 77 ms | 0 |
| Nov 9 | 0 | 0.0 | 76 ms | 0 |
| Nov 10 | 0 | 0.0 | 92 ms | 0 |
| Nov 10 | 0 | 0.0 | 68 ms | 0 |
| Nov 10 | 0 | 0.0 | 169 ms | 0 |
| Nov 10 | 0 | 0.0 | 92 ms | 0 |
| Nov 11 | 0 | 0.0 | 81 ms | 0 |
| Nov 11 | 0 | 0.0 | 123 ms | 0 |
| Nov 11 | 0 | 0.0 | 69 ms | 0 |
| Nov 11 | 0 | 0.0 | 80 ms | 0 |
| Nov 12 | 0 | 0.0 | 86 ms | 0 |
| Nov 12 | 0 | 0.0 | 85 ms | 0 |
| Nov 12 | 0 | 0.0 | 79 ms | 0 |
| Nov 12 | 0 | 0.0 | 115 ms | 0 |
| Nov 13 | 0 | 0.0 | 83 ms | 0 |
| Nov 13 | 0 | 0.0 | 91 ms | 0 |
| Nov 13 | 0 | 0.0 | 107 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 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Future Ordering 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 Future Ordering goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Future Ordering alerts to Slack, Discord or a webhook — free.
We track Future Ordering (futureordering.com) as part of the Food group. Welcome to Future Ordering - digital food ordering platform for profitable restaurant operations.
Future Ordering publishes an official status page at status.futureordering.com; when we can read it, its incident level is folded into the status shown here.
Common problems for 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 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 90 ms average, 33–157 ms range across 12 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Microsoft 365 disturbance preventing tickets from being created
We have not recorded a public Future Ordering incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
90 ms on average over the last 24 hours (33–157 ms). Latest regional checks: US East 42 ms, US West 63 ms, Europe 46 ms, Asia-Pacific 135 ms.
Yes, at https://status.futureordering.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 Future Ordering here at once, the problem is on Future Ordering'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 Future Ordering. 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.