Synthetic Monitoring

Simulate visitor interaction with your site to monitor the end user experience.

View Product Info


Simulate visitor interaction

Identify bottlenecks and speed up your website.

Learn More

Real User Monitoring

Enhance your site performance with data from actual site visitors

View Product Info


Real user insights in real time

Know how your site or web app is performing with real user insights

Learn More

Infrastructure Monitoring Powered by SolarWinds AppOptics

Instant visibility into servers, virtual hosts, and containerized environments

View Infrastructure Monitoring Info
Comprehensive set of turnkey infrastructure integrations

Including dozens of AWS and Azure services, container orchestrations like Docker and Kubernetes, and more 

Learn More

Application Performance Monitoring Powered by SolarWinds AppOptics

Comprehensive, full-stack visibility, and troubleshooting

View Application Performance Monitoring Info
Complete visibility into application issues

Pinpoint the root cause down to a poor-performing line of code

Learn More

Log Management and Analytics Powered by SolarWinds Loggly

Integrated, cost-effective, hosted, and scalable full-stack, multi-source log management

 View Log Management and Analytics Info
Collect, search, and analyze log data

Quickly jump into the relevant logs to accelerate troubleshooting

Learn More

Optimize your Pingdom alerts

Pingdom was made to directly alert our users of any downtime that might occur on servers and websites. But in many cases it’s a good idea to configure your Pingdom checks to first wait for a while and only alert you if the downtime continues.

Temporary errors do happen

But why wouldn’t you want to be informed the same second your website experiences downtime?
Well, first of all it’s good to know that the Internet isn’t always as stable as one could think; this is mostly due to its widespread infrastructure. By loading a website in a browser you’re almost always talking to at least a handful of different servers on the way.
The other and most important reason is that web servers can have temporary issues for a short period of time. Some examples are if backups are performed at a certain time of day which affects the server’s performance, maintenance windows where the server administrator is working with the server, temporary high load and restarts of the web server (in some cases this might be done automatically using scripts that monitor the server).
These kinds of issues are often called “false positives”, but in reality they are real errors. It’s just that they often go away by themselves so quickly that by the time you sit at your computer they are already gone.

Our suggested check configuration

We highly recommend that you always use a check resolution of 1 minute, meaning that we will test your website once every minute. Web servers are built to handle lots of requests, so checking it once every minute will not affect your web server performance or the bandwidth usage much. Checking every minute also means that you will collect more detailed data and lets you configure alerts with higher accuracy.
check resolution
Now let’s look at the important part of configuring alerts. This is where you set how and when to be alerted. In our suggested setup we are going to get a SMS (text) every time our website is down for more than 6 times. Since we have selected a check resolution of 1 minute the alert will be sent after 5 minutes of continuous downtime.
alert settings
We also selected to be alerted when our website is back up again. Using the “notify again every” option you can also receive additional reminders to make sure that no alert goes unnoticed.

Uptime still matters

Even though we think that maintaining a high uptime is very important, it might be wise to only be alerted on errors that are critical and don’t seem to be temporary.
This is especially true if you value your beauty sleep and don’t want to be woken up only to find your site working again.
It should be noted that we have something we call “second opinion” to filter out false alerts due to any local network issues. It works by always having a second server double-check a downtime from another location before we consider the website as down. But the second opinion will not filter out alerts where a temporary issue is happening on the web server such as the case we were discussing in this post.

Exit Rate vs Bounce Rate – Which One You Should Improve and Why

Tracking your website’s exit and bounce rates will give you insight into how [...]

Introduction to Observability

These days, systems and applications evolve at a rapid pace. This makes analyzi [...]

Webpages Are Getting Larger Every Year, and Here’s Why it Matters

Last updated: February 29, 2024 Average size of a webpage matters because it [...]

A Beginner’s Guide to Using CDNs

Last updated: February 28, 2024 Websites have become larger and more complex [...]

The Five Most Common HTTP Errors According to Google

Last updated: February 28, 2024 Sometimes when you try to visit a web page, [...]

Monitor your website’s uptime and performance

With Pingdom's website monitoring you are always the first to know when your site is in trouble, and as a result you are making the Internet faster and more reliable. Nice, huh?



Gain availability and performance insights with Pingdom – a comprehensive web application performance and digital experience monitoring tool.

Start monitoring for free