What happens when Amazon accidentally sends all of their support traffic your way?
Tags: devops, analytics, javascript, sre
Published: 2022-01-05 15:44:16

---
title: What happens when Amazon accidentally sends all of their support traffic your way?
published: true
description: A Typo leads to Amazon sending us a LOT of unexpected traffic ...
tags: devops, analytics,javascript, sre
cover_image: https://dev-to-uploads.s3.amazonaws.com/uploads/articles/pks8qitchwi06sm0xh7c.jpg
---

## Update: The issue has been resolved, but we still have no explanation as to what happened

A sudden massive spike in web traffic is something every tech startup dreams of (unless you’re on the SRE team). When it happened to us at [Openbase](https://openbase.com), we were thrilled. While we already take in ~400k visitors per month, we wanted to be thorough and dive into our analytics in order to find the source of all this new traffic, in hopes that we could capitalize on it and keep the trend going.

![A graph displaying a sudden increase in web traffic on GA](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/05q5alonc15w9cl3uk9b.png)

Unfortunately, this proved to be a little difficult to investigate. All of the traffic was direct, meaning that the sudden influx of users weren’t clicking on a viral tweet. Instead they were typing [openbase.com](https://openbase.com) directly into their browser URL bar - or so we thought. After a few mentions of this during our morning standup meetings, and a cursory glance at the horizon for unsolicited “Go to Openbase.com right now” billboards, the investigation took a backseat while we went back to the typical startup stuff. New features, improving the world of open source, building Yelp for package discovery, etc.

Then the strange support tickets started flowing in. “FireTV not working”. “My package came but it’s broken”. “We redeemed an Amazon gift card and wanted the money back on the card.” - Okay perhaps that last one (which is entirely real) was a bit of a helpful clue.

For some reason, Amazon support requests were coming to us.

![Gif of Ryan Reynolds saying "But Why?"](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/vspiu0jahhqsh4lh5obw.gif)

At first glance, Openbase.com doesn't share any similarities with Amazon.com. To start, we’re not an ecommerce brand, we’re an open source package search and discovery platform. “A” and “O” are very far apart from each other on a standard QWERTY keyboard. Why then were we getting a 900% increase in direct traffic from angry Amazon.com customers?

After pouring through all of our analytics services, logs, and anything else we could think of, we still had nothing. Finally, through a third party SEO service, we found a new backlink - http://amazom.com - which redirects to [https://openbase.com](https://openbase.com). Surprisingly, this link isn’t just the result of fat-fingering, a quick google search will reveal this typo exists all across the web.

![A whois record showing Amazon ownership](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/56jjr929cyzwl3elrxci.png)

Here’s where things get really strange - Amazon owns this domain. Why does it redirect to us at Openbase? Is it possible that the almighty DevOps at Amazon love Openbase SO MUCH?  Why did the traffic start pouring in on December 4th? Why did one of Kaitlyn’s 2 pack color changing mugs arrive broken in the box?  We don’t know. We’ve reached out to Amazon for clarification, and are excited for (but certainly not expecting) an explanation.

We’ve learned a few things from this ordeal:

1. Always investigate traffic spikes thoroughly
2. Angry users understandably don’t care that Openbase.com looks nothing like Amazon
3. Double boxing, along with plenty of styrofoam and bubble wrap isn’t always enough to ensure mugs don’t break in transit. While we don’t do any shipping here at Openbase, we do care very deeply about open source packages, so be sure to start your search for tools, frameworks, and libraries at [openbase.com](https://openbase.com)