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 57 min ago. Last stored result reached it in 28 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 13 | 0 | 0.0 | 100 ms | 0 |
| Tue 16 | 0 | 0.0 | 87 ms | 0 |
| Tue 18 | 0 | 0.0 | 30 ms | 0 |
| Tue 20 | 0 | 0.0 | 175 ms | 0 |
| Tue 22 | 0 | 0.0 | 26 ms | 0 |
| Wed 01 | 0 | 0.0 | 168 ms | 0 |
| Wed 02 | 0 | 0.0 | 35 ms | 0 |
| Wed 04 | 0 | 0.0 | 33 ms | 0 |
| Wed 06 | 0 | 0.0 | 49 ms | 0 |
| Wed 08 | 0 | 0.0 | 55 ms | 0 |
| Wed 11 | 0 | 0.0 | 37 ms | 0 |
| Wed 13 | 0 | 0.0 | 102 ms | 0 |
| Wed 15 | 0 | 0.0 | 37 ms | 0 |
| Wed 17 | 0 | 0.0 | 22 ms | 0 |
| Wed 19 | 0 | 0.0 | 82 ms | 0 |
| Wed 22 | 0 | 0.0 | 66 ms | 0 |
| Thu 00 | 0 | 0.0 | 55 ms | 0 |
| Thu 01 | 0 | 0.0 | 98 ms | 0 |
| Thu 03 | 0 | 0.0 | 114 ms | 0 |
| Thu 05 | 0 | 0.0 | 73 ms | 0 |
| Thu 08 | 0 | 0.0 | 53 ms | 0 |
| Thu 10 | 0 | 0.0 | 115 ms | 0 |
| Thu 12 | 0 | 0.0 | 76 ms | 0 |
| Thu 14 | 0 | 0.0 | 90 ms | 0 |
| Thu 16 | 0 | 0.0 | 88 ms | 0 |
| Thu 18 | 0 | 0.0 | 139 ms | 0 |
| Thu 20 | 0 | 0.0 | 35 ms | 0 |
| Thu 22 | 0 | 0.0 | 52 ms | 0 |
| Fri 00 | 0 | 0.0 | 62 ms | 0 |
| Fri 03 | 0 | 0.0 | 60 ms | 0 |
| Fri 05 | 0 | 0.0 | 40 ms | 0 |
| Fri 07 | 0 | 0.0 | 42 ms | 0 |
| Fri 09 | 0 | 0.0 | 27 ms | 0 |
| Fri 11 | 0 | 0.0 | 86 ms | 0 |
| Fri 12 | 0 | 0.0 | 126 ms | 0 |
| Fri 14 | 0 | 0.0 | 63 ms | 0 |
| Fri 16 | 0 | 0.0 | 80 ms | 0 |
| Fri 18 | 0 | 0.0 | 82 ms | 0 |
| Fri 19 | 0 | 0.0 | 23 ms | 0 |
| Fri 21 | 0 | 0.0 | 23 ms | 0 |
| Fri 23 | 0 | 0.0 | 77 ms | 0 |
| Sat 01 | 0 | 0.0 | 56 ms | 0 |
| Sat 03 | 0 | 0.0 | 80 ms | 0 |
| Sat 05 | 0 | 0.0 | 57 ms | 0 |
| Sat 07 | 0 | 0.0 | 78 ms | 0 |
| Sat 10 | 0 | 0.0 | 19 ms | 0 |
| Sat 12 | 0 | 0.0 | 89 ms | 0 |
| Sat 14 | 0 | 0.0 | 28 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 9 days of data so far, so the 90-day numbers fill in over time.
Scheduled Maintenance - R365 Training (ExpandShare)
R365 Training (ExpandShare) will be undergoing maintenance on November 19th, starting at 2:00 AM Pacific Time for approximately 2 hours. During this time, R365 Training (ExpandShare) will be temporarily unavailable. We appreciate your patience and understanding. If you have any questions, please reach out to the R365 support team.
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for Restaurant365 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 Restaurant365 goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Restaurant365 alerts to Slack, Discord or a webhook — free.
Restaurant365, at restaurant365.com, is one of the Food services we monitor. R365's cloud-based restaurant management software helps leaders master accounting, operations, & workforce to create incredible moments that drive profits.
Restaurant365 publishes an official status page at status.restaurant365.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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 57 ms average, 16–95 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Restaurant365 incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
57 ms on average over the last 24 hours (16–95 ms).
Yes, at https://status.restaurant365.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 Restaurant365 here at once, the problem is on Restaurant365'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 Restaurant365. 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.