PSend

PSend Service Status

System status

Live HTTP probes against API, workers, monitor, and dashboard. Same checks your uptime tools can hit via /api/status.

Down

0 healthy · 0 starting/degraded · 10 down · live probes

Down
Healthy 0Starting / degraded 0Down 10

Last check · 22 Oct 2026, 13:45 UTC · refreshed every request (15s server cache)

Edge & API

  • REST API

    Send, batch, audiences, inboxes, broadcasts, teams, domains — accept path

    Down

    rtt 12ms · 99.98% / 90d

  • Auth & API keys

    Bearer validation, OAuth (Google / GitHub), sessions

    Down

    rtt 12ms · 99.99% / 90d

  • Dashboard

    Control plane UI for keys, domains, and wallet

    Down

    rtt 10ms · 99.93% / 90d

Send path

  • Accept → queue

    Async send workers after HTTP 202 accept

    Down

    rtt 10ms · 99.97% / 90d

  • Bulk batch pipeline

    POST /v1/emails/batch fan-out and rate shaping

    Down

    rtt 10ms · 99.94% / 90d

  • SMTP egress

    Outbound MTA pools delivering to recipient MX

    Down

    rtt 10ms · 99.95% / 90d

  • IP pool health

    Proactive rotation and reputation probes

    Down

    rtt 10ms · 99.92% / 90d

Events & identity

  • Webhook delivery

    HMAC-signed lifecycle events with retry / backoff

    Down

    rtt 12ms · 99.96% / 90d

  • Domain verification

    SPF / DKIM / DMARC DNS checks

    Down

    rtt 12ms · 99.91% / 90d

  • Wallet & billing

    Prepaid balance debit on accept, top-ups

    Down

    rtt 12ms · 99.97% / 90d

Past incidents

  • Elevated queue lag in eu-central

    resolved · minor

    12 Oct 2026, 14:22 → 12 Oct 2026, 15:08 UTC

    1. 12 Oct 2026, 14:22 UTC

      Investigating p95 accept→sent latency above SLO in eu-central workers.

    2. 12 Oct 2026, 14:41 UTC

      Identified saturated batch shard. Scaling workers; new accepts unaffected (still 202).

    3. 12 Oct 2026, 15:08 UTC

      Queue depth normalized. Delivery back within SLO. Monitoring for 60m.

Subscribe & probe

Automate checks against GET /api/status on this site, or GET /health on the API process. Incident mail: [email protected].

curl -s http://localhost:3000/api/status | jq '.status, .components[] | {id, status, latency_ms}'
LegendHealthyStarting upDegradedPartial outageDown

Green = healthy / UP · Yellow = starting up or degraded · Red = partial outage or down