Skip to main content

Changelog

All notable changes to PingSLA are documented here.

The format follows Keep a Changelog.

[2.0.0] — 2026-05-18​

Added​

  • Multi-region probe architecture — checks from 4 global regions simultaneously
  • Keyword monitors — detect strings in HTTP response bodies
  • SSL certificate monitoring — expiry alerts with configurable warning thresholds
  • Slack notification channel — Slack Block Kit formatted incident messages
  • Outbound webhooks — HMAC-signed payloads with full incident data
  • Status page subscriber notifications — email subscribers get incident updates
  • Escalation policies — Business/Enterprise: escalate if incident unacknowledged
  • Audit logs — Business/Enterprise: full administrative action log
  • Custom status page domains — CNAME-based with automatic SSL provisioning
  • SLA reports — 30/60/90-day uptime percentages per monitor
  • API v1 — full REST API with OpenAPI 3.1 spec
  • Probe IP endpoint — GET /v1/probe-ips for firewall allowlisting

Improved​

  • Dashboard performance: reduced initial load time by 60%
  • Incident timeline now shows per-region failure breakdown
  • Probe check latency reduced from ~5s to ~1.2s average
  • Status page loads in under 500ms (static SSR)

Fixed​

  • Monitor status badge not updating after incident resolution
  • Telegram notifications failing for supergroups with 100 prefix IDs
  • SSL check false positive when intermediate cert uses SHA-1 signature
  • Status page iframe embed breaking for pages with special characters in slug

Breaking Changes (v1 → v2)​

  • API base path changed from /api/ to /v1/
  • Monitor status field renamed from active/inactive to up/down/paused
  • Notification channels moved from alert policy inline config to reusable channel objects

[1.5.0] — 2026-03-01​

Added​

  • Custom check intervals — 30-second option on Business plan
  • Monitor groups — organize monitors into folders in the dashboard
  • Maintenance windows — schedule downtime that excludes from SLA calculations
  • Mobile-responsive status pages

Fixed​

  • Race condition where two simultaneous failures could create duplicate incidents
  • HTTP monitor not following redirects correctly on 307 Temporary Redirect

[1.4.0] — 2026-01-15​

Added​

  • Telegram notification channel
  • Status page RSS/Atom feeds
  • Monitor bulk operations — pause/resume/delete multiple monitors at once
  • API key expiry configuration (optional)

Fixed​

  • Email alerts being rate-limited during large-scale incidents with many monitors down simultaneously

[1.3.0] — 2025-11-20​

Added​

  • Public status pages with hosted subdomain
  • Team workspace model — multiple users per workspace
  • RBAC — Owner, Admin, Editor, Viewer roles
  • Status page subscriber email notifications

[1.2.0] — 2025-09-10​

Added​

  • Multi-probe locations — US East, EU West
  • HTTP monitor request body — POST/PUT with body payload
  • Custom request headers on HTTP monitors
  • Response time alerting — fail if response exceeds threshold

[1.1.0] — 2025-07-01​

Added​

  • Ping (ICMP) monitors
  • Alert policy system — configurable failure/recovery thresholds
  • Email notification channel
  • Incident history

[1.0.0] — 2025-05-15​

Initial Release​

  • HTTP monitor with status code validation
  • Basic dashboard
  • Single-user workspace
  • Email notifications on monitor DOWN