Netlify Problems & Issues

A user received a $104,000 bill after their free-tier site was DDoSed, with 60.7TB bandwidth in one day. Support initially offered to reduce it to $5,225 (5% of original). CEO eventually waived the bill after viral backlash. Raises concerns about unlimited liability on supposedly free plans.

Unlike competitors, Netlify has no way to set hard spending limits on paid plans. Users cannot cap their bill at a maximum amount. Traffic spikes or DDoS attacks can result in thousands in charges with no warning until after the fact.

If you exceed your plan's bandwidth limits, Netlify charges $55 per additional 100GB. A single viral post or DDoS attack could cost hundreds or thousands of dollars. Users report unexpected bills in the hundreds without prior warning.

Pro plan costs $19/member/month. For teams, this quickly becomes expensive compared to alternatives. A 10-person team pays $190+/month or $2,280+/year. Cloudflare Pages offers unlimited team members on their free tier.

New accounts use a credit-based pricing system introduced in September 2025. Users find the credit calculations confusing and struggle to predict their monthly costs. Different resources consume credits at different rates, making budgeting difficult.

When free plan sites exceed monthly limits (100GB bandwidth, 300 build minutes), all projects on your account are paused until next billing cycle. No grace period - site goes down immediately. Users only get notifications at 50%, 75%, and 100% usage.

When builds fail (even due to Netlify issues), the build minutes are still consumed from your allotment. Users report being charged for failed deployments caused by AI agents or platform bugs. Wasted credits on non-functional deployments.

Users report having their accounts blocked for clicking on the wrong sign-up method and not completing verification in time. Account recovery is difficult without responsive support, leaving sites inaccessible.

Default serverless functions timeout after 10 seconds, with Pro plans only extending to 26 seconds. Many operations (database queries, API calls, image processing) can't complete in time. Competitors offer longer timeouts or background functions more readily.

Build and deployment times on Netlify average 68+ seconds for Hugo sites, compared to 20-45 seconds on Vercel and 49 seconds on Cloudflare Pages. Slow builds waste developer time and delay updates reaching production.

Users report limited customer service availability, slow response times, and passive-aggressive responses on support forums. Free users get virtually no support. Even paid users report difficulty getting help with billing disputes and technical issues.

Users describe the cancellation process as an 'impossible navigational maze' with dark patterns everywhere. Settings buried deep in menus, multiple confirmation steps, and confusing options make it hard to actually close your account or downgrade.

The platform has many menus and options that take significant time to configure. Users report difficulty managing repositories - pulling the wrong repo creates duplicate sites that can't be easily fixed or removed. Dashboard navigation is overwhelming for new users.

Netlify lacks robust DDoS protection, which is concerning given the billing model. A DDoS attack can result in massive charges. Users are left vulnerable unless they implement external protection like Cloudflare, which adds complexity.

Netlify primarily supports frontend and static site deployment. You cannot deploy traditional backends on Netlify. For full-stack applications, you need to use serverless functions (with their limitations) or deploy backends elsewhere.