User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Food
Is Future Ordering down?
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.
What to try while Future Ordering is having problems
- If the app is down, order from the restaurant by phone or its own site, and check order status before reordering to avoid double charges.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → futureordering.com—
Your browser → us—
Our checksReaching it
Official · ReportsMinor incident · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 50 min ago. Last stored result reached it in 57 ms.
Official status
Minor incident
Microsoft 365 disturbance preventing tickets from being created Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 77 ms | 0 |
| Mon 14 | 0 | 0.0 | 35 ms | 0 |
| Mon 16 | 0 | 0.0 | 115 ms | 0 |
| Mon 18 | 0 | 0.0 | 57 ms | 0 |
| Mon 21 | 0 | 0.0 | 76 ms | 0 |
| Mon 23 | 0 | 0.0 | 196 ms | 0 |
| Tue 01 | 0 | 0.0 | 188 ms | 0 |
| Tue 03 | 0 | 0.0 | 92 ms | 0 |
| Tue 05 | 0 | 0.0 | 38 ms | 0 |
| Tue 07 | 0 | 0.0 | 36 ms | 0 |
| Tue 09 | 0 | 0.0 | 111 ms | 0 |
| Tue 11 | 0 | 0.0 | 68 ms | 0 |
| Tue 14 | 0 | 0.0 | 236 ms | 0 |
| Tue 16 | 0 | 0.0 | 101 ms | 0 |
| Tue 18 | 0 | 0.0 | 120 ms | 0 |
| Tue 20 | 0 | 0.0 | 92 ms | 0 |
| Tue 23 | 0 | 0.0 | 59 ms | 0 |
| Wed 01 | 0 | 0.0 | 153 ms | 0 |
| Wed 03 | 0 | 0.0 | 69 ms | 0 |
| Wed 05 | 0 | 0.0 | 81 ms | 0 |
| Wed 08 | 0 | 0.0 | 208 ms | 0 |
| Wed 10 | 0 | 0.0 | 37 ms | 0 |
| Wed 12 | 0 | 0.0 | 140 ms | 0 |
| Wed 14 | 0 | 0.0 | 51 ms | 0 |
| Wed 16 | 0 | 0.0 | 69 ms | 0 |
| Wed 18 | 0 | 0.0 | 38 ms | 0 |
| Wed 21 | 0 | 0.0 | 80 ms | 0 |
| Wed 23 | 0 | 0.0 | 111 ms | 0 |
| Thu 01 | 0 | 0.0 | 77 ms | 0 |
| Thu 03 | 0 | 0.0 | 193 ms | 0 |
| Thu 05 | 0 | 0.0 | 86 ms | 0 |
| Thu 07 | 0 | 0.0 | 85 ms | 0 |
| Thu 09 | 0 | 0.0 | 112 ms | 0 |
| Thu 11 | 0 | 0.0 | 59 ms | 0 |
| Thu 13 | 0 | 0.0 | 121 ms | 0 |
| Thu 15 | 0 | 0.0 | 46 ms | 0 |
| Thu 17 | 0 | 0.0 | 79 ms | 0 |
| Thu 19 | 0 | 0.0 | 132 ms | 0 |
| Thu 22 | 0 | 0.0 | 97 ms | 0 |
| Fri 00 | 0 | 0.0 | 33 ms | 0 |
| Fri 01 | 0 | 0.0 | 140 ms | 0 |
| Fri 03 | 0 | 0.0 | 45 ms | 0 |
| Fri 05 | 0 | 0.0 | 121 ms | 0 |
| Fri 07 | 0 | 0.0 | 91 ms | 0 |
| Fri 09 | 0 | 0.0 | 34 ms | 0 |
| Fri 11 | 0 | 0.0 | 91 ms | 0 |
| Fri 13 | 0 | 0.0 | 157 ms | 0 |
| Fri 15 | 0 | 0.0 | 57 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live Future Ordering badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Future Ordering yet. Outages of 10 minutes or more get their own page here.
Having trouble with Future Ordering?
One report per service every 10 minutes from this network. No account.
Follow Future Ordering
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.
About Future Ordering
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.
Questions
Is Future Ordering down right now?
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
When was Future Ordering last down?
We have not recorded a public Future Ordering incident since monitoring began 6 days ago.
What is Future Ordering's uptime?
From our own checks: 100% over 6 days of checks.
How fast does Future Ordering respond?
90 ms on average over the last 24 hours (33–157 ms).
Does Future Ordering have an official status page?
Yes, at https://status.futureordering.com.
Future Ordering not working for me but the status is fine. What now?
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.