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 41 min ago. Last stored result reached it in 852 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 01 | 0 | 0.0 | 1037 ms | 0 |
| Tue 03 | 0 | 0.0 | 994 ms | 0 |
| Tue 05 | 0 | 0.0 | 929 ms | 0 |
| Tue 07 | 0 | 0.0 | 775 ms | 0 |
| Tue 09 | 0 | 0.0 | 1023 ms | 0 |
| Tue 11 | 0 | 0.0 | 834 ms | 0 |
| Tue 13 | 0 | 0.0 | 1000 ms | 0 |
| Tue 15 | 0 | 0.0 | 1010 ms | 0 |
| Tue 18 | 0 | 0.0 | 841 ms | 0 |
| Tue 20 | 0 | 0.0 | 673 ms | 0 |
| Tue 22 | 0 | 0.0 | 885 ms | 0 |
| Wed 00 | 0 | 0.0 | 997 ms | 0 |
| Wed 03 | 0 | 0.0 | 981 ms | 0 |
| Wed 05 | 0 | 0.0 | 1114 ms | 0 |
| Wed 07 | 0 | 0.0 | 1078 ms | 0 |
| Wed 09 | 0 | 0.0 | 1102 ms | 0 |
| Wed 12 | 0 | 0.0 | 1171 ms | 0 |
| Wed 14 | 0 | 0.0 | 1087 ms | 0 |
| Wed 16 | 0 | 0.0 | 1113 ms | 0 |
| Wed 18 | 0 | 0.0 | 866 ms | 0 |
| Wed 20 | 0 | 0.0 | 939 ms | 0 |
| Wed 22 | 0 | 0.0 | 826 ms | 0 |
| Thu 00 | 0 | 0.0 | 1024 ms | 0 |
| Thu 03 | 0 | 0.0 | 685 ms | 0 |
| Thu 05 | 0 | 0.0 | 924 ms | 0 |
| Thu 07 | 0 | 0.0 | 938 ms | 0 |
| Thu 09 | 0 | 0.0 | 849 ms | 0 |
| Thu 11 | 0 | 0.0 | 893 ms | 0 |
| Thu 13 | 0 | 0.0 | 818 ms | 0 |
| Thu 15 | 0 | 0.0 | 893 ms | 0 |
| Thu 17 | 0 | 0.0 | 904 ms | 0 |
| Thu 19 | 0 | 0.0 | 839 ms | 0 |
| Thu 21 | 0 | 0.0 | 1000 ms | 0 |
| Thu 23 | 0 | 0.0 | 999 ms | 0 |
| Fri 01 | 0 | 0.0 | 875 ms | 0 |
| Fri 03 | 0 | 0.0 | 1053 ms | 0 |
| Fri 05 | 0 | 0.0 | 986 ms | 0 |
| Fri 07 | 0 | 0.0 | 522 ms | 0 |
| Fri 09 | 0 | 0.0 | 4737 ms | 0 |
| Fri 11 | 0 | 0.0 | 842 ms | 0 |
| Fri 12 | 0 | 0.0 | 687 ms | 0 |
| Fri 14 | 0 | 0.0 | 1057 ms | 0 |
| Fri 16 | 0 | 0.0 | 850 ms | 0 |
| Fri 18 | 0 | 0.0 | 858 ms | 0 |
| Fri 20 | 0 | 0.0 | 883 ms | 0 |
| Fri 21 | 0 | 0.0 | 713 ms | 0 |
| Fri 23 | 0 | 0.0 | 829 ms | 0 |
| Sat 01 | 0 | 0.0 | 852 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 etg24 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 etg24 goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send etg24 alerts to Slack, Discord or a webhook — free.
etg24, at etg24.de, is one of the Cloud & developer services we monitor. etg24 | Ihr Immobilienverwaltungs-Portal für: ✓ Verwalter ✓ Eigentümer und Mieter ✓ Dienstleister ► Jetzt informieren.
etg24 publishes an official status page at status.etg24.de; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 1074 ms average, 198–4737 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public etg24 incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
1074 ms on average over the last 24 hours (198–4737 ms).
Yes, at https://status.etg24.de.
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 etg24 here at once, the problem is on etg24'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 etg24. 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.