Six days ago, MyClockTab.com was just what it started as: our first project, built with a focus on digital minimalism and a "time-in-tab" utility. It was running quietly in a corner of the internet.
Then, the "Hockey Stick" curve happened.
I don’t check our hosting logs every hour, but I do keep an eye on Google Analytics. Last week, the "Active Users" count started doing something it had never done before. Our baseline was about 50 users. Suddenly, that number started climbing. By the end of the 6th day, we had reached 24,000 total users.
The Reality Check
As the traffic surged, I started looking at the infrastructure. We were hosted on Vercel’s free tier. While Vercel is fantastic, I began to realize that for our first project, we needed a setup that could handle global scale without hitting serverless execution limits or bandwidth caps.
I decided to migrate the entire operation to Cloudflare Pages. No cold starts, unlimited bandwidth, and everything cached at the Edge. It sounded like the perfect long-term home.
The "522" Stress Test
Migrating a live site while people are actively using it is... stressful. Especially when it’s your first time doing it.
I updated the Nameservers and waited. Then, the screen in front of me started filling with errors instead of clocks. The DNS propagation felt like it was moving in slow motion.
The situation was a mess: one browser tab was showing a 404, another was showing a 522 Connection Timed Out. I knew there were people currently trying to access the site, and I was serving them a broken gateway page.
20 Minutes of Commands, 1 Hour of Silence
I spent about 20 minutes frantically running nslookup and dig commands, trying to figure out why the "Edge" felt more like a "Cliff."
Then came the one-hour wait—that painful silence where you hope it's just DNS propagation and not a fatal error you made in the config.
Finally, I found the culprit: I had pointed the DNS to Cloudflare, but I hadn't explicitly "claimed" and bound the custom domain inside the Cloudflare Pages project settings. It was like giving someone the address to your house but forgetting to unlock the front door.
I clicked "Bind Custom Domain," and within seconds, the site snapped back to life.
What This Taught Me
- Real Data is in the Analytics: If I hadn't checked Google Analytics, I might not have noticed the trend until we hit a hard limit.
- DNS is a Test of Patience: 20 minutes of work can easily turn into an hour of staring at a 522 screen.
- Scaling is about the "Next" 24,000: By moving to Cloudflare Pages, we’ve built a foundation that can handle the next spike without the panic we felt this time.
To our new users: Thanks for bearing with us during that hour of flickering screens. We’re still learning, but we're committed to keeping MyClockTab the cleanest, fastest clock on the web.
We want to hear from you. Now that the "pipes" are stable, I’ve added a tiny survey to the site. If you have a minute, tell us how you’re using MyClockTab. We’re building this for you. If you have a spare 60 seconds, click here to share your feedback and help us decide what we should build for the next 24,000 users.