Amazon Delivered My Package to an Address I Haven't Lived at in 14 Years

Either I'm losing my mind, or something weird happened. So I did what any reasonable person would do: analyzed 24 years of order history.

$123.77

Gone. Poof. Delivered to strangers who probably think I'm very generous.

The Case for My Sanity

Look, I know what you're thinking: "You probably just selected the wrong address, dummy." Fair. But consider the following:

290
Orders I successfully navigated to my current address since 2016
(392 items)
0
Orders I shipped to Greenwich St when I actually lived there (2012)
1
Order that somehow found its way to Greenwich St in 2026
(4 items)
67
Days between my last successful order and this... incident

The Scene of the Crime (Allegedly)

My Billing Address (Correct)
Pheasant Dr
Petaluma, CA

Where I've lived for 10 years

→ ? →↓ ? ↓
Where Amazon Shipped It
Greenwich St
San Francisco, CA

Haven't lived here since 2012

The Puzzle

My billing address was correct - so my account was fine. But somehow, the shipping address defaulted to an address from 14 years ago. An address I never even used for deliveries when I lived there. Did I fat-finger it? Did I have a senior moment at 42? Or did something else happen?

The Damage

Order ID: 113-6513585-7023465

Items: 4 (now presumably enjoyed by confused San Franciscans)

Total: $123.77

Plot Twist: I Never Even Got Packages There

Here's where it gets weird. Even when Greenwich St was my billing address back in 2012, I always shipped packages elsewhere - usually to my office. Why? Because it was a split-level row house right on the street with nowhere safe to leave a package. Porch pirates would've had a field day.

9 Orders with Greenwich St as Billing Address (2012)

Every single one shipped somewhere else:

  • My work address in SF
  • Other Oakland addresses (when I moved)
  • Family in Virginia

Packages actually delivered to Greenwich St: 0

So Greenwich St was never a delivery address for me. Not once. Not ever. Which makes it a pretty strange choice for Amazon to suddenly decide it's my default in 2026, no?

Exhibit A Through D (Yes, I Went Full Detective)

I may have gotten a little obsessive. Here's what my Amazon app looked like right after I didn't get my package:

1. My "Default" Address is... Wrong?

Greenwich St is set as my "Default: amazon" address. I haven't lived there since 2012. I never shipped packages there. And yet, here we are.

Amazon app showing Greenwich St incorrectly set as default address

2. This Grocery Thing is New, Right?

At checkout, I now get this grocery upsell screen. I don't remember seeing this before, but honestly, who pays attention to these things? (This is me acknowledging I might have missed something.)

New grocery interstitial screen with Continue to checkout button

3. Checkout Defaults to Wrong Address

After that screen, here's checkout. Notice it defaults to Greenwich St. The question is: did I manually change this to my correct address 290 times over 10 years, or was it just... defaulting correctly until recently?

Checkout screen showing order defaulting to wrong Greenwich St address

4. The Warning I Never Saw

When you manually change your address, Amazon shows this big blue warning. I definitely would have noticed this. But I never saw it - which suggests I didn't change anything.

Address change prompt showing warning message that appears when user changes address

My Theory (And I Stress: Theory)

Screenshot #4 shows Amazon does warn you when addresses change. I never saw this warning. So either I've been unconsciously changing my address back to Petaluma for 290 orders without ever noticing the warning, or... something changed on Amazon's end. Occam's razor suggests I'm not that oblivious. But you be the judge.

My Entire Address History (Yes, I Graphed It)

The Suspicious 67-Day Gap

Between my last successful order and this fiasco, Amazon released three iOS app updates. All of them mention changes to "account and order information." Coincidence? Maybe! Let's investigate:

April 20, 2026
Amazon iOS v27.8.0 released
April 28, 2026
Last successful delivery to Pheasant Dr, Petaluma (the good times)
May 4, 2026
Amazon iOS v27.9.0 SUSPECT #1
May 18, 2026
Amazon iOS v27.10.0 SUSPECT #2
June 11, 2026
Amazon iOS v27.11.2 SUSPECT #3
July 5, 2026
Package goes rogue - ships to 2012

The Prime Suspects

All three updates share identical release notes: "Our new design provides easier access to the features you use most while on the go. This includes the homepage, account and order information, your cart..."

I can't prove which update (if any) caused this. But something changed my default shipping address to an ancient value I never even used for deliveries. That's... weird, right? I'm not crazy for thinking that's weird?

Amazon iOS App Version History showing updates on Apr 20, May 4, May 18, and Jun 11

The evidence. Or at least, evidence of something.

24 Years of Orders, Visualized

Notice that tiny red sliver in 2026? That's the problem.

The TL;DR (In Spreadsheet Form)

For those who skipped to the bottom (I don't blame you):

The Stat The Number
Years at my current address 10 years (2016-2026)
Orders successfully delivered there 290 orders (392 items)
Last time I lived at Greenwich St 2012 (14 years ago)
Orders I ever shipped to Greenwich St 0 (not even when I lived there)
Orders mysteriously sent there in 2026 1 order, 4 items ($123.77)

So... About That Refund

Look, I'm not saying it's definitely Amazon's fault. Maybe I did have a momentary lapse in judgment. Maybe I accidentally time-traveled to 2012 while placing my order. Maybe I'm just getting old.

But after 10 years and 290 successful orders, the data suggests something funky happened. And I'd really like my $123.77 back.

What do you say, Amazon?

I'm very nice and only mildly passive-aggressive. Feel free to reach out.