User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Money
Is ibelsa down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → ibelsa.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 54 min ago. Last stored result reached it in 2709 ms.
Official status
All clear
All systems operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 2064 ms | 0 |
| Mon 21 | 0 | 0.0 | 1700 ms | 0 |
| Mon 23 | 0 | 0.0 | 2572 ms | 0 |
| Tue 01 | 0 | 0.0 | 1856 ms | 0 |
| Tue 03 | 0 | 0.0 | 1897 ms | 0 |
| Tue 06 | 0 | 0.0 | 2217 ms | 0 |
| Tue 08 | 0 | 0.0 | 1985 ms | 0 |
| Tue 10 | 0 | 0.0 | 1712 ms | 0 |
| Tue 12 | 0 | 0.0 | 1534 ms | 0 |
| Tue 14 | 0 | 0.0 | 1870 ms | 0 |
| Tue 16 | 0 | 0.0 | 1658 ms | 0 |
| Tue 19 | 0 | 0.0 | 1872 ms | 0 |
| Tue 21 | 0 | 0.0 | 2398 ms | 0 |
| Tue 23 | 0 | 0.0 | 1915 ms | 0 |
| Wed 01 | 0 | 0.0 | 1980 ms | 0 |
| Wed 04 | 0 | 0.0 | 1717 ms | 0 |
| Wed 06 | 0 | 0.0 | 1884 ms | 0 |
| Wed 08 | 0 | 0.0 | 1499 ms | 0 |
| Wed 10 | 0 | 0.0 | 2072 ms | 0 |
| Wed 13 | 0 | 0.0 | 2096 ms | 0 |
| Wed 15 | 0 | 0.0 | 2020 ms | 0 |
| Wed 17 | 0 | 0.0 | 2112 ms | 0 |
| Wed 19 | 0 | 0.0 | 1452 ms | 0 |
| Wed 21 | 0 | 0.0 | 2251 ms | 0 |
| Wed 23 | 0 | 0.0 | 2321 ms | 0 |
| Thu 01 | 0 | 0.0 | 1584 ms | 0 |
| Thu 04 | 0 | 0.0 | 2119 ms | 0 |
| Thu 06 | 0 | 0.0 | 1740 ms | 0 |
| Thu 08 | 0 | 0.0 | 2031 ms | 0 |
| Thu 10 | 0 | 0.0 | 2330 ms | 0 |
| Thu 12 | 0 | 0.0 | 1684 ms | 0 |
| Thu 14 | 0 | 0.0 | 2013 ms | 0 |
| Thu 16 | 0 | 0.0 | 1528 ms | 0 |
| Thu 18 | 0 | 0.0 | 1714 ms | 0 |
| Thu 20 | 0 | 0.0 | 1893 ms | 0 |
| Thu 22 | 0 | 0.0 | 1888 ms | 0 |
| Fri 00 | 0 | 0.0 | 1856 ms | 0 |
| Fri 02 | 0 | 0.0 | 1790 ms | 0 |
| Fri 04 | 0 | 0.0 | 1646 ms | 0 |
| Fri 06 | 0 | 0.0 | 1799 ms | 0 |
| Fri 08 | 0 | 0.0 | 1599 ms | 0 |
| Fri 10 | 0 | 0.0 | 1699 ms | 0 |
| Fri 12 | 0 | 0.0 | 2242 ms | 0 |
| Fri 14 | 0 | 0.0 | 1724 ms | 0 |
| Fri 17 | 0 | 0.0 | 1961 ms | 0 |
| Fri 18 | 0 | 0.0 | 2107 ms | 0 |
| Fri 19 | 0 | 0.0 | 1646 ms | 0 |
| Fri 21 | 0 | 0.0 | 2709 ms | 0 |
Reliability
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.
Embed this status: free live ibelsa badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for ibelsa yet. Outages of 10 minutes or more get their own page here.
Having trouble with ibelsa?
One report per service every 10 minutes from this network. No account.
Follow ibelsa
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.
About ibelsa
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: 1867 ms average, 1245–2709 ms range across 16 successful checks.
Questions
Is ibelsa down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was ibelsa last down?
We have not recorded a public ibelsa incident since monitoring began 7 days ago.
What is ibelsa's uptime?
From our own checks: 100% over 7 days of checks.
How fast does ibelsa respond?
1867 ms on average over the last 24 hours (1245–2709 ms).
Does ibelsa have an official status page?
Yes, at https://ibelsa-status.com.
ibelsa not working for me but the status is fine. What now?
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.