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 1 hr ago. Last stored result reached it in 1440 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 2150 ms | 0 |
| Tue 00 | 0 | 0.0 | 1863 ms | 0 |
| Tue 02 | 0 | 0.0 | 1539 ms | 0 |
| Tue 04 | 0 | 0.0 | 1950 ms | 0 |
| Tue 06 | 0 | 0.0 | 1681 ms | 0 |
| Tue 08 | 0 | 0.0 | 1509 ms | 0 |
| Tue 10 | 0 | 0.0 | 1546 ms | 0 |
| Tue 12 | 0 | 0.0 | 1640 ms | 0 |
| Tue 15 | 0 | 0.0 | 2018 ms | 0 |
| Tue 17 | 0 | 0.0 | 1586 ms | 0 |
| Tue 19 | 0 | 0.0 | 1553 ms | 0 |
| Tue 21 | 0 | 0.0 | 1633 ms | 0 |
| Wed 00 | 0 | 0.0 | 1924 ms | 0 |
| Wed 02 | 0 | 0.0 | 1501 ms | 0 |
| Wed 04 | 0 | 0.0 | 882 ms | 0 |
| Wed 06 | 0 | 0.0 | 861 ms | 0 |
| Wed 09 | 0 | 0.0 | 798 ms | 0 |
| Wed 11 | 0 | 0.0 | 993 ms | 0 |
| Wed 13 | 0 | 0.0 | 1615 ms | 0 |
| Wed 15 | 0 | 0.0 | 1502 ms | 0 |
| Wed 17 | 0 | 0.0 | 1927 ms | 0 |
| Wed 19 | 0 | 0.0 | 1731 ms | 0 |
| Wed 22 | 0 | 0.0 | 1981 ms | 0 |
| Thu 00 | 0 | 0.0 | 1757 ms | 0 |
| Thu 02 | 0 | 0.0 | 1678 ms | 0 |
| Thu 04 | 0 | 0.0 | 1642 ms | 0 |
| Thu 06 | 0 | 0.0 | 1711 ms | 0 |
| Thu 08 | 0 | 0.0 | 1631 ms | 0 |
| Thu 10 | 0 | 0.0 | 1624 ms | 0 |
| Thu 12 | 0 | 0.0 | 1628 ms | 0 |
| Thu 14 | 0 | 0.0 | 1246 ms | 0 |
| Thu 16 | 0 | 0.0 | 1498 ms | 0 |
| Thu 18 | 0 | 0.0 | 1751 ms | 0 |
| Thu 20 | 0 | 0.0 | 1618 ms | 0 |
| Thu 22 | 0 | 0.0 | 1680 ms | 0 |
| Fri 00 | 0 | 0.0 | 1671 ms | 0 |
| Fri 03 | 0 | 0.0 | 1536 ms | 0 |
| Fri 05 | 0 | 0.0 | 1280 ms | 0 |
| Fri 07 | 0 | 0.0 | 1230 ms | 0 |
| Fri 09 | 0 | 0.0 | 1329 ms | 0 |
| Fri 10 | 0 | 0.0 | 1258 ms | 0 |
| Fri 11 | 0 | 0.0 | 1325 ms | 0 |
| Fri 13 | 0 | 0.0 | 1321 ms | 0 |
| Fri 15 | 0 | 0.0 | 1465 ms | 0 |
| Fri 17 | 0 | 0.0 | 1621 ms | 0 |
| Fri 18 | 0 | 0.0 | 1849 ms | 0 |
| Fri 19 | 0 | 0.0 | 1404 ms | 0 |
| Fri 21 | 0 | 0.0 | 1440 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 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for B4Checkin 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 B4Checkin goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send B4Checkin alerts to Slack, Discord or a webhook — free.
We track B4Checkin (b4checkin.com) as part of the Money group. Explore hotel payment solutions that eliminate paperwork and enhance efficiency with our secure online payment portal.
B4Checkin publishes an official status page at status.b4checkin.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 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 1426 ms average, 1230–1849 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public B4Checkin incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
1426 ms on average over the last 24 hours (1230–1849 ms).
Yes, at https://status.b4checkin.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 B4Checkin here at once, the problem is on B4Checkin'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 B4Checkin. 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.