All systems
operational.
Live operational state for every SendNectar component, plus how we handle incidents when something does go wrong.
Every moving part, individually.
No incidents recorded.
SendNectar is early, and we would rather show an empty history honestly than manufacture one. When an incident happens, it is posted here with its severity, the surfaces affected, the timeline, and what changed afterwards.
What "operational" means here.
Incidents are records, not vibes
Every operational incident is stored with a type, severity, start time, and resolution time — the same table your workspace reads from. What we publish here is what our systems recorded.
Queues never silently drop work
Background jobs and workflow steps run on leased workers with attempt counts and retries. A transient failure is retried and visible, not swallowed.
Delivery degradation is yours to see
Provider-level delivery, bounce, and complaint rates are scored daily in your own reporting — so a provider problem shows up in your workspace, not just ours.
Consent processing has no failure mode
Bounce, complaint, and unsubscribe handling cannot be disabled or deferred, including during an incident. Suppression is applied before delivery, always.
Operational,
and honest about it.
Start free.
Connect a provider in test mode and watch every message, event, and job for yourself.