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 59 min ago. Last stored result reached it in 481 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 404 ms | 0 |
| Mon 18 | 0 | 0.0 | 244 ms | 0 |
| Mon 20 | 0 | 0.0 | 295 ms | 0 |
| Mon 23 | 0 | 0.0 | 194 ms | 0 |
| Tue 01 | 0 | 0.0 | 368 ms | 0 |
| Tue 03 | 0 | 0.0 | 218 ms | 0 |
| Tue 05 | 0 | 0.0 | 356 ms | 0 |
| Tue 07 | 0 | 0.0 | 302 ms | 0 |
| Tue 09 | 0 | 0.0 | 440 ms | 0 |
| Tue 11 | 0 | 0.0 | 188 ms | 0 |
| Tue 13 | 0 | 0.0 | 483 ms | 0 |
| Tue 16 | 0 | 0.0 | 513 ms | 0 |
| Tue 18 | 0 | 0.0 | 499 ms | 0 |
| Tue 19 | 0 | 0.0 | 382 ms | 0 |
| Tue 21 | 0 | 0.0 | 379 ms | 0 |
| Tue 23 | 0 | 0.0 | 575 ms | 0 |
| Wed 01 | 0 | 0.0 | 310 ms | 0 |
| Wed 04 | 0 | 0.0 | 133 ms | 0 |
| Wed 06 | 0 | 0.0 | 243 ms | 0 |
| Wed 08 | 0 | 0.0 | 393 ms | 0 |
| Wed 10 | 0 | 0.0 | 240 ms | 0 |
| Wed 13 | 0 | 0.0 | 224 ms | 0 |
| Wed 15 | 0 | 0.0 | 337 ms | 0 |
| Wed 17 | 0 | 0.0 | 489 ms | 0 |
| Wed 18 | 0 | 0.0 | 312 ms | 0 |
| Wed 21 | 0 | 0.0 | 481 ms | 0 |
| Wed 23 | 0 | 0.0 | 272 ms | 0 |
| Thu 01 | 0 | 0.0 | 558 ms | 0 |
| Thu 03 | 0 | 0.0 | 430 ms | 0 |
| Thu 04 | 0 | 0.0 | 333 ms | 0 |
| Thu 06 | 0 | 0.0 | 268 ms | 0 |
| Thu 08 | 0 | 0.0 | 217 ms | 0 |
| Thu 10 | 0 | 0.0 | 273 ms | 0 |
| Thu 13 | 0 | 0.0 | 236 ms | 0 |
| Thu 15 | 0 | 0.0 | 342 ms | 0 |
| Thu 17 | 0 | 0.0 | 554 ms | 0 |
| Thu 19 | 0 | 0.0 | 279 ms | 0 |
| Thu 21 | 0 | 0.0 | 283 ms | 0 |
| Thu 23 | 0 | 0.0 | 303 ms | 0 |
| Fri 01 | 0 | 0.0 | 416 ms | 0 |
| Fri 03 | 0 | 0.0 | 290 ms | 0 |
| Fri 05 | 0 | 0.0 | 267 ms | 0 |
| Fri 07 | 0 | 0.0 | 283 ms | 0 |
| Fri 09 | 0 | 0.0 | 297 ms | 0 |
| Fri 11 | 0 | 0.0 | 119 ms | 0 |
| Fri 13 | 0 | 0.0 | 245 ms | 0 |
| Fri 15 | 0 | 0.0 | 355 ms | 0 |
| Fri 17 | 0 | 0.0 | 481 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: 302 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.
302 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.