USPS is in the middle of a multi-year network restructuring, and the honest version of what that means is: mail is slower and less predictable than it used to be, and it depends heavily on where it's going. We've written about why — but rather than just tell you it's true, this page shows it, using real transit data from actual TCGplayer PWE orders moving through the mailstream right now.

This isn't a sample or an estimate. It's every order that's actually entered the USPS mailstream through TCGHaulTracker in the last 60 days — meaning it's received at least one scan — aggregated by destination and compared against USPS's own expected transit windows for that distance.

11%
On pace
18%
Running slow
47%
Very slow
17%
Likely Delivered
6%
Not enough data
On pace Running slow Very slow Likely Delivered Not enough data
Methodology: Each dot is a destination ZIP3 cluster, scoped to PWE letter-mail orders that have entered the USPS mailstream (received at least one scan) — a barcode that hasn't been scanned yet isn't counted here at all, and package-label shipments are excluded entirely, since packages get real delivery-confirmation scans in a way letter mail mostly doesn't and would otherwise skew the picture. "On pace" means average delivery time for that destination is within USPS's expected transit window for its zone (based on DMM 604.5 distance thresholds), computed only from orders with a real observed delivery timestamp. "Running slow" is up to 30% over that window; "Very slow" is more than 30% over — same measured basis. "Likely Delivered" covers orders where USPS stopped reporting scans for 14+ days with no confirmed delivery event — we assume these delivered (the carrier just didn't report a final scan), but since that's an assumption rather than an observed timestamp, these are kept separate from the measured on-pace/slow/very-slow figures rather than forced into a speed category they weren't actually timed for. "Not enough data" means an order has entered the mailstream but hasn't resolved to any outcome yet — genuinely still in transit. Data is aggregated across every TCGHaulTracker user — no individual order, buyer, or address is identifiable from this map. Rolling 60-day window, refreshed roughly every 15 minutes.

Why this matters more than it used to

A slow network isn't something any tracking tool can fix — USPS's transit times are USPS's transit times, regardless of whose barcode is on the envelope. But there's a real difference between an order that's stuck and an order that's just slow, and right now, without scan data, most sellers can't tell which one they're looking at.

That's the actual problem this map is pointing at. If you're shipping into a "Very slow" zone above, an order going quiet for a week isn't necessarily bad news — it might just be normal for that lane right now. Without visibility into that, every quiet order looks the same: alarming. With it, you know which ones are actually worth worrying about.

  • Set buyer expectations by lane, not by guesswork. If a destination is running slow, you can say so before a buyer asks.
  • Tell the difference between slow and lost. A quiet order in an on-pace zone is a different situation than a quiet order in a very-slow one.
  • See it change over time. This map refreshes on a rolling 60-day window every ~15 minutes — as USPS's network shifts, so does this data, without you having to guess whether things have gotten better or worse.
This is the same data every TCGHaulTracker seller sees for their own orders — just aggregated across the whole platform here. Your own dashboard shows this broken down for your specific destinations, not just the platform-wide average.

Data shown reflects orders processed through TCGHaulTracker only and is not a claim about USPS performance generally — it's what we're actually seeing move through the mailstream. Last generated September 5, 2026 at 6:12 AM UTC.