Skip to main content
sus.botdocs
  • SEO
  • AI
  • QA
  • Privacy
  • Accessibility
  • Security
  1. Docs
  2. QA
  3. Uptime and response time
  4. The site was down for several checks in a row

QA finding

The site was down for several checks in a row

QA Error Severity: High

Part of the audit Uptime and response time. Finding id: qa.outagesFromChecks.

What it costs you

Visitors and search engines got an error for that whole period.

What to do

Look at the server and hosting logs for that period and find what stopped answering.

What it checks

  • Outage with start and end time

How to fix it

Find the cause of the outage

  1. Check the hosting status page and the server logs between [started] and [last failed].
  2. If the same time of day keeps appearing, look for a scheduled job, a backup or a deployment at that time.

How to check: The next checks answer normally, and no new outage appears here.

A real case

Researchers at Uptime Institute found that over 60% of the outages in their 2022 survey caused at least $100,000 in total losses, up from 39% in 2019, and 15% cost more than $1 million.

Source: Uptime Institute, 2022 Outage Analysis, 8 June 2022

Thresholds

Thresholds for The site was down for several checks in a row
NameDefaultMeaning
min_failed_checks2How many failed checks in a row make an outage. One failed check alone is often a network blip.
  • All audits
  • About sus.bot
  • Open the app
  • Contact support