Reported USPS, FedEx and UPS status across four shipping platforms, plus a production rate check every 5 minutes. Across 135 carrier-affecting incidents recorded here, 90% were reported by only one company — so a lone report usually means that platform's integration rather than the carrier.
All carrier APIs operational
· checked
4/4 measured rate checks succeeded on the latest run · lowest 24h coverage 100.0%
Status data may be stale — the monitor has not reported in over 20 minutes.Collection status
Reported carrier status
Current carrier component status published by each platform. A gray “last known” reading means
the source did not report on the latest collection.
One fixed rate request to each platform’s production API, every 5 minutes. One request
path, not a speed ranking — how this works.
Rating latency, last 24h
breaks in a line are collection gaps
Measured rating latency per platform over the last 24 hours, sampled every 5 minutes.
1 check a platform did not answer is marked on the baseline. A break in a line with no mark is a check the collector never ran.
5-minute checks · all 4 platforms · selections are saved in the URL
EasyPost1764ms
Shippo1781ms
ShipStation3339ms
ShipEngine3733ms
no answer (1)
Ticks mark checks the platform did not answer in time. A break in a line with no tick is a check we never ran — ours, not theirs.
1 unanswered by ShipEngine · 0 not collected by us
All 289 samples quoted 2 carriers
p95 5993ms 290 observed last sample
Scope: one monitoring account per platform, a 16 oz 10×8×4 in parcel from San Francisco to
Washington, DC, from a scheduled Cloudflare Worker. Connected carrier sets differ. ShipStation v1 is
checked against USPS only. Methodology and limits
· JSON telemetry API