Silence detection and public status
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
1
Send the events your server already sees. Payments, webhooks, crons, agents. One HTTP call, or a prompt in Cursor, Lovable, Bolt, or v0.
2
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
When the channel stays quiet past the grace, Pro emails confirmed subscribers. That is the notice, not a dashboard you have to watch.
4
Free can publish a branded public page and open incidents by hand. Pro opens the incident automatically. The next expected event closes it.
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
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
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
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.
Business is $299 per month and contact only. Email mail@logs.so.