Is ClubHouse Down? Live status & outage reports

Service info and troubleshooting

App crashes on launch

If Clubhouse closes immediately after opening, start with the basics: force-quit the app, then relaunch. If that doesn't help, check whether your iOS or Android version meets the minimum requirements — the app regularly drops support for older OS versions. Clearing the cache (Android: Settings → Apps → Clubhouse → Clear Cache) often fixes silent crashes.

No audio in a room

You joined a room but hear nothing. First, check that your device volume isn't muted and that Clubhouse has microphone and audio permissions in your phone settings. If other speakers are visible but silent, leave the room and rejoin — audio sync issues are common after unstable connections. Also try switching from Wi-Fi to mobile data or vice versa to rule out packet loss on your current network.

Microphone not working on stage

• Make sure no other app (calls, voice recorder) is holding the microphone in the background
• Revoke and re-grant microphone permission in your device settings
• Restart the app — the mic sometimes locks up after switching between rooms quickly
• If on iOS, check Screen Time restrictions that may block mic access for third-party apps

Notifications not arriving

Clubhouse relies heavily on push notifications for room alerts and invites. Go to your device notification settings and confirm that notifications for the app are fully enabled — banners, sounds, and badge counts. On Android, also check battery optimization: if the app is in the restricted list, the system kills it before notifications arrive. Re-enabling background activity usually solves this immediately.

Slow loading of room feed

The main hallway sometimes freezes or shows a spinner indefinitely. This almost always points to a weak connection rather than a server issue. Run a quick speed test — anything below 5 Mbps can cause feed loading failures. If speeds are fine, log out and back in to refresh your session token. Persistent slowness on strong connections may mean the CDN node serving your region is under load; waiting 5–10 minutes typically resolves it.

Account login fails

If the SMS verification code isn't arriving, wait 60 seconds before requesting a new one — duplicate requests often cancel each other out. Check that your phone number is entered with the correct country code. If the code arrives but login still fails, try uninstalling and reinstalling the app: corrupted local auth data can block the login flow entirely.