Netlify Sent a $104k Bill for a Static Site: How to Avoid It

Imagine waking up, checking your email, and finding a $104,000 bill from Netlify for a static site. That's exactly what happened to one developer on Reddit, and the story went viral. Who wants to sell a kidney just to host some HTML pages?

How Did This Happen?

The issue stemmed from an unexpected traffic spike. A site that normally saw few visitors suddenly went viral. Netlify charges for bandwidth and serverless functions, and without proper limits, costs can skyrocket.

What went wrong:

• No budget alerts or traffic limits were set.
• Serverless functions were executed excessively due to bots or a DDoS attack.
• The developer didn't switch to a cheaper plan or enable CDN caching.

How to Protect Your Wallet

This case is a stark reminder for everyone using serverless platforms: always set spending limits. Most providers, including Netlify, Vercel, and AWS, offer budget alerts and caps.

Practical tips:

• Enable budget notifications.
• Use CDN caching to reduce origin load.
• For static sites, consider Netlify Edge Functions instead of serverless — they're cheaper.
• Monitor traffic analytics regularly.

Netlify will likely waive this bill (after the publicity), but relying on goodwill is not a strategy. Better safe than sorry.

METABYTE's take: This story perfectly illustrates why we always advise clients to set up monitoring and alerts early in development. Even a simple static site can become expensive if you don't keep an eye on infrastructure.