Uptime check results

Each time Pingdom finishes an uptime check, a Beam agent reads the result and status history for that endpoint. It applies your approved rule to decide whether a failed check is a real outage or a blip, then updates the incident record or opens an alert. Confirmed downtime notifies the responsible owner automatically with the affected check named. A single ambiguous failure, a check from one flaky location, or a pattern that could be a false positive is routed to a person, who confirms it before anyone is paged in the middle of the night.

Page speed reports

Slow pages hurt quietly. When Pingdom posts a page speed or performance report, the agent reads the timings, compares them against your approved thresholds, and records whether the page passed or regressed. Pages within budget log without noise. A meaningful slowdown, a metric crossing your limit, or a regression against last week is written up and sent to the responsible team with the specific timings attached. Cases where the data looks incomplete or the test itself failed are held for a human, so nobody wastes an afternoon chasing a performance ghost that never existed.

Incident alert handling

Alerts pile up fast during a rough day. On a new Pingdom alert, the agent reads severity, affected checks, and any linked incident, then applies your rule to group related alerts, update the open incident, and notify the right responder. Clear, single cause alerts are handled and annotated on their own. A storm of alerts spanning several services, or an alert that does not map to a known check, is escalated to an engineer with the full context gathered, so a person leads the response instead of drowning in duplicate pages during an outage.