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 1 min ago. Last stored result reached it in 382 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 360 ms | 0 |
| Nov 7 | 0 | 0.0 | 191 ms | 0 |
| Nov 7 | 0 | 0.0 | 1181 ms | 0 |
| Nov 7 | 0 | 0.0 | 400 ms | 0 |
| Nov 8 | 0 | 0.0 | 219 ms | 0 |
| Nov 8 | 0 | 0.0 | 230 ms | 0 |
| Nov 8 | 0 | 0.0 | 242 ms | 0 |
| Nov 8 | 0 | 0.0 | 275 ms | 0 |
| Nov 9 | 0 | 0.0 | 375 ms | 0 |
| Nov 9 | 0 | 0.0 | 248 ms | 0 |
| Nov 9 | 0 | 0.0 | 340 ms | 0 |
| Nov 9 | 0 | 0.0 | 244 ms | 0 |
| Nov 10 | 0 | 0.0 | 356 ms | 0 |
| Nov 10 | 0 | 0.0 | 302 ms | 0 |
| Nov 10 | 0 | 0.0 | 498 ms | 0 |
| Nov 10 | 0 | 0.0 | 493 ms | 0 |
| Nov 11 | 0 | 0.0 | 208 ms | 0 |
| Nov 11 | 0 | 0.0 | 243 ms | 0 |
| Nov 11 | 0 | 0.0 | 337 ms | 0 |
| Nov 11 | 0 | 0.0 | 312 ms | 0 |
| Nov 12 | 0 | 0.0 | 430 ms | 0 |
| Nov 12 | 0 | 0.0 | 268 ms | 0 |
| Nov 12 | 0 | 0.0 | 342 ms | 0 |
| Nov 12 | 0 | 0.0 | 283 ms | 0 |
| Nov 13 | 0 | 0.0 | 290 ms | 0 |
| Nov 13 | 0 | 0.0 | 283 ms | 0 |
| Nov 13 | 0 | 0.0 | 355 ms | 0 |
| Nov 13 | 0 | 0.0 | 382 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for orderBilly 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 orderBilly goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send orderBilly alerts to Slack, Discord or a webhook — free.
We track orderBilly (orderbilly.com) as part of the Food group. Billy is een platform dat bestellen en betalen in jouw zaak makkelijk maakt. Billy automatiseert je volledige order-to-cash flow en heeft een flexibele setup voor elk café, restaurant en event.
orderBilly publishes an official status page at status.orderbilly.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 310 ms average, 119–481 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public orderBilly incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
310 ms on average over the last 24 hours (119–481 ms).
Yes, at https://status.orderbilly.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 orderBilly here at once, the problem is on orderBilly'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 orderBilly. 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.