Cronitor incident

Pings and telemetry not being received

Resolved after 46 minutes, affecting Site Analytics and Telemetry API, on November 8, 2026.

resolved Nov 08, 2026, 10:18 PM UTC

This incident is resolved. cronitor.link was unavailable from about 1:32 PM to 1:46 PM PT (21:32 to 21:46 UTC), and pings and telemetry have been received normally since. Pings sent during that window may not have been recorded, so missed-ping alerts from that time may be false.

Started
Nov 08, 2026, 09:32 PM UTC
Resolved
Nov 08, 2026, 10:18 PM UTC
Duration
46m
Detected by Pingoru
Nov 08, 2026, 09:32 PM UTC

Affected components

Site AnalyticsTelemetry API

Update timeline

  1. investigating Nov 08, 2026, 09:45 PM UTC

    We're investigating an outage of cronitor.link, the endpoint that receives pings and telemetry. Since about 1:32 PM PT (21:32 UTC), requests to it are failing, so job pings, heartbeats and site analytics may not be getting recorded. This may cause missed-ping alerts for jobs that are actually running fine. The dashboard and API at cronitor.io are working. We'll post another update within 30 minutes.

  2. monitoring Nov 08, 2026, 10:07 PM UTC

    Pings and telemetry are being received again as of about 1:46 PM PT (21:46 UTC). We're monitoring to confirm full recovery. Pings sent during the outage may not have been recorded, so some missed-ping alerts in that window may be false.

  3. resolved Nov 08, 2026, 10:18 PM UTC

    This incident is resolved. cronitor.link was unavailable from about 1:32 PM to 1:46 PM PT (21:32 to 21:46 UTC), and pings and telemetry have been received normally since. Pings sent during that window may not have been recorded, so missed-ping alerts from that time may be false.

Your product runs on more than Cronitor

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →