LoginSign Up
← Back to all sparks
U

updown.io

ANALYTICS
Velocity2.5

updown.io sends domain-expiry alerts to every channel and moves French SMS alerts to a UK number.

uptime-monitoringalertingsmsdomain-expiryssldevops
◆Current state
On 8 November updown.io moved SMS alerts sent from its French number to a UK number after the French regulator reserved mobile numbers for person-to-person messages. The same update routes domain expiration alerts through every notification channel with a new webhook event, adds dashboard warnings for malformed HTTP/2 headers, errors after a 2xx and charset mismatches, and exposes certificate details in the API. September brought a detailed check page with multi-year heatmaps and SLA history.
◆Where it's heading
updown.io keeps widening what a single check reports, from heatmaps and SLA history to certificate and domain data, while staying a small, steady shipper. Alerts now reach the channels teams already use rather than email alone.
◆Prediction
Expect more domain and certificate signals exposed through the API and webhooks, extending the domain-expiration event added here.

◆Recent moves

  1. 5d ago

    📱 New SMS sender number

    French SMS alerts move to a UK sender after a regulator change, and domain expiration alerts now reach Slack, Teams, webhooks and other channels. New dashboard warnings explain why a check behaves oddly, adding to the richer check reporting started in September.

    View source ↗
  2. 2mo 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 ↗
  3. 3mo 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 ↗
  4. 4mo 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 ↗
  5. 7mo 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 ↗
  6. 1y 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 ↗