Shipnest
All systems operational
Checked 6/17/2026, 12:21:10 PM
JSON
Components
  • Database
    21ms round-trip
    ok
  • Error floor (15m)
    No elevated failures
    ok
  • Carrier fleet (last test)
    All 7 enabled carrier accounts passing
    ok
  • Channel sync (10m)
    Just ran
    ok
  • Tracking refresh (30m)
    Last success 18m ago
    ok
  • Scheduled reports (60m)
    Last success 19m ago
    ok
  • Catalog sync (24h)
    Last success 4h ago
    ok
  • Demo reset (24h)
    Last success 3h ago
    ok
  • Past-due dunning (24h)
    Last success 2h ago
    ok
  • Data retention sweep (24h)
    Last success 3h ago
    ok
  • Carrier credentials check (24h)
    Last success 6h ago
    ok
  • Redis cache (Upstash)
    57ms round-trip
    ok
Incident history (90 days)1 incident
  • Degraded
    Carrier credentials check (24h): Last success 93h ago
    5/19/2026, 10:03:09 AM · Resolved after 6m · cron-credential-check

This page updates on every request — no cache. Poll /api/status.json from your monitoring tool (UptimeRobot, Pingdom, Datadog Synthetics). The response always returns HTTP 200 — alert on the overall field so third-party probes don't false-alarm on 503.

Carrier + channel reachability is per-tenant and visible to org members under /carriers and /integrations. This public page only speaks to platform infrastructure.