Website Name:
Response Time:
HTTP Status Codes:
Last Down:
Local Node:
IMPORTANT: Some website is uptime some local only.

Website status / 24h

100% UpTime
0% DownTime Website Status History status history chart

The above graph displays service status activity for over the last 10 automatic checks. The blue bar displays the response time, which is better when smaller. If no bar is displayed for a specific time it means that the service was down and the site was offline.

Service Status History
Status Node Date Time DNS Time Response Time HTTP Code Time Ago
No items were found
* Times displayed are UTC/GMT

We have tried pinging website using our server and the website returned the above results. If is down for us too there is nothing you can do except waiting. Probably the server is overloaded, down or unreachable because of a network problem, outage or a website maintenance is in progress..

Why only response time is measured?

We want to skip all the stuff that represents real (dns, ping, traceroute, download speed) and actually measure the only real thing (how fast can my web page be loaded).

  • DNS Time This will be slow only for the first time user or search engine visit your site.
  • Ping Not every web server have ICMP enabled. More importantly no one is using Ping to browse your site!
  • Traceroute Traceroute differs from every single PC and keep changing, why would this ever make sense?
  • Download Speed A large homepage may have a good download speed, but still take long time to load.
  • Response Time (waiting + receiving) The only thing really matters to end users and search engines. Some website has Responsed but users can't view or read content,Downtimechecker has defined it is downtime does not actually host anything. All incoming requests are redirected to can not be resolved to any public IP address.