User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
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 57 min ago. Last stored result reached it in 442 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 494 ms | 0 |
| Mon 23 | 0 | 0.0 | 1113 ms | 0 |
| Tue 01 | 0 | 0.0 | 1241 ms | 0 |
| Tue 03 | 0 | 0.0 | 385 ms | 0 |
| Tue 05 | 0 | 0.0 | 545 ms | 0 |
| Tue 08 | 0 | 0.0 | 610 ms | 0 |
| Tue 10 | 0 | 0.0 | 381 ms | 0 |
| Tue 12 | 0 | 0.0 | 386 ms | 0 |
| Tue 14 | 0 | 0.0 | 445 ms | 0 |
| Tue 16 | 0 | 0.0 | 363 ms | 0 |
| Tue 19 | 0 | 0.0 | 983 ms | 0 |
| Tue 21 | 0 | 0.0 | 459 ms | 0 |
| Tue 23 | 0 | 0.0 | 495 ms | 0 |
| Wed 01 | 0 | 0.0 | 351 ms | 0 |
| Wed 04 | 0 | 0.0 | 341 ms | 0 |
| Wed 06 | 0 | 0.0 | 400 ms | 0 |
| Wed 08 | 0 | 0.0 | 376 ms | 0 |
| Wed 10 | 0 | 0.0 | 371 ms | 0 |
| Wed 13 | 0 | 0.0 | 900 ms | 0 |
| Wed 15 | 0 | 0.0 | 774 ms | 0 |
| Wed 17 | 0 | 0.0 | 410 ms | 0 |
| Wed 19 | 0 | 0.0 | 371 ms | 0 |
| Wed 21 | 0 | 0.0 | 394 ms | 0 |
| Wed 23 | 0 | 0.0 | 2103 ms | 0 |
| Thu 02 | 0 | 0.0 | 487 ms | 0 |
| Thu 04 | 0 | 0.0 | 801 ms | 0 |
| Thu 06 | 0 | 0.0 | 313 ms | 0 |
| Thu 08 | 0 | 0.0 | 551 ms | 0 |
| Thu 10 | 0 | 0.0 | 723 ms | 0 |
| Thu 12 | 0 | 0.0 | 761 ms | 0 |
| Thu 14 | 0 | 0.0 | 372 ms | 0 |
| Thu 16 | 0 | 0.0 | 542 ms | 0 |
| Thu 18 | 0 | 0.0 | 415 ms | 0 |
| Thu 20 | 0 | 0.0 | 400 ms | 0 |
| Thu 22 | 0 | 0.0 | 381 ms | 0 |
| Thu 23 | 0 | 0.0 | 809 ms | 0 |
| Fri 01 | 0 | 0.0 | 403 ms | 0 |
| Fri 03 | 0 | 0.0 | 408 ms | 0 |
| Fri 05 | 0 | 0.0 | 399 ms | 0 |
| Fri 07 | 0 | 0.0 | 602 ms | 0 |
| Fri 09 | 0 | 0.0 | 416 ms | 0 |
| Fri 11 | 0 | 0.0 | 376 ms | 0 |
| Fri 13 | 0 | 0.0 | 382 ms | 0 |
| Fri 15 | 0 | 0.0 | 446 ms | 0 |
| Fri 17 | 0 | 0.0 | 458 ms | 0 |
| Fri 19 | 0 | 0.0 | 527 ms | 0 |
| Fri 21 | 0 | 0.0 | 671 ms | 0 |
| Fri 23 | 0 | 0.0 | 442 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 onebullex 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 onebullex goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send onebullex alerts to Slack, Discord or a webhook — free.
We track onebullex (onebullex.com) as part of the Money group. Trade crypto securely on OneBullEx. Access spot & futures markets, top trading pairs, fast execution, and institutional-grade security.
onebullex publishes an official status page at status.onebullex.com; when we can read it, its incident level is folded into the status shown here.
Common problems for money services: login and two-factor problems, payments or transfers failing, and app errors.
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: 477 ms average, 374–968 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 onebullex incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
477 ms on average over the last 24 hours (374–968 ms).
Yes, at https://status.onebullex.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For money services, watch for login and two-factor problems, payments or transfers failing, and app errors. If many people report onebullex here at once, the problem is on onebullex'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 onebullex. 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.