If your parcel is somewhere on a US transit route this week, here is the direct answer: the nationwide ground stop of November 13 held departures for a bit more than four hours, and the problem it left behind is a hub backlog that clears in days. That makes it a delay event for cross-border shipments, not a lost-package event; Xinhua reported that the stop also caused broad disruption to logistics transport [1]. The useful next step is not a support ticket. Open the tracking page, find the last physical scan, and read it against the carrier's own delivery estimate [2].
What actually stopped: on the afternoon of November 13 local time, air traffic control communication networks in the United States began reporting anomalies, and the FAA ordered airports nationwide to hold flights at the gate. Aircraft already in the air kept flying under control and landed; the order was lifted at 8:15 that evening [3]. The FAA's own definition explains the shape of the disruption. A ground stop requires aircraft meeting specific conditions to stay on the ground, it ranks among the most restrictive traffic-management tools, and flights already airborne are not restricted and may continue to land [1]. A parcel that was already airborne that afternoon was never grounded. The bottleneck formed on the ground, at departure airports and at hub sorting operations, which is why shipment visibility, not the flight map, is what a buyer should watch.
Why four hours became a weekend
The stop ended the night of November 13. The backlog did not. Flight-tracking agencies counted roughly 9,000 to 10,000 cancelled flights on the 13th and thousands more on the 14th [3]. Reuters, as cited by CCTV, put the cumulative count of delayed or cancelled flights past 20,000 by the evening of November 14 [4]. Xinhua reported that with aircraft and crews displaced, airlines might need days to fully resume operations [1]. The hubs took the worst of it, with New York, Atlanta and Chicago among the airports where large numbers of travelers were stranded [3].
The weekend numbers show the recovery pace. As of midday November 15, more than 1,600 flights had been cancelled and nearly 3,800 delayed [5]. JetBlue had cancelled 27 percent of that day's planned flights and American Airlines 13 percent [5]. Transportation Secretary Sean Duffy said on November 15 that operations were expected to recover gradually that day and reach full recovery on November 16, because aircraft and crews were not at their scheduled duty positions [5]. That is his forecast as of November 15, not a confirmed result; the carrier's own service alerts remain the better source for whether your specific route is moving [2].
For a shipment, the practical reading is that this event could stretch delivery timelines by days, the same scale as the days airlines need to reposition aircraft and crews [1], so the clock to judge against is the delivery estimate the carrier already published, not the number of hours since your last scan.
What a stalled tracking page can prove
The 17TRACK delay guide gives a checking order that fits this situation. A silent tracking page alone does not prove a package is delayed or lost; start with the latest physical scan, any exception message, and the carrier's current delivery estimate [2]. A scan recording acceptance, pickup, arrival or departure is stronger evidence of carrier handling than a label-created message [2]. Read the individual events underneath the big status label, including dates, locations and any instructions, because a broad status such as "In transit" can cover several stages [2]. The locations in that event history also answer whether this event touches your order at all: scans naming US cities are the sign that a parcel rides a US leg.
Silence inside the delivery window means little by itself. A shipment without a new scan is not necessarily late if it remains within the expected delivery window, and an estimate is not automatically a delivery guarantee [2]. Carrier handoffs also create gaps: some shipments change carriers before final delivery, and tracking updates may pause between the first carrier's handover event and the next carrier's acceptance scan [2].
A hub disruption leaves specific fingerprints. It can appear as a processing-delay notice, a changed delivery estimate, or an unusually long gap after arrival at a sorting facility, and a generic "Operational delay" or "Delivery exception" label does not by itself establish what happened [2]. An explicit instruction, such as a customs document request or a collection notice, usually matters more than a generic transit status [2]. Check the carrier's own service alerts alongside the shipment details, and if tracking gives no weather reason, do not infer one from a local forecast [2].
Hypothetical example, to show the method: a parcel last scanned "Arrived at sorting center" on November 12, silent since, still inside a delivery window that runs to November 20. Nothing on that page proves delay or loss. If an exception message says "Clearance delay," the request inside that message, not the silence, is the thing to answer.
When waiting ends and acting starts
The same guide matches the action to the stage where progress stopped [2]:
- No confirmed carrier receipt: ask the seller to verify dispatch and handover. The seller is usually better positioned to investigate at this stage.
- An explicit request for information or payment: verify the request and respond through the official channel.
- A delivery attempt or collection event: follow the carrier's delivery notice rather than waiting for a transit update.
- A network exception with no action requested: check service alerts and the revised estimate, then seek an investigation if the shipment remains overdue.
- A handoff to another carrier: check the destination carrier's tracking page before concluding that all updates have stopped.
Contact the seller first when tracking shows only label creation [2]. For an investigation or claim, ask whether the sender must initiate the process; carrier investigations and purchase-related remedies are separate processes, so check the retailer's applicable terms and any payment-provider deadlines rather than assuming a shipping inquiry preserves every other option [2]. A delay alone does not establish a universal refund entitlement [2].
Most cross-border purchases have three protection windows: the marketplace's item-not-received process, the carrier's loss or damage claim, which may be opened by the sender, and a payment-provider dispute [2]. The deadlines for each are set by the applicable terms and differ across platforms and services, so the terms on your own order are the numbers that count.
The cause is still open, and the risk repeats
Preliminary findings point to a single new router. Reuters, cited by CCTV, reported that the communications contractor L3Harris was upgrading old copper lines to fiber when the newly installed router began sending other routers floods of connection requests, more than 1,000 every four to five seconds, overloading the network and touching 17 of the 22 regional air traffic control centers [4]. CCTV reported the transport department's account: the router at an Arkansas facility broadcast data across the network on startup, the department disabled the broadcast function on 69 routers, and the fault then cleared [5]. What remains undetermined is whether the fault sat in the device itself or in the installation [4]. Duffy said there is no evidence maintenance staff sabotaged anything, and the FBI, the FAA and law enforcement agencies are participating in the investigation [5]. Statements that no cyberattack was involved came in November 13–15 reporting and stand only as of those statements [1] [3].
For a cross-border shopper, the reason to know this is recurrence. The US Government Accountability Office reported in September that more than 75 percent of 138 air traffic control systems were unsustainable or at risk, while controllers handle up to 45,000 flights a day on what the report called "old and unreliable technology" [1]. Some of the routers affected this week were bought in 2001 and were already obsolete by 2006 [5]. Reuters reported the FAA spends about one billion dollars a year maintaining legacy copper communications lines, and plans to retire the floppy disks still used at more than 400 facilities only by the end of 2028 [4]. A January 2023 system failure halted domestic departures for about two hours [1], and a September 2026 facility failure in Philadelphia left about 9,500 flights delayed or cancelled [4].
The bottom line for a parcel on a US transit line: the delay risk from this event is real, the recovery clock is measured in days rather than hours, and the root cause is still under investigation. The checking habit is the part that carries over: whatever causes the next disruption, its traces will land in the same event history you already know how to read.