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 2 hr ago. Last stored result reached it in 955 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 1046 ms | 0 |
| Nov 7 | 0 | 0.0 | 1001 ms | 0 |
| Nov 7 | 0 | 0.0 | 1044 ms | 0 |
| Nov 7 | 0 | 0.0 | 922 ms | 0 |
| Nov 7 | 0 | 0.0 | 869 ms | 0 |
| Nov 8 | 0 | 0.0 | 1023 ms | 0 |
| Nov 8 | 0 | 0.0 | 1070 ms | 0 |
| Nov 8 | 0 | 0.0 | 859 ms | 0 |
| Nov 8 | 0 | 0.0 | 848 ms | 0 |
| Nov 9 | 0 | 0.0 | 986 ms | 0 |
| Nov 9 | 0 | 0.0 | 891 ms | 0 |
| Nov 9 | 0 | 0.0 | 1003 ms | 0 |
| Nov 9 | 0 | 0.0 | 961 ms | 0 |
| Nov 10 | 0 | 0.0 | 926 ms | 0 |
| Nov 10 | 0 | 0.0 | 951 ms | 0 |
| Nov 10 | 0 | 0.0 | 901 ms | 0 |
| Nov 10 | 0 | 0.0 | 983 ms | 0 |
| Nov 11 | 0 | 0.0 | 994 ms | 0 |
| Nov 11 | 0 | 0.0 | 911 ms | 0 |
| Nov 11 | 0 | 0.0 | 920 ms | 0 |
| Nov 11 | 0 | 0.0 | 962 ms | 0 |
| Nov 12 | 0 | 0.0 | 917 ms | 0 |
| Nov 12 | 0 | 0.0 | 948 ms | 0 |
| Nov 12 | 0 | 0.0 | 973 ms | 0 |
| Nov 12 | 0 | 0.0 | 952 ms | 0 |
| Nov 13 | 0 | 0.0 | 932 ms | 0 |
| Nov 13 | 0 | 0.0 | 923 ms | 0 |
| Nov 13 | 0 | 0.0 | 927 ms | 0 |
| Nov 13 | 0 | 0.0 | 896 ms | 0 |
| Nov 14 | 0 | 0.0 | 1010 ms | 0 |
| Nov 14 | 0 | 0.0 | 961 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: 965 ms average, 836–1296 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 Sapaad incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
965 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.