User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
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 54 min ago. Last stored result reached it in 89 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 194 ms | 0 |
| Mon 18 | 0 | 0.0 | 101 ms | 0 |
| Mon 20 | 0 | 0.0 | 90 ms | 0 |
| Mon 22 | 0 | 0.0 | 173 ms | 0 |
| Tue 00 | 0 | 0.0 | 83 ms | 0 |
| Tue 02 | 0 | 0.0 | 106 ms | 0 |
| Tue 05 | 0 | 0.0 | 113 ms | 0 |
| Tue 07 | 0 | 0.0 | 93 ms | 0 |
| Tue 09 | 0 | 0.0 | 87 ms | 0 |
| Tue 11 | 0 | 0.0 | 91 ms | 0 |
| Tue 13 | 0 | 0.0 | 141 ms | 0 |
| Tue 15 | 0 | 0.0 | 114 ms | 0 |
| Tue 18 | 0 | 0.0 | 142 ms | 0 |
| Tue 20 | 0 | 0.0 | 88 ms | 0 |
| Tue 22 | 0 | 0.0 | 181 ms | 0 |
| Wed 00 | 0 | 0.0 | 97 ms | 0 |
| Wed 03 | 0 | 0.0 | 126 ms | 0 |
| Wed 05 | 0 | 0.0 | 117 ms | 0 |
| Wed 07 | 0 | 0.0 | 53 ms | 0 |
| Wed 09 | 0 | 0.0 | 117 ms | 0 |
| Wed 12 | 0 | 0.0 | 67 ms | 0 |
| Wed 14 | 0 | 0.0 | 110 ms | 0 |
| Wed 16 | 0 | 0.0 | 116 ms | 0 |
| Wed 18 | 0 | 0.0 | 167 ms | 0 |
| Wed 20 | 0 | 0.0 | 110 ms | 0 |
| Wed 22 | 0 | 0.0 | 91 ms | 0 |
| Thu 01 | 0 | 0.0 | 140 ms | 0 |
| Thu 03 | 0 | 0.0 | 137 ms | 0 |
| Thu 05 | 0 | 0.0 | 54 ms | 0 |
| Thu 07 | 0 | 0.0 | 106 ms | 0 |
| Thu 09 | 0 | 0.0 | 90 ms | 0 |
| Thu 11 | 0 | 0.0 | 73 ms | 0 |
| Thu 13 | 0 | 0.0 | 180 ms | 0 |
| Thu 15 | 0 | 0.0 | 125 ms | 0 |
| Thu 17 | 0 | 0.0 | 168 ms | 0 |
| Thu 19 | 0 | 0.0 | 93 ms | 0 |
| Thu 21 | 0 | 0.0 | 97 ms | 0 |
| Thu 23 | 0 | 0.0 | 90 ms | 0 |
| Fri 01 | 0 | 0.0 | 101 ms | 0 |
| Fri 03 | 0 | 0.0 | 156 ms | 0 |
| Fri 06 | 0 | 0.0 | 117 ms | 0 |
| Fri 08 | 0 | 0.0 | 109 ms | 0 |
| Fri 10 | 0 | 0.0 | 66 ms | 0 |
| Fri 11 | 0 | 0.0 | 78 ms | 0 |
| Fri 12 | 0 | 0.0 | 86 ms | 0 |
| Fri 14 | 0 | 0.0 | 41 ms | 0 |
| Fri 16 | 0 | 0.0 | 123 ms | 0 |
| Fri 17 | 0 | 0.0 | 89 ms | 0 |
No outages on record for Orbee 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 Orbee goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Orbee alerts to Slack, Discord or a webhook — free.
Orbee is listed in our Cloud & developer category and checked at orbee.com. Orbee is the automotive data platform that unifies every customer signal so dealerships can activate smarter audiences, run better campaigns, and close more deals.
Orbee publishes an official status page at status.orbee.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Response time over the last 24 hours: 96 ms average, 41–156 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
96 ms on average over the last 24 hours (41–156 ms).
Yes, at https://status.orbee.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Orbee here at once, the problem is on Orbee'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 Orbee. 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.