Ping your website.
Around the world.

Pingmine sends an HTTP request from each of the 15 cities and times how long it takes to receive response headers. Each location waits up to five seconds. Redirects are reported without being followed.

A global test shows how your website responds from different networks and regions. Compare the city results to spot an unusually slow location, a timeout, or an HTTP error. This can help you investigate hosting performance, routing differences, and CDN behavior.

Each result is a snapshot from a Cloudflare probe. It does not represent every visitor or network in that city. Run a few tests to check whether a difference persists.

Yes. There are 1,000 complete tests available each day, shared by everyone. Each test checks all 15 cities. To keep access fair, each network address can run up to 30 tests per day. Both limits reset at 00:00 UTC. Security verification and short request limits help protect this shared allowance.

Enter a public website domain or an HTTP or HTTPS URL using its standard port. We use HTTPS when you enter a domain without a protocol. Raw IP addresses, private networks, login credentials, and custom ports are not supported.

Pingmine measures the time until an HTTP response’s headers arrive. It does not use ICMP ping, download the full page, execute JavaScript on the target, or measure Core Web Vitals.

Response time is shown in milliseconds: a lower number means that probe received response headers sooner. The bars compare timings within the current test; the shortest measured response is marked Fastest. Click Location, Response time, or HTTP status to sort the results, and click again to reverse the order.

The color guide uses green below 200 ms, yellow for 200–499 ms, and red for 500 ms or more. These are Pingmine’s display bands, rather than a universal speed standard. There is no single ideal response time for every website. Compare similar URLs and repeat the test before drawing conclusions. A cached CDN response can be much quicker than a request that reaches your origin server.

Yes, as one diagnostic signal. Test the same public URL before and after a hosting, DNS, or CDN change, then compare repeated measurements from the same cities. Keep the protocol and path consistent. Caching, connection reuse, and server load can change the result, so one test alone does not establish that a provider is faster.

Network conditions, server load, DNS, connection reuse, and CDN caching all affect response times. Treat each test as a snapshot. Repeat a test to understand a pattern rather than relying on a single reading.

Timing and HTTP status describe different things. A server can return a 404 Not found or 403 Forbidden response very quickly. A checkmark means a successful 2xx HTTP response; a redirect is shown separately, and errors include a status description. Always read the status alongside the timing.

Each location waits up to five seconds. A timeout means no response completed within that window. A 403 or 429 response may mean the website blocks automated requests or limits traffic; it does not necessarily mean it is unavailable to people.

Public test URLs and results are not saved to our application database. Salted hashes of network addresses enforce daily and short-term request limits. Verification-token hashes expire after five minutes to prevent reuse. Expired security records are removed as new requests arrive. Cloudflare Turnstile checks browser signals for abuse prevention, Web Analytics measures page performance, and Cloudflare may process operational logs for security and reliability. Avoid submitting confidential URLs or secret query parameters.