User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Social
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 824 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 1243 ms | 0 |
| Mon 21 | 0 | 0.0 | 400 ms | 0 |
| Mon 23 | 0 | 0.0 | 898 ms | 0 |
| Tue 01 | 0 | 0.0 | 342 ms | 0 |
| Tue 03 | 0 | 0.0 | 1274 ms | 0 |
| Tue 06 | 0 | 0.0 | 1127 ms | 0 |
| Tue 08 | 0 | 0.0 | 674 ms | 0 |
| Tue 10 | 0 | 0.0 | 682 ms | 0 |
| Tue 12 | 0 | 0.0 | 507 ms | 0 |
| Tue 14 | 0 | 0.0 | 523 ms | 0 |
| Tue 16 | 0 | 0.0 | 857 ms | 0 |
| Tue 19 | 0 | 0.0 | 642 ms | 0 |
| Tue 21 | 0 | 0.0 | 895 ms | 0 |
| Tue 23 | 0 | 0.0 | 627 ms | 0 |
| Wed 01 | 0 | 0.0 | 1188 ms | 0 |
| Wed 03 | 0 | 0.0 | 1093 ms | 0 |
| Wed 06 | 0 | 0.0 | 1157 ms | 0 |
| Wed 08 | 0 | 0.0 | 3491 ms | 0 |
| Wed 09 | 0 | 0.0 | 3681 ms | 0 |
| Wed 12 | 0 | 0.0 | 3238 ms | 0 |
| Wed 14 | 0 | 0.0 | — | 1 |
| Wed 16 | 0 | 0.0 | 733 ms | 0 |
| Wed 18 | 0 | 0.0 | 1137 ms | 0 |
| Wed 20 | 0 | 0.0 | 857 ms | 0 |
| Wed 22 | 0 | 0.0 | 707 ms | 0 |
| Thu 00 | 0 | 0.0 | 345 ms | 0 |
| Thu 03 | 0 | 0.0 | 427 ms | 0 |
| Thu 05 | 0 | 0.0 | 533 ms | 0 |
| Thu 07 | 0 | 0.0 | 1533 ms | 0 |
| Thu 09 | 0 | 0.0 | 871 ms | 0 |
| Thu 11 | 0 | 0.0 | 700 ms | 0 |
| Thu 13 | 0 | 0.0 | 1050 ms | 0 |
| Thu 15 | 0 | 0.0 | 708 ms | 0 |
| Thu 17 | 0 | 0.0 | 1283 ms | 0 |
| Thu 19 | 0 | 0.0 | 1043 ms | 0 |
| Thu 21 | 0 | 0.0 | 768 ms | 0 |
| Thu 23 | 0 | 0.0 | 1325 ms | 0 |
| Fri 01 | 0 | 0.0 | 375 ms | 0 |
| Fri 03 | 0 | 0.0 | 699 ms | 0 |
| Fri 05 | 0 | 0.0 | 363 ms | 0 |
| Fri 07 | 0 | 0.0 | 1751 ms | 0 |
| Fri 10 | 0 | 0.0 | 530 ms | 0 |
| Fri 12 | 0 | 0.0 | 691 ms | 0 |
| Fri 14 | 0 | 0.0 | 1465 ms | 0 |
| Fri 16 | 0 | 0.0 | 1177 ms | 0 |
| Fri 17 | 0 | 0.0 | 669 ms | 0 |
| Fri 18 | 0 | 0.0 | 510 ms | 0 |
| Fri 19 | 0 | 0.0 | 824 ms | 0 |
98.73% 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 Mumble 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 Mumble goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Mumble alerts to Slack, Discord or a webhook — free.
Mumble, at mumble.info, is one of the Social services we monitor. Mumble is a free, open source, low latency, high quality voice chat application.
Mumble publishes an official status page at status.mumble.info; when we can read it, its incident level is folded into the status shown here.
Common problems for social services: feeds not loading, posts or messages not sending, and login loops.
Measured uptime from our checks: 98.73% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 822 ms average, 263–1751 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Mumble incident since monitoring began 8 days ago.
From our own checks: 98.73% over 8 days of checks.
822 ms on average over the last 24 hours (263–1751 ms).
Yes, at https://status.mumble.info.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For social services, watch for feeds not loading, posts or messages not sending, and login loops. If many people report Mumble here at once, the problem is on Mumble'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 Mumble. 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.