Last updated: May 9, 2026
If you got here, it's probably one of three things. Either the audio in a Space you're listening to keeps cutting in and out, or you tapped a Space and the bottom-of-screen player just sits there spinning, or you were added as a speaker and your microphone is doing absolutely nothing. They look like the same problem — "Spaces is broken" — but the underlying causes are different, and so is the fix for each.
I want to skip the generic "restart your phone" pep talk and get into what's actually breaking Spaces in 2026. Two things have changed in the last year that matter: X moved more of the Spaces audio path to a newer WebRTC pipeline (which broke a lot of older Chrome installs), and the desktop web client became noticeably more fragile than the mobile app. Both of those drive most of what people are seeing right now.
Audio cuts out after a few minutes on desktop → Almost always the Chrome WebRTC bug. Jump to fix #2.
Space won't open at all — just spins → Cache or app version. Fix #3.
You can hear but the room is silent for everyone else → The host's stream dropped, not yours. Wait or rejoin.
Promoted to speaker, mic does nothing → Permission re-prompt failed. Fix #4.
"Could not fetch Space" error → The Space ended, was deleted, or you're region-blocked via VPN. Fix #5.
Spaces tab missing entirely → Account flag or A/B rollout. Fix #6.
X doesn't publish a status page for Spaces specifically, which makes outages weirdly hard to confirm. The fastest signal is to search "X Spaces down" or "Twitter Spaces down" on X itself — if there's a real outage, the complaints start trending within ten minutes. Downdetector picks them up shortly after. If you see a spike, close the app and check back in 30–60 minutes; nothing on your end will help.
Spaces outages tend to be partial: hosting works but joining fails, or vice versa. So if you're trying to host and it's broken, it doesn't necessarily mean listeners can't hear you — ask someone to check.
This is the single most common Spaces complaint in 2026, and it's frustrating because it doesn't look like a bug at first — the audio just gradually fades or starts skipping after you've been listening for 5–15 minutes. What's happening is that Chrome's autoplay/audio-context handling clashes with how X's web client renews the WebRTC audio stream. The session technically stays alive, but the audio buffer underruns and never recovers.
What actually fixes it:
chrome://settings/content/sound and make sure x.com is allowed to play sound. Then go to chrome://flags and set Hardware Media Key Handling to Disabled, restart Chrome, and try the Space again.You tap the purple bubble at the top of someone's profile, or the live indicator on a tweet, and the player slides up and just sits there. Two real causes:
X ships Spaces backend changes faster than they ship full app updates, so a version of the X app that's even a few weeks old can hit endpoints that no longer exist. Check the App Store or Play Store and update if there's anything available. This is especially true if you have auto-update turned off.
The X app caches recent Space metadata locally, and if a Space ended unexpectedly while you were listening, that record can get stuck and block new ones from loading. To clear it:
This one is sneaky. If you joined a Space as a listener and the host promoted you to speaker mid-conversation, X sometimes fails to re-trigger the microphone permission prompt. Your mic icon appears, you tap to unmute, and nobody can hear you.
This message means the X app could not retrieve the Space's metadata from the server. It's not a network error in the usual sense — it's a specific server response. Three things cause it:
If you open the X app and there's no Spaces icon at the bottom (or no purple ring around live profiles), it's one of two things: an A/B test rollout, or a quiet account flag.
X periodically rolls out UI changes to subsets of users, and Spaces visibility has been part of several recent tests. The faster check: open x.com in a desktop browser. If Spaces shows up there, your account is fine and the mobile app is just on a different rollout track — updating the app or signing out and back in usually pulls you onto the standard UI.
If Spaces is missing on web too, your account may have been flagged for spam-adjacent activity (mass-following, rapid posting). Spaces hosting requires the account to be in good standing. Check your X account status under Settings → Your account → Account information for any restrictions.
Different problem from full dropouts. If voices sound like they're underwater, robotic, or skipping syllables, it's a bandwidth or jitter issue. Spaces needs about 1.5 Mbps of stable bandwidth, but more importantly, it needs consistent latency. A connection that averages 50 Mbps but spikes to 400ms ping every few seconds will sound worse than a steady 5 Mbps line.
Q: Why does the audio in X Spaces keep cutting out after a few minutes?
A: On desktop, the most common cause in 2026 is a Chrome-specific streaming bug that drops the WebRTC audio session after a few minutes idle. Switching to Firefox usually resolves it instantly. On mobile, it's almost always a bandwidth issue — Spaces needs roughly 1.5 Mbps of stable upload/download, and Wi-Fi networks that fluctuate between 5 GHz and 2.4 GHz can break the stream. Try mobile data as a test; if audio holds, your Wi-Fi is the issue.
Q: I tap the Space and nothing happens — it won't open at all. Why?
A: Three causes account for almost all "Space won't open" reports: an outdated X app (Spaces gets backend changes pushed faster than the rest of the app, so older versions silently break), a corrupted local cache (force-stop the app and clear it from app info), or a VPN that routes you through a region X has flagged. Disable the VPN, update the app, then try again.
Q: Why can't I speak in a Space when the host adds me as a co-host or speaker?
A: X needs explicit microphone permission, and there are actually two layers: the OS-level permission for the X app itself, and (on iPhone) a separate setting under Settings > X > Microphone that can revert after iOS updates. If you joined as a listener and were promoted later, X sometimes fails to re-prompt for mic access — leave the Space and rejoin once permissions are granted.
Q: Is X Spaces actually down right now, or is it just me?
A: Check Downdetector or search "X Spaces down" on X itself — outage reports usually appear there within minutes. X doesn't publish a public status page for Spaces, so user reports are the fastest signal. If reports are spiking, wait 20–60 minutes; Spaces outages are typically resolved server-side without any action from you.
Q: Why does X Spaces work in the app but not on the desktop website?
A: The web client uses your browser's WebRTC stack, which has more failure modes than the native app. Common culprits: Chrome's autoplay policy blocking the audio context, an extension like uBlock Origin filtering a Spaces endpoint, or a missing site permission for the microphone in the address-bar lock icon. Open x.com in a private window with no extensions to confirm — if it works there, walk back through your extensions and site permissions.
If none of the above worked, the next thing to check is whether your specific Space is the problem rather than your setup. Try joining any other live Space (the Spaces tab usually has a few running). If those work and only one specific Space doesn't, the issue is on the host's end — you can't fix it from your side. If nothing works for you but Spaces is up for everyone else, file a report through X's help center at help.x.com referencing your account and the Space ID, and check back in 24–48 hours.