Silence detection and public status
Email when production goes quiet.
Instrument a channel and set the expected rhythm. If activity stops, logs.so can email confirmed subscribers and publish the same incident on your public page. Recovery closes it.
Free forever. No card. Pro is $19/mo.
payments went quiet
No checkout.session.completed for 26 minutes. Expected one every 15.
logs.so paged you · now
How it works
1
Instrument a channel
Send the events your server already sees. Payments, webhooks, crons, agents. One HTTP call, or a prompt in Cursor, Lovable, Bolt, or v0.
2
Set an expected rhythm
Tell logs.so how often that channel should move, plus a grace period. Silence is only a bug when activity was supposed to arrive.
3
Receive an incident email
When the channel stays quiet past the grace, Pro emails confirmed subscribers. That is the notice, not a dashboard you have to watch.
4
Publish, then close on recovery
Free can publish a branded public page and open incidents by hand. Pro opens the incident automatically. The next expected event closes it.
A public status page your customers can trust
Components, incidents, and email for confirmed subscribers. Silence can open the incident. Recovery closes it. No manual copy-paste onto a status page.
Harbor
Checkout, billing webhooks, and nightly jobs for Harbor.
Components
- Checkout APIOperational
- Billing webhooksMajor outage
- Nightly reportsOperational
- Agent runsOperational
Billing webhooks have gone silent
Harbor expected a billing event at least every 5 minutes. None arrived after the grace period, so this incident opened automatically.
Open · 47 minutes ago
From logs.so
Incident opened: Billing webhooks have gone silent
logs.so
Billing webhooks have gone silent
Expected activity stopped. Harbor published this incident automatically.
Harbor expected a billing event at least every 5 minutes. None arrived after the grace period, so this incident opened automatically.
View status pageUnsubscribe from these emails
Incident opened by silence detection
Powered by logs.so
Instrument a channel in one paste
Paste a prompt into your agent, or send one HTTP call. The feed is how you prove the channel is alive. Silence detection is how you notice when it is not.
Compare silence detection
Status pages, event feeds, and cron pings can all look healthy while a channel is quiet. These pages spell out the difference, plus checks for an overdue cron and a Stripe webhook that returned 200 while payment never processed.
Plans
- Free$0. Unlimited events, 7-day history, one branded public status page.
- Pro$19/mo. Full history, silence monitors, automatic incidents, 250 subscribers.