Is FedEx API down?
Shipzil checks the FedEx API every 5 minutes across EasyPost, Shippo, ShipStation and ShipEngine — four platforms run by three independent companies — and sends its own production rate request to each platform. Across 155 carrier-affecting incidents recorded here, 91% were reported by only one company, so a problem on a single platform usually means that platform's FedEx integration rather than FedEx itself. Snapshot at November 11, 2026, 03:55 UTC: FedEx API status: 4 operational across 4 monitored platforms. Last resolved incident: November 7, 2026. Over the last 90 days the worst-performing platform for FedEx was Shippo, at 95.68% reported uptime. The status below refreshes live.
95.68% on Shippo
0 of 3
Status by platform
| Platform | Company | Status | Status since |
|---|---|---|---|
| EasyPost | EasyPost | Operational | |
| Shippo | Shippo | Operational | |
| ShipStation | Auctane | Operational | |
| ShipEngine | Auctane | Operational |
Reported uptime, 90 days
Where a platform published component state changes, the window is measured from those — when each component actually left and returned to operational. Otherwise it falls back to when the incident was opened and closed, which overstates it. Either way this is uptime as reported by the platforms, not independently measured: there may be outages nobody reported. Account-surface incidents and standing advisories are excluded, since neither is carrier API downtime.
Of the 155 carrier-affecting incidents behind these figures, 45 (29%) had their carriers inferred from the incident title rather than a component the platform tagged. And a platform that reports less looks better here: Shippo 79, EasyPost 42, ShipEngine 25, ShipStation 9 incidents recorded respectively.
Measured reachability
Shipzil's own rate checks rather than a platform report: how often a request to each platform returned at least one bookable FedEx rate. Only platforms whose monitoring account can quote FedEx appear.
| Platform | Returned a rate | Checks | Last seen |
|---|---|---|---|
| EasyPost | 100.0% | 289/289 |
A check the platform never answered is excluded from these counts rather than charged to FedEx — which is why a platform with unanswered checks shows a smaller total than the rest. Those are the platform's own failures and are listed on its page. Percentages are withheld below 20 checks.
Platform-reported API response time, 24h
Published by the platform about its own API, not measured here and not specific to FedEx. Shipzil's own measurement of a FedEx rate request through each platform is in Measured reachability above, and is typically several times larger because it includes the carrier call. A platform that stops publishing keeps its last reading for up to two hours before it is dropped, so each row states when it was last published.
Platform-reported error rate, 24h
Published by the platform about itself. Only platforms that publish this appear, so absence here means a platform does not report it — not that its error rate is zero.
Incident history (68)
Show 53 older incidents
Standing advisories (1)
Unresolved for more than 48 hours and excluded from uptime.
No longer reported (1)
Never marked resolved, but the platform has dropped them from its status feed. Excluded from uptime beyond the point it stopped reporting them.
Scheduled maintenance (14)
FedEx API questions
- Is FedEx API down right now?
- FedEx API status is checked every 5 minutes against 4 shipping platforms run by three independent companies, plus an independent rate request to each. 91% of carrier-affecting incidents recorded here were reported by only one company, so a lone report usually points to that platform's integration rather than the carrier. Shipzil also records production rate failures even when the platform files no incident. The current reading is at the top of this page and refreshes without reloading.
- How is FedEx API status determined?
- Two separate signals. What each platform reports about FedEx on its own status page, across EasyPost, Shippo, ShipStation, ShipEngine; and Shipzil's own rate request to each platform's production API every 5 minutes, recording whether FedEx returned a bookable rate. The two are never merged: a platform reporting operational while our request fails is evidence, not a contradiction to resolve.
- Is FedEx down, or is it my shipping platform?
- Compare the platforms. If only one of EasyPost, Shippo, ShipStation or ShipEngine reports a FedEx problem, the fault is most likely that platform's FedEx integration; if platforms from two or more independent companies report it together, it is more likely FedEx itself. ShipStation and ShipEngine are both run by Auctane, so together they count as one source. Of 155 carrier-affecting incidents recorded here, 91% were reported by only one company. Shipzil's own rate checks add a third signal: a failure it measured that no platform reported.
- What is FedEx API uptime?
- FedEx reported 90-day uptime is 95.68% on its worst-performing platform (Shippo). Shipzil reports the worst platform rather than an average, because averaging mixes different integrations and improves the number every time a platform is added. This is uptime as reported by those platforms, not independently measured.
How FedEx reliability differs by platform, side by side: EasyPost vs Shippo vs ShipStation vs ShipEngine.