Degraded performance
Checked 7/21/2026, 6:24:34 PM
Components
- Database23ms round-tripok
- Error floor (15m)No elevated failuresok
- Carrier fleet (last test)All 7 enabled carrier accounts passingok
- Channel sync (10m)Last success 4m agook
- Tracking refresh (30m)Last success 22m agook
- Scheduled reports (60m)Last success 20m agook
- Catalog sync (24h)Last success 13h agook
- Demo reset (24h)Last success 12h agook
- Past-due dunning (24h)Last success 7h agook
- Data retention sweep (24h)Last success 11h agook
- Carrier credentials check (24h)Last success 12h agook
- Redis cache (Upstash)fetch faileddegraded
Incident history (90 days)2 incidents
- DegradedCarrier credentials check (24h): Last success 93h ago5/19/2026, 10:03:09 AM · Resolved after 6m · cron-credential-check
- DegradedRedis cache (Upstash): fetch failed7/16/2026, 4:09:26 PM · Ongoing (5d) · redis
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.