updown.io
updown.io keeps methodically widening its probe network and deepening pulse monitoring.
◆Recent moves
- 4d ago
🇨🇦 New Toronto monitoring location
Replaces the Montreal node with a Toronto one for better IPv6 reliability and bundles pagination for large accounts, pulse string validation, and API and notification fixes — a typical multi-item updown release.
View source ↗ - 2mo ago
String match with pulse checks
Adds response-body string matching to pulse checks so a cron job's output can be validated, not just its presence, alongside a batch of small fixes — deepening the pulse monitoring surface.
View source ↗ - 8mo ago
New Location: Cap Town, South Africa 🇿🇦
Adds a Cape Town, South Africa probe location, broadening geographic coverage, with an IP-filtering caveat for affected accounts.
View source ↗ - 8mo ago
📉 New 10y performance history chart
Introduces a bespoke 10-year performance chart on status pages for long-term trend analysis, with SVG export and mixed daily/monthly granularity.
View source ↗ - 1y ago
⏰ Pulse monitoring
⚡ SPARKShipping pulse monitoring extended updown from HTTP uptime checks into cron/heartbeat monitoring — the capability that anchors the recent run of pulse refinements.
View source ↗ - 1y ago
❌ Downtime list
Adds a consolidated, filterable list of all downtimes with detailed per-event timelines, a long-requested view that surfaces history previously buried in email alerts.
View source ↗