Is there any issue with your server?
# ask-ai
m
Is there any issue with your server?
t
Thanks for reaching out, ERIC. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
Thanks for checking — I can help with that. There are no reported, system-wide outages right now. LiveKit is designed for high availability (live migrations and fault tolerance) and we make commercially reasonable efforts to keep services available 24/7, aside from planned maintenance or events beyond our control. For architecture details you can review the blog on our distributed mesh network: https://blog.livekit.io/scaling-webrtc-with-distributed-mesh/ To help me diagnose your issue faster, can you tell me: • What exactly you’re seeing (error messages, failed connections, dropped calls)? • When it started and whether it’s intermittent or constant. • Which region or data center you’re using, if known. • Any room IDs, session IDs, or client logs you can share (redact any sensitive keys). If you prefer, I can also check your affected room/session if you provide a room ID and timestamp. Sources: Terms of Service | LiveKit | How We Built a Globally Distributed WebRTC Mesh Network | How We Built a Globally Distributed WebRTC Mesh Network | How We Built a Globally Distributed WebRTC Mesh Network
m
I’m currently using React Native, but the speaker audio isn’t playing. How can I fix this?
t
Thanks — I’m sorry you’re seeing speaker audio not play in your React Native app. I can help troubleshoot this, but I need a few details to narrow down the cause and give targeted steps. Could you share the following? • Which platform(s) are affected: iOS, Android, or both — and OS versions. • Your React Native version and the LiveKit React Native SDK version. • Exact behavior: no audio at all, audio only through the earpiece, very low volume, or intermittent drops. • Whether the issue happens on all devices or just specific models, and whether Bluetooth/headphones are connected when it occurs. • Any error messages or logs (console, ADB logcat for Android, Xcode logs for iOS) when joining a room or subscribing to a track. • Confirmation that microphone/speaker permissions are granted and that local audio capture (
getUserMedia()
/ local track) succeeds. • Whether you see subscription events in the SDK (e.g.,
TrackSubscribed
/ participant/track events) for remote audio tracks. • The code snippet where you initialize LiveKit, subscribe to tracks, and attach audio to your UI (redact any keys or tokens). • If iOS: do you set or modify
AVAudioSession
category/mode anywhere? • If Android: do you change audio routing or audio focus, and what device make/model is affected? • Optionally: a Room/Participant/Track ID and approximate timestamp when the issue happened (redact sensitive tokens) so I can correlate logs. Things you can quickly check while you gather this: • Confirm app has microphone and speaker permissions and that the OS is not muting the app or routing audio to a disconnected Bluetooth device. • Verify remote audio tracks are subscribed to (your SDK events) and that you are attaching the audio track to a player/output rather than only rendering a UI view. • On iOS, ensure
AVAudioSession
is configured to allow speaker output (apps sometimes set category/mode that routes audio to earpiece). • On Android, check audio focus and routing settings and try toggling speakerphone to see if audio changes. Share the details above and any logs or code snippets you can. Once I have that, I’ll provide targeted troubleshooting steps and code-level fixes you can try. Sources: LiveKit coming to React Native! | client-sdk-react-native | livekit/livekit_composite | DeepWiki