Shipnest
Degraded performance
Checked 10/18/2026, 11:42:44 AM
JSON
Components
  • Database
    22ms round-trip
    ok
  • Error floor (15m)
    No elevated failures
    ok
  • Carrier fleet (last test)
    All 10 enabled carrier accounts passing
    ok
  • Channel sync (10m)
    Last success 2m ago
    ok
  • Tracking refresh (30m)
    Last success 12m ago
    ok
  • Scheduled reports (60m)
    Last success 41m 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 2h ago
    ok
  • Carrier credentials check (24h)
    Last success 6h ago
    ok
  • Redis cache (Upstash)
    fetch failed
    degraded
Incident history (90 days)0 incidents
No incidents in the last 90 days. The ledger updates automatically when the live snapshot drops below all-OK.

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.