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 33 min ago. Last stored result reached it in 1599 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 10:00 | 0 | 0.0 | 2330 ms | 0 |
| 12:00 | 0 | 0.0 | 1684 ms | 0 |
| 14:15 | 0 | 0.0 | 2013 ms | 0 |
| 16:00 | 0 | 0.0 | 1528 ms | 0 |
| 18:15 | 0 | 0.0 | 1714 ms | 0 |
| 20:15 | 0 | 0.0 | 1893 ms | 0 |
| 22:15 | 0 | 0.0 | 1888 ms | 0 |
| 00:15 | 0 | 0.0 | 1856 ms | 0 |
| 02:15 | 0 | 0.0 | 1790 ms | 0 |
| 04:30 | 0 | 0.0 | 1646 ms | 0 |
| 06:30 | 0 | 0.0 | 1799 ms | 0 |
| 08:45 | 0 | 0.0 | 1599 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 ibelsa 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 ibelsa goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send ibelsa alerts to Slack, Discord or a webhook — free.
We track ibelsa (ibelsa.com) as part of the Money group. ibelsa ist die cloudbasierte Hotelsoftware für moderne Hotels: PMS, Payment, Anbindungen und persönliche Unterstützung in einer flexiblen Lösung.
ibelsa publishes an official status page at ibelsa-status.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with 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: 1817 ms average, 1528–2330 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 ibelsa incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
1817 ms on average over the last 24 hours (1528–2330 ms).
Yes, at https://ibelsa-status.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 ibelsa here at once, the problem is on ibelsa'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 ibelsa. 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.