Status · live telemetry
System status
Live health of every Pulsewise component, 90-day uptime, and the full incident history.
Components
Per-service health, region routing, and live throughput.
REST endpoints, auth, and rate-limiter.
App shell, charts, and live socket streams.
Telemetry pipeline from connected hosts.
Email, Slack, Discord, and webhook fan-out.
Inference engine for incident root-cause.
Login, sessions, OAuth, and workspace ACL.
Uptime · last 90 days
Every bar is a UTC day, coloured by the most severe event recorded.
Incident history
Every postmortem is published in full — what broke, when, and what we changed to prevent it.
Scheduled metrics database migration
Planned migration of the time-series store to improve query performance under high cardinality. Executed in a low-traffic window with no user-facing impact.
Alert delivery latency on Slack and Discord
Outbound alerts to Slack and Discord were delayed by up to 3 minutes due to upstream rate-limiting from both providers during a traffic spike.
Ingestion pipeline throughput upgrade
Blue-green rollout of a higher-throughput ingestion fleet. Traffic was shifted progressively with no metric loss during the cutover.
Elevated API latency from a single workspace
API P95 spiked to ~800ms after a single workspace with 200+ servers began polling at 4× normal cadence. Mitigation included rate-limiting and horizontal scale-out.
AI diagnostics engine outage
AI summary generation returned errors for new incidents due to an expired internal TLS certificate on the inference gateway. Queued requests were processed retroactively.
Get notified the moment something changes
One email per incident — when it starts, when it’s mitigated, and a postmortem when it’s closed. No marketing. No noise.
- Incident emails
- RSS feed
- Webhook