logs.sologs.so
StatusPricingBlogDocs

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.

View a status page

Free forever. No card. Pro is $19/mo.

logs.so · watching 4 channels
60m agonow
payments
quiet 26:00
signups
just now
emails
just now
agent-runs
just now
1 went quiet3 channels healthy

payments went quiet

No checkout.session.completed for 26 minutes. Expected one every 15.

logs.so paged you · now

Works with

  • Lovable
  • Bolt
  • Cursor
  • v0
  • Claude Code
  • Codex
  • 10x.app
  • Xcode

How it works

  1. 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. 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. 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. 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.

logs.so/status/demo · Harbor

Harbor

Checkout, billing webhooks, and nightly jobs for Harbor.

Major outage

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 page

Unsubscribe 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.

Plans

  • Free$0. Unlimited events, 7-day history, one branded public status page.
  • Pro$19/mo. Full history, silence monitors, automatic incidents, 250 subscribers.

Business is $299 per month and contact only. Email mail@logs.so.

See pricing

Know the moment it goes quiet.

Free forever. No card.

View a status page
logs.sologs.so

Email when expected production activity goes quiet.

Product

  • Status demo
  • Pricing
  • Docs
  • Blog
  • Contact

Builders

  • For Lovable
  • For Bolt
  • For Cursor
  • For v0
  • For Claude Code
  • For Codex
  • For 10x.app
  • For Xcode

Company

  • Support Teams
  • Privacy
  • Terms
© 2026 logs.soIncident email and public status pages.