#cdn

Jacob Paris Can you share what version of Next.js you're on? Next 16 uses Turbopack instead of Webpack so you shouldn't be getting errors like this on up to date versions

Ngoiyaeric I fixed it with sse-error-extension-conflict

Alexey Ryabov it has been fixed by Vercel team.

Amy Egan Hey there. I know this post is pretty old, but wanted to share some info in case it helps (hopefully you've already solved it). 3 million in seconds definitely doesn't seem like normal usage so that could be a DDoS attack. Whenever you see something like that happening, you can enable Attack Mode. It will challenge all visitors with a verification screen while allowing legitimate users through. It's free and requests blocked by it don't count toward your usage. You can also investigate traffic in your dashboard to see what's hitting your site. Look for patterns in user agents, IP addresses, or specific routes being targeted. For protection going forward, you can set up with spend limits and consider adding custom firewall rules to block specific bad actors. For spikes in legitimate traffic, there's also a new Flat Rate CDN option that gives you a fixed monthly price. It covers traffic spikes for CDN Requests, Fast Data Transfer, Blob Data Transfer, and Observability events generated by CDN requests to prevent surprise bills. https://vercel.com/blog/introducing-flat-rate-cdn

system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. https://vercel.com/docs/domains/troubleshooting

Pauline P. Narvas Hey, @suheb! Feel free to share more details about your project, it'd help us tailor our suggestions, but some ideas to get you started: **Bundle Size Optimization** - Use `<@next>` `/bundle-analyzer` to identify large dependencies: `ANALYZE=true npm run build` - Enable `optimizePackageImports` in next.config.js for icon/utility libraries - Implement code splitting and lazy loading for non-critical components - Tree-shake unused code and remove unnecessary dependencies **Image Optimization** - Use Next.js `<Image>` component for automatic optimization - Images are served in modern formats (WebP/AVIF) reducing size by 25-35% - Enable lazy loading and use `sizes` prop for responsive images - Consider using a CDN for very large image libraries **Build & Deployment Speed** - Leverage Vercel's build cache (enabled by default) - Use Turborepo for monorepos to cache and parallelize builds - Consider enhanced build machines for large projects (up to 70% faster) - Enable Turbopack for faster local development Let us know how you get on!

Ryu A good way to approach this is to separate build/deployment size from runtime loading performance. For deployment/build size: * Remove unused dependencies. * Check for large assets accidentally included in the repo. * Avoid bundling server-only packages into client components. * Use dynamic imports for heavy UI/client-only code. * Keep generated files, uploads, and local cache folders out of the deployment. For page performance: * Use `next/image` for images. * Compress large images before uploading them. * Lazy-load below-the-fold components where it makes sense. * Check bundle size with a bundle analyzer. * Use Vercel Speed Insights or Web Vitals to see what is actually slow. The most useful first step is usually to identify the biggest files/dependencies instead of guessing. Once you know whether the problem is large assets, heavy JS, or slow server/data fetching, the fix is much clearer.

Pauline P. Narvas Hey, tools! Welcome to the Vercel Community. Could you go through these steps so that we can pass it on the right team to debug? https://community.vercel.com/t/resolving-ip-blocking-issues/171

system Hey @tools-2714! 👋 Just wanted to follow up here. If you've found a solution or still need help, let us know! We're happy to continue assisting.

Ryu Hi Operendia, Your evidence points away from the app upload code and toward the public Blob serving path. If the Blob API can list the object with `HTTP 200`, but the direct public URL returns: ``` 503 SERVICE_UNAVAILABLE X-Vercel-Error: SERVICE_UNAVAILABLE Body: The deployment is currently unavailable ``` then this is not a normal “file missing” case. A missing blob would be a different kind of failure, and your URL format also matches the public Blob URL format Vercel documents: https://vercel.com/docs/vercel-blob/public-storage I’d do one isolation test before escalating it as store-specific: ``` 1. Create a brand-new public Blob store in the same team 2. Upload one tiny test image/text file with access: "public" 3. Open the returned public URL directly with curl -I ``` If the new store works but `pywla5knjbnow7ji.public.blob.vercel-storage.com` still returns 503 for every object, that strongly suggests the old store’s public serving layer is stuck or unavailable. If the new store also returns 503, then I’d check whether the team/project is paused, blocked, or over a Blob usage limit, because that would affect serving even if the token can still perform some API operations. The useful escalation summary would be: ``` Store ID: pywla5knjbnow7ji Blob API list/upload: 200 Public blob URL: 503 SERVICE_UNAVAILABLE Affects all blobs, old and new Tested from multiple networks Latest X-Vercel-Id: Latest timestamp: New public Blob store test result: Team/project paused or usage-limit banner: yes/no ``` Do not post the `BLOB_READ_WRITE_TOKEN`, but the public blob URL, `X-Vercel-Id`, and timestamp are safe and useful for Vercel to correlate.

Anshuman Bhardwaj Hi @schutzworks, welcome to the Vercel Community! Can you try setting the header value in `vercel.json` to an empty string? https://vercel.com/docs/project-configuration/vercel-json#headers

system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. https://community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

Amy Egan Just tested it and saw it's returning a 404 with code `NOT_FOUND` rather than `DEPLOYMENT_NOT_FOUND`. That means the deployment exists, but the page you expected doesn't. Please use the debugging steps linked above to figure out why that's happening

Ryu Hi Devansh, If those Sentry events cluster around deploy times, I’d treat this as version skew first. With `dynamic(() => import(...), { ssr: false })`, the browser may not request that CSS/JS chunk until later. If the user loaded HTML/JS from an older deployment, then a new production deployment goes live, that old client can later try to fetch a chunk URL that no longer exists on the deployment it is being routed to. That usually shows up as: ``` Loading CSS chunk failed /_next/static/css/<hash>.css ``` A good way to confirm is to check the failed asset request in Sentry or browser devtools: ``` status: 404 or failed network request url: /_next/static/css/... time: close to a new deployment ``` I’d also compare one failed chunk URL directly: ``` curl -I https://your-domain.com/_next/static/css/FAILED_HASH.css ``` If it returns `404`, and the event happened after a deployment, that strongly points to stale client/runtime vs new deployment assets rather than a normal React error. A few mitigations I’d check: * enable/verify Vercel Skew Protection if your plan/project supports it * make sure HTML/RSC responses are not being cached by an extra CDN/proxy in front of Vercel * do not override caching for `/_next/static/*` * keep deployment retention / skew max age long enough for typical user sessions * add a one-time reload fallback for chunk-load failures so users recover instead of staying on a broken page Vercel’s Skew Protection docs describe the exact problem: keeping framework-managed JS/CSS/data requests pinned to the deployment that served the original page: https://vercel.com/docs/skew-protection I would not remove `dynamic()` just because of this. Dynamic imports can make the issue more visible because chunks are requested later, but the underlying thing to prove is whether the failed CSS URL is from an older deployment and returning 404 after rollout.

system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. https://vercel.com/docs/projects/domains/troubleshooting You can also use v0 to narrow down the possibilities.

SkyMesh Dynamics ah, then I'm not the only one who reported this

Ryu Hi Yuze, Your `openssl` test is a good way to narrow it down. Since this fails when the trailing dot is included in SNI: ``` echo | openssl s_client -connect deckclip.app:443 -servername 'deckclip.app.' ``` but works without it: ``` echo | openssl s_client -connect deckclip.app:443 -servername 'deckclip.app' ``` then this is happening before your Next.js app or `vercel.json` redirects can run. So I don’t think there’s an app-level redirect/header fix for the HTTPS case. A trailing dot is valid in DNS as an absolute/FQDN form, but TLS certificate/SNI matching is a separate layer. If Vercel’s edge does not normalize `deckclip.app.` to `deckclip.app` before selecting the certificate, the handshake can fail before any HTTP request exists. The practical workaround is to avoid generating or linking to the trailing-dot form anywhere in your app/canonical URLs. For users manually typing `https://deckclip.app``./`, there probably is not a project-side fix unless Vercel changes edge/SNI normalization behavior. The useful evidence to keep in the thread is exactly what you already have: same domain, same IP path, only the SNI value changes, and the trailing-dot SNI fails before HTTP.

system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. https://vercel.com/docs/projects/domains/troubleshooting You can also use v0 to narrow down the possibilities.

Agus 6148 did you ever figure it out? having the same issue

system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. https://vercel.com/docs/projects/domains/troubleshooting You can also use v0 to narrow down the possibilities.

Pauline P. Narvas In most cases, if you exceed your usage limits on the Hobby plan, you will have to wait 30 days before you can use the feature again.

mwask will all my projects be paused???

Longnguyenthanh075 5963 I am having the same issue as I approaching end limits of 10GB, the document said up to 10GB for Hobby plan and no mention of resetting as well. I am well past that 30-day period but have not see it resets. I checked with the CS bots from vercel it said the limit will be resetted.

Pauline P. Narvas Welcome to the Vercel Community! Cool project Vercel’s CDN supports HTTP/2 through ALPN negotiation. When testing with curl, try: `curl -I --http2-prior-knowledge https://reeflocal.io` The results are: ``` HTTP/2 200 accept-ranges: bytes access-control-allow-origin: * age: 69 cache-control: public, max-age=0, must-revalidate content-disposition: inline content-type: text/html; charset=utf-8 date: Fri, 17 Apr 2026 11:08:08 GMT etag: "4b264812b229d2b3a2943254c19261d8" last-modified: Fri, 17 Apr 2026 11:06:58 GMT server: Vercel strict-transport-security: max-age=63072000 x-vercel-cache: HIT x-vercel-id: lhr1::29hdk-1776424087993-d123805054ce content-length: 9145 ``` For Brotli/gzip compression, include the Accept-Encoding header: `curl -H "Accept-Encoding: gzip, br" -I https://reeflocal.io` I can see: ``` HTTP/2 200 access-control-allow-origin: * age: 108 cache-control: public, max-age=0, must-revalidate content-disposition: inline content-encoding: br content-type: text/html; charset=utf-8 date: Fri, 17 Apr 2026 11:08:46 GMT etag: W/"4b264812b229d2b3a2943254c19261d8" last-modified: Fri, 17 Apr 2026 11:06:58 GMT server: Vercel strict-transport-security: max-age=63072000 x-vercel-cache: HIT x-vercel-id: lhr1::f8fq6-1776424126886-571b3cb5b9a5 ``` If you’re behind a proxy, it might downgrade connections to HTTP/1.1. Test from a different network to confirm!

system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. https://vercel.com/docs/projects/domains/troubleshooting You can also use v0 to narrow down the possibilities.

Pauline P. Narvas We have a guide for this: https://vercel.com/kb/guide/resolve-err-too-many-redirects-when-using-cloudflare-proxy-with-vercel Let us know how you get on!

Pauline P. Narvas I recommend you check out: https://community.vercel.com/t/debugging-404-errors/437

Naimusshakib582 Pixel **"Thank you, Pawlean, for the detailed troubleshooting guide.** I have followed the steps you provided, but I believe the issue is related to **Edge Network Routing** rather than a standard 404 configuration error like a missing `index.html` or an incorrect build output. Here are the relevant details based on your guide: * **Domain Configuration:** My domain shows a **'Valid Configuration'** status in the Vercel dashboard. * **Observed Error:** I am getting **\[Mention the exact error here, e.g., a browser-specific DNS Error/No Response, OR the Vercel white 404 screen with its specific Code and ID if you see it\]**. It seems my site is not reaching the Vercel Edge Network successfully. * **Project Details:** For your internal review, the **Deployment URL** or **Project ID** is: **`https://onyx-drift-app-final-git-main-naimusshakib582-pixels-projects.vercel.app/ **Failing Custom Domain:** My custom domain is consistently showing the 404 error: 👉 **[Custom Domain]:** `https://www.onyx-drift.com/` (or `onyx-drift.com`) `** Could you please check the **routing and DNS propagation** for this specific deployment internally? Your help is greatly appreciated. Thank you."

Anshuman Bhardwaj Hi @ahmadsajid3470-5358, I'm happy that you're considering Vercel for your project. I think you can find some of the biggest New Media outlets on our https://vercel.com/customers page. If you optimize and cache your content properly, I think Vercel can take you very far. Let me know if you have specific questions.

Selçuk Çukur Yes, Vercel is definitely suitable for a gaming content and news site like yours. Since most of your pages are static (guides, updates, blog posts), Vercel’s global CDN will serve them super fast to visitors everywhere. * **Performance:** Static content is cached at the edge, so even during traffic spikes after big game updates, pages load quickly. * **SEO:** If you’re using Next.js or similar, server‑side rendering and fast response times help search engines index your content properly. * **Traffic handling:** You don’t need to worry about scaling servers — Vercel automatically handles spikes in traffic. * **CDN:** Built‑in CDN means your content is globally available without extra setup. In short, for a gaming news and guide site, Vercel gives you speed, scalability, and simplicity. If you add dynamic features later (comments, accounts, etc.), you can extend with serverless functions or external APIs.

Ahmad Sajid Thanks man this helps me.

Emma Taylor Great overview, thanks for sharing this. One thing I’ve noticed with Vercel is how much the edge network and image optimization help without extra configuration. Even basic projects feel faster once deployed. The preview deployments are also really useful for testing changes before going live, especially when working in a team. It reduces a lot of guesswork. This kind of summary is helpful for people who are new to Vercel and trying to understand where the performance gains actually come from.