GEARCHECK LABConnect two tabs or devices you control to test a real browser-to-browser WebRTC data channel. GearCheck Lab provides temporary signaling; the other browser is the measurement endpoint.
READY — choose an action below
No measurement yet.
Pairing exchanges connection descriptions through GearCheck Lab. After connection, small ping messages travel over the WebRTC data channel to the other browser and are echoed back. The displayed round-trip values include both browsers and their network path. Successful ping count and reply gaps describe this sample, not raw packet loss. ICE candidate-pair RTT is displayed separately when the browser reports it. No camera or microphone is requested. Two tabs on one computer test only a local path and must not be interpreted as an internet test.
A public Google STUN service is contacted after creating or joining a session to discover connection candidates; it can see your network address. The other peer can learn network addresses through WebRTC. Share the temporary code only with a device you control. Some networks require a TURN relay, which is not provided, so connection may fail. Hiding a page stops its active sample while leaving the peer available. Signaling and connection access expire after three minutes; connection descriptions are kept only in server memory. No RTP audio/video packet-loss or jitter score is invented for this data-channel test.
Device previews, recordings, selected files and report notes stay in your browser. Downloaded files remain on your device. The call check sends small HTTP probes to GearCheck Lab. The WebRTC test exchanges temporary connection descriptions through our server and contacts the disclosed STUN service only after you create or join a session. Ordinary page requests and usage measurement are described in our privacy policy.