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 25 min ago. Last stored result reached it in 1010 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 03 | 0 | 0.0 | 1047 ms | 0 |
| Tue 05 | 0 | 0.0 | 926 ms | 0 |
| Tue 07 | 0 | 0.0 | 1201 ms | 0 |
| Tue 09 | 0 | 0.0 | 951 ms | 0 |
| Tue 11 | 0 | 0.0 | 923 ms | 0 |
| Tue 13 | 0 | 0.0 | 864 ms | 0 |
| Tue 16 | 0 | 0.0 | 937 ms | 0 |
| Tue 18 | 0 | 0.0 | 1143 ms | 0 |
| Tue 20 | 0 | 0.0 | 934 ms | 0 |
| Tue 23 | 0 | 0.0 | 951 ms | 0 |
| Wed 01 | 0 | 0.0 | 863 ms | 0 |
| Wed 03 | 0 | 0.0 | 1031 ms | 0 |
| Wed 05 | 0 | 0.0 | 1105 ms | 0 |
| Wed 07 | 0 | 0.0 | 898 ms | 0 |
| Wed 10 | 0 | 0.0 | 911 ms | 0 |
| Wed 12 | 0 | 0.0 | 916 ms | 0 |
| Wed 14 | 0 | 0.0 | 885 ms | 0 |
| Wed 16 | 0 | 0.0 | 1102 ms | 0 |
| Wed 18 | 0 | 0.0 | 1197 ms | 0 |
| Wed 21 | 0 | 0.0 | 962 ms | 0 |
| Wed 23 | 0 | 0.0 | 864 ms | 0 |
| Thu 01 | 0 | 0.0 | 917 ms | 0 |
| Thu 03 | 0 | 0.0 | 1087 ms | 0 |
| Thu 05 | 0 | 0.0 | 876 ms | 0 |
| Thu 07 | 0 | 0.0 | 903 ms | 0 |
| Thu 09 | 0 | 0.0 | 1007 ms | 0 |
| Thu 11 | 0 | 0.0 | 948 ms | 0 |
| Thu 13 | 0 | 0.0 | 973 ms | 0 |
| Thu 15 | 0 | 0.0 | 875 ms | 0 |
| Thu 17 | 0 | 0.0 | 1025 ms | 0 |
| Thu 20 | 0 | 0.0 | 951 ms | 0 |
| Thu 22 | 0 | 0.0 | 1011 ms | 0 |
| Fri 00 | 0 | 0.0 | 890 ms | 0 |
| Fri 03 | 0 | 0.0 | 932 ms | 0 |
| Fri 05 | 0 | 0.0 | 1071 ms | 0 |
| Fri 07 | 0 | 0.0 | 923 ms | 0 |
| Fri 09 | 0 | 0.0 | 977 ms | 0 |
| Fri 11 | 0 | 0.0 | 836 ms | 0 |
| Fri 13 | 0 | 0.0 | 1011 ms | 0 |
| Fri 15 | 0 | 0.0 | 844 ms | 0 |
| Fri 17 | 0 | 0.0 | 927 ms | 0 |
| Fri 18 | 0 | 0.0 | 862 ms | 0 |
| Fri 20 | 0 | 0.0 | 880 ms | 0 |
| Fri 21 | 0 | 0.0 | 1296 ms | 0 |
| Fri 23 | 0 | 0.0 | 911 ms | 0 |
| Sat 01 | 0 | 0.0 | 891 ms | 0 |
| Sat 03 | 0 | 0.0 | 1139 ms | 0 |
| Sat 05 | 0 | 0.0 | 1010 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.
No outages on record for Sapaad 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 Sapaad goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Sapaad alerts to Slack, Discord or a webhook — free.
Sapaad is listed in our Food category and checked at sapaad.com. Sapaad's cloud-based POS and all-in-one restaurant management solution empowers your team to improve your service quality, boost sales, and manage costs.
Sapaad publishes an official status page at status.sapaad.com; when we can read it, its incident level is folded into the status shown here.
Typical issues 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 962 ms average, 836–1296 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 Sapaad incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
962 ms on average over the last 24 hours (836–1296 ms).
Yes, at https://status.sapaad.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 Sapaad here at once, the problem is on Sapaad'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 Sapaad. 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.