User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
superchat.de · 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 16 min ago. Last stored result reached it in 555 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 573 ms | 0 |
| Mon 15 | 0 | 0.0 | 453 ms | 0 |
| Mon 17 | 0 | 0.0 | 696 ms | 0 |
| Mon 19 | 0 | 0.0 | 705 ms | 0 |
| Mon 21 | 0 | 0.0 | 402 ms | 0 |
| Mon 23 | 0 | 0.0 | 481 ms | 0 |
| Tue 02 | 0 | 0.0 | 742 ms | 0 |
| Tue 04 | 0 | 0.0 | 378 ms | 0 |
| Tue 05 | 0 | 0.0 | 535 ms | 0 |
| Tue 07 | 0 | 0.0 | 731 ms | 0 |
| Tue 09 | 0 | 0.0 | 521 ms | 0 |
| Tue 12 | 0 | 0.0 | 610 ms | 0 |
| Tue 14 | 0 | 0.0 | 458 ms | 0 |
| Tue 16 | 0 | 0.0 | 685 ms | 0 |
| Tue 18 | 0 | 0.0 | 694 ms | 0 |
| Tue 21 | 0 | 0.0 | 450 ms | 0 |
| Tue 23 | 0 | 0.0 | 559 ms | 0 |
| Wed 01 | 0 | 0.0 | 769 ms | 0 |
| Wed 03 | 0 | 0.0 | 392 ms | 0 |
| Wed 06 | 0 | 0.0 | 557 ms | 0 |
| Wed 08 | 0 | 0.0 | 480 ms | 0 |
| Wed 10 | 0 | 0.0 | 510 ms | 0 |
| Wed 12 | 0 | 0.0 | 392 ms | 0 |
| Wed 14 | 0 | 0.0 | 409 ms | 0 |
| Wed 16 | 0 | 0.0 | 538 ms | 0 |
| Wed 19 | 0 | 0.0 | 559 ms | 0 |
| Wed 21 | 0 | 0.0 | 515 ms | 0 |
| Wed 23 | 0 | 0.0 | 608 ms | 0 |
| Thu 01 | 0 | 0.0 | 586 ms | 0 |
| Thu 03 | 0 | 0.0 | 659 ms | 0 |
| Thu 05 | 0 | 0.0 | 660 ms | 0 |
| Thu 07 | 0 | 0.0 | 658 ms | 0 |
| Thu 09 | 0 | 0.0 | 364 ms | 0 |
| Thu 12 | 0 | 0.0 | 420 ms | 0 |
| Thu 14 | 0 | 0.0 | 493 ms | 0 |
| Thu 16 | 0 | 0.0 | 619 ms | 0 |
| Thu 18 | 0 | 0.0 | 672 ms | 0 |
| Thu 20 | 0 | 0.0 | 394 ms | 0 |
| Thu 22 | 0 | 0.0 | 656 ms | 0 |
| Fri 00 | 0 | 0.0 | 824 ms | 0 |
| Fri 02 | 0 | 0.0 | 536 ms | 0 |
| Fri 04 | 0 | 0.0 | 533 ms | 0 |
| Fri 06 | 0 | 0.0 | 520 ms | 0 |
| Fri 08 | 0 | 0.0 | 442 ms | 0 |
| Fri 11 | 0 | 0.0 | 458 ms | 0 |
| Fri 13 | 0 | 0.0 | 390 ms | 0 |
| Fri 15 | 0 | 0.0 | 479 ms | 0 |
| Fri 17 | 0 | 0.0 | 555 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Superchat 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 Superchat goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Superchat alerts to Slack, Discord or a webhook — free.
Superchat, at superchat.de, is one of the Cloud & developer services we monitor. Machen Sie die Kundenkommunikation zu Ihrer Priorität. Schaffen Sie echte und langfristige Kundenbeziehungen mit der Messaging Lösung von Superchat.
Superchat publishes an official status page at status.superchat.de; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 548 ms average, 390–824 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 Superchat incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
548 ms on average over the last 24 hours (390–824 ms).
Yes, at https://status.superchat.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 Superchat here at once, the problem is on Superchat'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 Superchat. 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.