# Livekit cloud connectivity test

**URL:** <https://community.livekit.io/t/livekit-cloud-connectivity-test/1136>\
**Category:** Getting Started\
**Created:** [May 15, 2026, 10:13am UTC](https://community.livekit.io/t/livekit-cloud-connectivity-test/1136 "2026-05-15T10:13:31Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![RabbaniF22](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/rabbanif22/32/1002_2.png) [@RabbaniF22](https://community.livekit.io/u/RabbaniF22)\
**Post date:** [May 15, 2026, 10:13am UTC](https://community.livekit.io/t/livekit-cloud-connectivity-test/1136/1 "2026-05-15T10:13:31Z")

</div>

I have built a video call kind of application using the LiveKit cloud, but what is happening now is that some users are entering the video call, but because of their network connectivity, it is poor or bad. The connection is getting dropped, like the agent is getting disconnected or the internet is very bad. So, I need a test before entering the room or the call itself to verify if all the connections are stable or not. What infrastructure do we have to test this? Is there already a library that I can use, or do you have to just use the FastAPI or a network speed test API that is available on the internet? Just check the internet connection speed with [fast.com](http://fast.com) or any free api that is available?

---

<div class="post-metadata">

**Author:** ![RabbaniF22](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/rabbanif22/32/1002_2.png) [@RabbaniF22](https://community.livekit.io/u/RabbaniF22)\
**Post date:** [May 15, 2026, 10:13am UTC](https://community.livekit.io/t/livekit-cloud-connectivity-test/1136/2 "2026-05-15T10:13:59Z")

</div>

@Muhammad_Usman_Bashir @CWilson

---

<div class="post-metadata">

**Author:** ![darryncampbell](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/darryncampbell/32/20_2.png) [@darryncampbell](https://community.livekit.io/u/darryncampbell)\
**Post date:** [May 15, 2026, 10:40am UTC](https://community.livekit.io/t/livekit-cloud-connectivity-test/1136/3 "2026-05-15T10:40:05Z")

</div>

LiveKit should be resilient to poor network conditions, and we have some advanced features to deliver video to users appropriate to their bandwidth: [Codecs and more | LiveKit Documentation](https://docs.livekit.io/transport/media/advanced/#video-simulcast)

Having said that however, we are still constrained by the actual network conditions of the user. If you chose to, you could not allow video sharing if you determine a user’s network connection is too poor to permit it… There is nothing native in LiveKit to do this, but if it were me, I would use client-side libraries such as Android’s [TelephonyManager getDataNetworkType()](https://developer.android.com/reference/android/telephony/TelephonyManager#getDataNetworkType()) to achieve this.

---

<div class="post-metadata">

**Author:** ![RabbaniF22](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/rabbanif22/32/1002_2.png) [@RabbaniF22](https://community.livekit.io/u/RabbaniF22)\
**Post date:** [May 15, 2026, 10:47am UTC](https://community.livekit.io/t/livekit-cloud-connectivity-test/1136/4 "2026-05-15T10:47:17Z")

</div>

i found this [ConnectionCheck | LiveKit JS Client SDK - v2.19.0](https://docs.livekit.io/reference/client-sdk-js/classes/ConnectionCheck.html)  
will this be any helpful to check the user connectivity strength with my livekit cloud?

---

<div class="post-metadata">

**Author:** ![Muhammad\_Usman\_Bashir](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/muhammad_usman_bashir/32/1149_2.png) [@Muhammad\_Usman\_Bashir](https://community.livekit.io/u/Muhammad_Usman_Bashir)\
**Post date:** [May 15, 2026, 6:39pm UTC](https://community.livekit.io/t/livekit-cloud-connectivity-test/1136/5 "2026-05-15T18:39:01Z")

</div>

@RabbaniF22, yes, `ConnectionCheck` is the right tool. It’s the native LiveKit pre-call diagnostic suite. You pass it your project URL and a token, and it runs the checks that matter for an actual call: `WebSocket` to the signal server, `WebRTC` capability, TURN reachability, reconnect, publish audio, publish video, protocol fallback, and Cloud region detection. Far more useful than a generic [fast.com](http://fast.com) speed test, because it exercises the same path the call will use.

Verified on main in `client-sdk-js/src/connectionHelper/ConnectionCheck.ts`:

```auto
  // livekit-client v2.19.0+
  import { ConnectionCheck } from 'livekit-client';

  const checker = new ConnectionCheck(url, token);
  await checker.checkWebsocket();
  await checker.checkWebRTC();
  await checker.checkTURN();
  await checker.checkPublishAudio();
  await checker.checkPublishVideo();
  await checker.checkReconnect();
  console.log(checker.getResults(), checker.isSuccess());

```

Gate the join button on `isSuccess()` or on specific failing checks for a clean pre-call flow.

---

<div class="post-metadata">

**Author:** ![CWilson](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/cwilson/32/135_2.png) [@CWilson](https://community.livekit.io/u/CWilson)\
**Post date:** [May 18, 2026, 4:17pm UTC](https://community.livekit.io/t/livekit-cloud-connectivity-test/1136/6 "2026-05-18T16:17:08Z")

</div>

@RabbaniF22 that is a helpful test. To get deeper diagnostics if they are using Chrome browser is to open a tab to `chrome://webrtc-internals` and then in another tab reproduce the issue. That should have details about exactly what is happening during the WebRTC session from that browser.