twitch.com — PING network test and history

Compare round-trip latency and packet loss from different locations.

Time -Loss -Failed

queryAaaa ENODATA twitch.com

Time -Loss -Failed

queryAaaa ENODATA twitch.com

Time -Loss -Failed

queryAaaa ENODATA twitch.com

Time -Loss -Failed

queryAaaa ENODATA twitch.com

Time -Loss -Failed

queryAaaa ENODATA twitch.com

Time -Loss -Failed

queryAaaa ENODATA twitch.com

Time -Loss -Failed

queryAaaa ENODATA twitch.com

Time -Loss -Failed

queryAaaa ENODATA twitch.com

Time -Loss -Failed

queryAaaa ENODATA twitch.com

Recent queries

Latest 20 per type

Compare round-trip latency and packet loss from different locations.

History opens saved results. Select “Run again” to start a new test.

Inspect route paths, hop addresses and response times from different locations.

Open Traceroute

History opens saved results. Select “Run again” to start a new test.

Compare DNS records, resolvers and response times across locations.

History opens saved results. Select “Run again” to start a new test.

Combine route tracing with repeated probes to inspect hop latency and loss. Intermediate hop rate limiting does not establish destination packet loss.

History opens saved results. Select “Run again” to start a new test.

Inspect HTTP status, response headers and request timings from different locations.

History opens saved results. Select “Run again” to start a new test.