Sendfable is being written now — join the early-access list.

sendfable

Status

This is a static status foundation — not a live monitor and not a page of invented uptime charts. When we publish real-time components, they will replace this explanation.

Current posture

No automated status feed is connected on this page yet.

If you are experiencing an issue, check your workspace dashboards first (sends, bounces, billing), then email support. We will not invent a green checkmark to look “always up.”

What status will cover

  • App & API — ability to sign in, edit campaigns, and manage audiences
  • Sending pipeline — queue workers that hand messages to Amazon SES
  • Tracking & webhooks — open/click recording and SES event ingestion
  • Billing — Stripe checkout and portal availability (when relevant)

Dependencies we do not control

Inbox placement and Amazon SES regional availability can affect delivery even when Sendfable's app is healthy. We will distinguish product incidents from upstream provider issues whenever we post updates.

How we will communicate

  1. Post incident summaries on this status surface (or a dedicated status host).
  2. Note start time, impact, and resolution without vague “degraded performance” fluff.
  3. Link related changelog entries when a fix ships.

Prefer email updates? Contact support from your account email once you are signed up — we are not collecting a fake status-subscriber count on this page.

Build on a clear foundation

Create a free Sendfable account while we expand live status reporting.