Incident management for client site outages

After an outage the client asks two questions: what happened, and will it happen again. You need the facts to answer.

"The site was down" is not an explanation.

An alert email tells you a site went down. The next morning you need more: when it started, from where it failed, what the server answered, when it came back.

Without a record, the explanation for the client is a guess.

Every outage is written down as it happens.

  1. Timeline

    Start, end and duration, the regions that saw it down, and the checks made during the outage.

  2. Cause

    We turn the error into plain words: DNS, connection refused, timeout, certificate, redirect loop, or the HTTP code, with the first lines of the answer.

  3. Notes

    The team adds updates and post-mortems to the outage. Each note can stay internal or go on the status page and to subscribers.

Want to try it on a real site? The 30-day trial needs no credit card.

Start free trial

Frequently asked questions

Do maintenance windows create outages?

No. During a maintenance window we do not check the site, and an outage in progress closes with the reason "maintenance".

How long do you keep outages?

3 months on Free, 12 months on Solo, Essentials and Pro, 24 months on Complete.

Try it on your clients' sites.

Connect your first sites today and see what SitePing finds on them.

  • Every Complete feature except backups
  • Up to 10 sites
  • No credit card needed to start
  • At the end you choose a plan or move to Free, and nothing is charged
Start the 30-day trial

Already have an account? Log in. Prefer to look at one site first? Free read-only audit.