FedEx tracking spends most of a parcel's journey cycling through four statuses: arrived at a FedEx hub or location, departed it, arrived at the next one, departed that. They read like the parcel is going in circles. It is not; it is going through the network. This page explains each of those scans, in the order they appear, and what "departed FedEx hub" tells you about when the parcel will arrive.
Short answer: "Departed FedEx hub" means your parcel has been scanned leaving one of FedEx's large sorting hubs and is on a truck or plane to the next point on its route. "Arrived at FedEx hub" is the scan before it, at the same building. "Departed FedEx location" and "arrived at FedEx location" are the same two events at a smaller facility. "At local FedEx facility" means the parcel has reached the station that serves your address, which is the last stop before "on FedEx vehicle for delivery". Departing a hub is not the same as being out for delivery: there can be one or several more arrive-and-depart pairs first, especially on long or international routes.
The four scans, in order
| Status | Where the parcel is | What it means |
|---|---|---|
| Arrived at FedEx hub | Inside a major FedEx sorting hub | The parcel has been scanned in at a hub and is being sorted toward its next destination |
| Departed FedEx hub | Leaving that hub | Sorted and loaded onto the next linehaul, by truck or by air |
| Arrived at FedEx location / departed FedEx location | A smaller FedEx facility, such as a ramp or a regional station | The same in-and-out pair at a facility that is not one of the big hubs |
| At local FedEx facility | The FedEx station that serves your address | The last stop; the parcel is waiting to be loaded onto a delivery vehicle |
| On FedEx vehicle for delivery | On the van | Delivery is expected today |
"Hub" and "location" are FedEx's words for the size of the building, not for a different kind of event. A parcel from the West Coast to the East Coast might show arrived and departed at an origin station, a regional hub, a national hub and a destination station before reaching the local facility.
Why the statuses repeat
Every facility the parcel passes through produces an arrival scan and a departure scan. A domestic ground parcel might show two or three pairs; an international one, more, with a customs stage in between. Seeing "departed FedEx hub" twice from two different cities is the network working, not a routing error. The general version of this pattern, which every carrier shares, is in departed from facility and arrived at facility.
"Departed FedEx location" but not out for delivery
This is the most searched confusion. "Departed FedEx location" only says the parcel left a building. If that building was the local facility, the next scan is usually "on FedEx vehicle for delivery" the same morning. If it was a hub two states away, the parcel still has linehaul ahead of it and will show "arrived at FedEx location" at the next stop. The tell is the city on the scan: when the departure scan is from a facility in or near your city, delivery is close; when it is from somewhere far away, it is not.
How long does each stage take?
FedEx publishes no per-scan timings, so this is a practical reading rather than a rule.
- Between "arrived at FedEx hub" and "departed FedEx hub": usually the same day. Hubs sort continuously and the parcel leaves on the next departure to its destination.
- Between "departed FedEx hub" and the next arrival scan: overnight for a regional hop by truck, longer for a cross-country or international leg. FedEx Express moves by air and shows fewer, faster hops; FedEx Ground moves by truck and shows more.
- From "at local FedEx facility" to "on FedEx vehicle for delivery": typically the next morning, sometimes the same day if the parcel arrived early.
- When to worry: a parcel that has shown "departed FedEx hub" with no further scan for more than two or three business days, or that keeps arriving and departing the same city. That is the moment to check the estimated delivery date on the tracking page and, if it has passed, to contact the shipper, who as FedEx's customer can open the trace.
Where to see the full picture
The FedEx tracking page shows every scan with its city and time, and the estimated delivery date at the top. When the statuses on this page are confusing, the city sequence usually explains them. The rest of FedEx's vocabulary, including "shipment information sent to FedEx", "delivery exception" and "delivered", is in FedEx tracking statuses; the case where FedEx shows only a delivered scan with no history is in FedEx no travel history; and the generic meanings of "in transit" and "out for delivery" are in why is my package stuck in transit and out for delivery meaning.
For merchants
Your customers are reading FedEx's scans in FedEx's words, and "departed FedEx hub" from a city they have never heard of generates the ticket "where is my package". The fix is to normalise every carrier's statuses onto one small set the customer understands ("on its way", "at your local facility", "out for delivery") and to message proactively when a scan sequence stalls. That is what Pango does across more than 100 carriers through prebuilt connectors, on one record of the order, so a stalled hub scan triggers a message and a check rather than a ticket.
The bottom line
"Departed FedEx hub" is a parcel leaving a sorting hub for the next stop, and the arrive-and-depart pairs around it are the network doing its job. Read the cities, not the words: a departure from your own city is delivery tomorrow, a departure from far away is another hop. The full FedEx vocabulary is in FedEx tracking statuses.
