Trust

System Status

Uptime and incident history for the systems that deliver your digests.

All systems operational

As of Oct 3, 2026, 12:00 UTC — no open incidents

100% uptime since launch

Read this honestly: our self-monitoring started today (Oct 3, 2026). The 30-day grid below therefore shows one measured day; the remaining slots are greyed out because that history does not exist yet — we won't paint retroactive green. Before today, uptime was good but we have no independent instrumented data to publish, so we publish none. This page will fill itself in truthfully over time.

30-day uptime

Oct 3 ← 29 days not yet measured

Monitored · operational Before monitoring started (no data)

Components

Public website & scanner tool

alertsnail-pace-bills.vercel.app — uptime since Oct 3, 2026: 100%

Operational

Competitor price & stock scanners

Scheduled scan cycles (daily / 4x daily / hourly by plan) — uptime since Oct 3, 2026: 100%

Operational

Email digest delivery

Transactional digest pipeline — uptime since Oct 3, 2026: 100%

Operational

Telegram alert delivery

Instant alerts & Monday summaries via Telegram Bot API — uptime since Oct 3, 2026: 100%

Operational

Incident history

No incidents to report. Self-monitoring began on October 3, 2026, and every scheduled scan cycle and digest delivery has run successfully since. As history accumulates, real incidents (and real failures) will appear here — we will not delete them.

How incidents will be reported

1 — This page updates first

Any degradation is posted here with a severity label: Degraded (partial delays), Major outage (digests not delivering), Critical (data integrity or security). Updates at least every 30 minutes while open.

2 — Affected customers get an email

If missed or delayed digests are attributable to our infrastructure, affected accounts receive a notification and, where it exceeds the 48-hour promise, a prorated credit per our Refund Policy.

3 — Post-mortem within 48 hours

Every Major or Critical incident gets a plain-language post-mortem here: what broke, who it affected, what changed so it won't repeat. No "a third-party provider had an issue" cop-outs unless it literally was, and then we say which and what we did about it.

4 — Competitor-site blocks are handled differently

If a specific competitor's site blocks scanning (bot walls, redesigns), that's not an AlertSnail outage — we'll mark those URLs "coverage degraded" in your digest footer and tell you which clusters we're adapting to, rather than hiding it.

This status page is currently maintained manually by our operations automation and reviewed daily. For incident questions: alertsnaildesk@gmail.com.