PulseTrace
Start free
All free tools
Free tool

Is it down? Check whether a website is up, with response time and redirect chain

Enter a URL and PulseTrace requests it from outside your network, following redirects, and reports the status code and where the time went. If it answers here but not for you, the problem is between you and the site.

Monitor this continuously

Check this URL every minute from 12 regions and get told — in Slack, PagerDuty or email — when it goes down and when it comes back.

Start free HTTP(S) monitor

How to read the result

  1. 1Up means the final response was a 2xx or 3xx. A 4xx or 5xx is reported as down with the status; a connection failure or timeout with the reason.
  2. 2The timing split shows where the time went: DNS resolution, then the request until the first byte, then reading up to the first 64 KB of body.
  3. 3The redirect chain is shown hop by hop. Two or more redirects on a landing URL are a common, easily fixed performance cost.
  4. 4This is one request from one location. A real check runs on a schedule from many regions and needs consecutive failures before it alerts.

Questions

It says up but I can't reach it.
Then the site is reachable from the internet and the problem is closer to you: your DNS resolver, a corporate proxy, a regional CDN edge, or a block on your IP. Try the DNS lookup tool with a different resolver.
It says down but the site loads for me.
The site may be blocking automated clients (a WAF returning 403), or you are seeing a cached copy from your browser or CDN. The status code shown is what the origin returned to a plain request.
Where is the check made from?
From PulseTrace's server. A monitor uses up to 12 regions and requires failures from more than one before opening an incident, which is what stops one bad network path from paging you.

Other free tools

SSL certificate checkerSecurity headers graderDNS lookupSLA & uptime calculatorCron expression builderUptime monitoring →