LoginSign Up
← Back to all sparks
U

updown.io

ANALYTICS
Velocity5.0

updown.io adds closed port monitoring and a detailed check metrics page with multi-year uptime heatmaps.

uptime-monitoringslanetworkindiedevops
◆Current state
updown.io has been steadily expanding beyond simple HTTP uptime monitoring: pulse monitoring for cron jobs and internal services (shipped Feb 2025), closed TCP port monitoring to verify firewall rules, string matching in pulse check bodies, and now a detailed check page with 48h/60d/10y heatmaps and per-month SLA percentages. Geographic coverage expanded with Toronto and Cape Town nodes.
◆Where it's heading
The product is growing from a ping-and-alert tool into a lightweight observability layer for small teams — each release adds a class of monitoring that previously required a heavier tool (Datadog, Grafana). The 10-year performance chart and SLA history are squarely aimed at teams tracking uptime commitments over time, not just incident response.
◆Prediction
The next likely move is API-accessible historical metrics so teams can pull SLA data into their own reporting — the 10-year chart suggests demand for long-term uptime data that currently lives only in the UI.

◆Recent moves

  1. 13d ago

    New check details page: heatmaps, per-location data, and SLA history

    The new check details page adds 48h/60d/10-year uptime/Apdex/response-time heatmaps, per-location breakdowns, and monthly SLA percentages — a substantial data density upgrade for teams that track uptime commitments over long periods.

    View source ↗
  2. 1mo ago

    🛑 Closed port monitoring

    Closed TCP port monitoring lets teams verify that firewall rules are actually blocking ports — a security-posture use case that uptime monitoring tools rarely cover, extending updown beyond availability into basic network hygiene.

    View source ↗
  3. 2mo ago

    New monitoring node: Toronto replaces Montreal (better IPv6)

    Toronto monitoring node replaces the old Montreal node with better IPv6 reliability — geographic maintenance with improved network path quality but no user-visible capability change.

    View source ↗
  4. 5mo ago

    String match with pulse checks

    String matching in pulse check bodies lets updown verify that a periodic task sent meaningful content in its heartbeat, not just that it arrived — a correctness check for cron job monitoring beyond simple liveness.

    View source ↗
  5. 10mo ago

    New monitoring location: Cape Town, South Africa

    Cape Town (South Africa) monitoring node adds an African presence point — geographic expansion with the usual IP-filtering caveat for accounts that restrict locations.

    View source ↗
  6. 11mo ago

    10-year performance history chart

    The 10-year performance history chart gives teams a long-range view of response time trends — useful for measuring the impact of infrastructure changes (CDN migrations, app rewrites) against a multi-year baseline.

    View source ↗