Facing the same issue. From yesterday morning onwards after a commit that does not affect anything, tried by turning off the Vercel Authentication even though it was working earlier with Vercel Authentication. Asked the support bot it suggested it's related to the Vercel Screenshot Service. The fixes as per the bot did not seem to work, looking forward to any communication. No issues when viewing the deployed site for users and incognito.

Vercel Authentication -> Disabled

• Firewall Custom Rules -> 0 (none)

• Bot Protection -> Inactive

• Homepage has NO auth guards or route-level access control in code

• Homepage loads correctly in incognito mode (200 OK)

• Project name: v2-portfolio

• Framework: Next.js

• Plan: Hobby

• Last Working Deployment: Dk5GrntmL

• First broken deployment: ff86984 (chore: update tsconfig.json)

Hi,

My deployment thumbnails in the Vercel dashboard are showing "Error: Forbidden (403)", but my live site and custom domain work perfectly fine.

**Project:** danmu-api

**Framework:** Node.js

**Plan:** Hobby

**What I checked:**

- Vercel Authentication: Disabled

- Bot Protection: Inactive

- Custom Firewall Rules: 0

**Firewall Traffic logs show DDoS Mitigation is blocking these AWS IPs:**

- 18.145.252.166 (Amazon.com Inc, AS16509)

- 52.53.151.3 (Amazon.com Inc, AS16509)

- 54.67.140.255 (Amazon.com Inc, AS16509)

These appear to be Vercel's own thumbnail/screenshot service being blocked by DDoS Mitigation.

This was working fine before and started happening recently. Since I'm on Hobby plan, I don't have access to System Bypass Rules to whitelist these IPs manually.

Could someone help unblock these IPs or reset the DDoS Mitigation rule for my project?

Thank you.

Its the same for me too. Two days now my previews are broken and on top of that several users are getting denials from Vercel DDOS mitigation, including my self and my colleague. Since today I have 1 custom rule to

• Plan: Hobby

• Framework: Next.js

• Firewall Custom Rules -> 1

• Vercel Authentication -> Disabled

Exact same situation here I am also facing lot of random DDos mitigation issues for genuine traffic. Even my trusted frontend is getting denied to fetch resource from my backend !

Has anyone identified a solution for this issue? The Vercel team has not yet responded, and for the past few days, I have been unable to use my web application, with my APIs rendered entirely inoperable.

i have the same issue

I am facing the same issue.

any vercel stuff here to fix the issue?

It's interesting how this could be an inter-vercel issue, I have the same problem now for a couple of days, and I also refactored my project into a turbo monorepo two days ago, and thought this is some problem with my refactor. Asked Codex to investigate, and it gave me a link to this thread. I want to add that the favicons also disappeared in vercel dashboard when the thumbnails started showing that Error 403 forbidden message instead of the actual home page screenshot.

I also have Bot protection and AI Bots management turned off for those projects, and i see DDoS protection invoked by agent `Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/141.0.7390.0 Safari/537.36` trying to access / coming from Amazon.com, Inc IPs

I have the same problem

same issue here

same issue here, 2 projects now

Facebook's link-preview crawler (facebookexternalhit) returns 403 on the apex domain https://wellow.fyi, while every other social crawler I've tested (Twitterbot, Slackbot, LinkedInBot, Discordbot, WhatsApp) returns 200 from the same host with the same path. From my own IP using curl -A "facebookexternalhit/1.1" I also get 200, which means the 403 only fires for traffic actually coming from Meta's crawler IP range — pointing at edge-side IP-level treatment that I have no project-level setting to control. This is breaking Instagram DM and Facebook link previews for the site. I've already gone through the obvious checklist and ruled everything out (details below) — appears to be something Meta-IP- specific at Vercel's edge.

Current:

• Facebook Sharing Debugger reports "Bad Response Code: 403" on https://wellow.fyi (and on cache-busted variants like
  https://wellow.fyi/?v=fbtest)

Wellow

Wellow · Capitalize on your conviction — from belief to a researchable thesis, in 30 seconds

Capitalize on your conviction. Type what you believe; in 30 seconds Wellow returns a structured thesis: ranked tickers, an exposure map, the risks that would break it, and the live data you'd watch to prove or falsify it.

• Debugger UI suggests "could be due to a robots.txt block" — but
  robots.txt is permissive (see below) so that's a misleading hint
• All other social crawler user agents return 200 from the same URL

Expected:

• facebookexternalhit gets 200 with our OG metadata, same as every
  other crawler. Instagram/Facebook link previews populate.

Project name: wellow-research Production URL: https://wellow.fyi Framework: Next.js 16 (App Router, Turbopack) Plan: Hobby Region: iad1 (US East) Deployment: latest commit on main DNS: apex A → 216.198.79.1, www → CNAME to vercel-dns (managed via GoDaddy) Reproduction URL for FB debugger: https://developers.facebook.com/tools/debug/?q=https%3A%2F%2Fwellow.fyi

Thank you for bringing this to our attention. To ensure this is investigated with the necessary priority and privacy, please report all security-related concerns, potential exploits, or abuse directly to the Vercel Security Team.

Please submit your report here: vercel.com/abuse

Reporting via this official channel is the fastest way to reach our security engineers and ensures that sensitive information is handled in a secure environment rather than a public forum.

Hi everyone,

I'm facing an issue with the screenshot preview in Vercel. My project is a simple static site (HTML, CSS, JS), and the deployment itself works perfectly --- the site is accessible and returns 200 OK.

However, in the Vercel dashboard, the screenshot preview shows "403 Forbidden".

Details:

• Project type: Static (no backend, no middleware, no vercel.json)

• Deployment status: Successful

• Site accessibility: Works fine in browser

• curl -I result:

  1
  HTTP/1.1 200 OK
  2
  X-Vercel-Cache: HIT

• I did not implement any bot blocking, headers, or authentication

• Issue persists even after waiting several hours and redeploying

What I've tried:

• Redeploying (with and without cache)

• Creating a fresh deployment

• Verifying there's no custom config or blocking logic

Question:

Is this a known issue or limitation with the preview screenshot system? Is there any way to force the preview to regenerate correctly?

Any clarification would help. Thanks.

I have the same problem, teamId: team_2jxmmbnhn2iFUrqcEGgXB72x

Hey folks! I grouped all your posts into this one as they all seem similar. Are you still seeing this?

Thank you for bringing this to our attention. To ensure this is investigated with the necessary priority and privacy, please report all security-related concerns, potential exploits, or abuse directly to the Vercel Security Team.

Please submit your report here: vercel.com/abuse

Reporting via this official channel is the fastest way to reach our security engineers and ensures that sensitive information is handled in a secure environment rather than a public forum.

Could you also check for my team id: team_XJBpvXQh7yqC77Vl2fLQQs0C

I'm having the same issue on multiple of my websites

I'm experiencing the same issue. Could you please help me resolve it asap? All V0 deployments on my website are returning a 403 Forbidden error.

Yes, I am still getting the same issue. 403 on the vercel preview and facebook.

Same issue here.

Hi @anshumanb, I have encountered the same problem with my account. Would you mind checking and fixing it for me?

my team id: `team_8dflfLwBd9a5NzsgKJzlr8Gw`

Hi @firehiwotk21-7699, our team is looking into it.

Hi Anshuman,

I'm still experiencing the issue on my website and would appreciate it if you could resolve it as soon as possible.

We are currently encountering a 403 error, and it's affecting the functionality of our website. As the site includes multiple v0 deployments, the issue appears to be related to v0 and is causing significant disruption.

Please look into this urgently and let me know if you need any additional information.

@pawlean, @anshumanb

It would be awesome if you guys could provide some feedback.

Thank you!

Hi, could you please look into my issue? Thank you.

@anshumanb shouldn't this be an incident?

I see many people keep reporting their website not being accessible. If possible could you explain what the problem is? It's also quite hard to understand what is going on.

Do you also have 403 forbidden error on your v0 deployments on the website? We tried to enable this, but this didn't help.

Same issue here. Preview not showing at all, have tried to restart sandbox, error persists for all projects. Receive forbidden message as well. Sandbox unable to restart.

Have not been able to access projects in three days now.

Hi there, could you all also post the URL or project ID here so we can inspect further into this?

Thank you for the timely reply.

Also I want to point out that other than the thumbnail problem, occasionally trying to navigate to the love site will return the same 403 error with x-vercel-mitigation: deny

Affected projects:

Website URL_PROD: https://virtality.app/ URL_DEV: https://preview-web.virtality.app/ project_id: prj_rc5BFp0xvMFl0H4MRxagfDFgqqza

Console

URL_PROD: https://console.virtality.app/ URL_DEV: https://preview-console.virtality.app/ project_id: prj_3y92gys0Mpn3wRyxcIBTHmg1oWnS

Adminboard

URL_PROD: https://admin.virtality.app/ URL_DEV: https://preview-admin.virtality.app/ project_id: prj_xb4stgRZMWNqVvMbK49OENguQZjT

Service

URL_PROD: https://service.virtality.app/ URL_DEV: https://preview-service.virtality.app/ project_id: prj_826x7kqdRrMafKnyEgZNvQ8zkogq

Hi @steliospne, thanks for updating the post here. I'll pass this information to our team. Could you grab the request ID and time next time (with timezone) you see a 403? This will help us identify the issue better.

Hi @tobiaslucius-clarke, welcome to the Vercel Community!

I'm sorry you're facing this issue. Could you share the chat ID? Also, if you can check the network tab it may have request ID information that can help us debug the issue better.

Hi @marcocaldera & @lenagryn-9120, I understand this isn't ideal. If you could provide me the project IDs and URLs where you see the issues, it'll help. Also, the next time you see the 403, please share the request IDs from the browser network tab and the time (with timezone) as it'll help us debug this issue.

Our team is actively looking into this but need more information to better help you as some errors might be unrelated and confusing.

Thanks for your reply. The problem is happening at the website - https://adfin.com/ . Specifically on the pages: 1. https://adfin.com/ 2. https://adfin.com/accountants 3. https://adfin.com/businesses 4. https://adfin.com/generate-invoices 5. https://adfin.com/accept-payments 5. https://adfin.com/direct-debit-payments

Please find all the projects that have 403 issue:

1. https://v0-finbro-dashboard-etzbnp016-lenagryn-9120s-projects.vercel.app/
2. https://v0-invoice-capture-prototype-d4pg9nmc9-lenagryn-9120s-projects.vercel.app/
3. v0-screen-2-3pyda35j9-lenagryn-9120s-projects.vercel.app
4. https://v0-white-window-design-bhyzs01rm-lenagryn-9120s-projects.vercel.app/
5. v0-replicate-prototye-g2dpalukj-lenagryn-9120s-projects.vercel.app
6. v0-project-design-specifications-8ygfsboyy.vercel.app
7. https://v0-direct-debit-animation-3oxmq8qr2-lenagryn-9120s-projects.vercel.app/

The following request was made from the Netherlands. Hope this is helpful.

Here is the ChatID: healthcare-quote-mockup-cq69YuHO6bv

Here is more info from the network tab:

Team id: team_XJBpvXQh7yqC77Vl2fLQQs0C

Websites:

https://business.playtoreveal.app/

prj_H0SRL4sLzXuOTLXVrIpkb2sZ2BI8

https://campaign.playtoreveal.app/

prj_DfwWB8E7B2iXkO4f1dV0nNfiiboj

Example of request id: ID: fra1::llrb7-1778071890806-597ac585cf09

Facing the same issue

Here is my project id :prj_3cXdYckaselmSgh3cuzb51fvcg6I

And here is the url of project : https://1dreamscape-creation.vercel.app/

1dreamscape-creation.vercel.app

Dreamscape Creations

Dreamscape Creations E-commerce

Hello, facing he same issue

project id: prj_bnz82LTYwqDGc9fVLuqsIDhgynw9 urls:

https://tierarztmobilerdulovic.vercel.app/

https://www.tierarztmobilerdulovic.de/

Hi Anshuman, could you please let me know when we can expect a resolution to this issue? Our website is still not functional due to the V0 403 errors. It has already been 3 days, and we still haven't received any recommendations or a solution to the issue. Please resolve this ASAP.

Hey @anshumanb do you have an update?

Any updates on the solution?

My project url: clsbooking.com

Hi, do you have any update re the problem?

Hello, I am also facing the same issue it's a been a week like this, could you help me out, I do not use the Rules or have set any custom ones, the dashboard preview for my project is the only thing that seems to be broken.

Hi everyone, I understand that this has been less than ideal. I've escalated this issue with our team.

In the mean time, if you're using domain fronting on these projects, try turning it off because are actively restricting projects using this to ensure high security measures.

Update: Our team is actively working on a fix.

If your project was created before 2026-01-01, redeploying it should unblock you in the meantime.

yes i am still seeing this issue!

I am having the same issue to my 5 projects.

Just checking if there was any solutions for this issue ...

I'm having the same issue. I deleted that project and started a new one, but it's still the same.

I'm having the same issue, it's really hurting my trust in Vercel. These 403 issues started happening to me around a week ago, randomly everywhere.

My projects are getting X-Vercel-Mitigated: deny responses when loaded in an iframe from adfin.com. I need to whitelist iframe requests from my domain.

Are you guys all on the free tier or are you paying for Vercel? I'm a bit concerned because I want to switch to the paid version once my project are advertised to customers but if I risk to have my website unavailable for 1+ weeks I need to reconsider my risks and choices.

@anshumanb do we have any updates on the 403 issue? Because now 403 are randomly appearing on my live site too. And it's blocking my own home IP and I don't know for what reason.

Hi everyone, did anyone try this fix in the meantime? Let me check the status of the fix deployment.

Your proposed solution didn't work. Please fix the problem with V0 iframes on adfin.com. We have already been waiting for a week for a resolution!

Anshuman We have a Series A announcement tomorrow, and if our website has widespread 403 issues with v0 iframes, it would be a very bad sign for our customers. We kindly ask you to prioritise this issue highly and resolve it today.

Hi Anshuman, unfortunately the proposed solution didn't fix the issue.

Further observation indicates that after every deployment the issue worsen and after some minutes it becomes better but not resolved.

My main issue is that the forbidden errors are an predictable and I have no way to know how many users are affected since the "blocking" happens before they even reach the app.

Finally, other account projects are working as intented, only the business critical projects are affected...

What is the solution here, can you revert until you figure it. Our clients are complaining and we have nothing to do except move to other vendors.

Hello! Been getting them in all my projects too, its random and appears randomly across devices and browser types

I'm experiencing the same issue, reported it here https://community.vercel.com/t/deployment-thumbnail-shows-error-forbidden-403-live-site-works-fine/40244

Vercel Community

Deployment thumbnail shows "Error: Forbidden (403)" — live site works fine

Current vs Expected Behavior: Currently, all deployment thumbnails show "Error: Forbidden (403)" in the Vercel dashboard preview starting from commit f6d7fc7...

Same issue seen here. Please advise how to fix! This is impacting our upcoming product launch.

It seems to be fine now for me.

Hi everyone, our team has confirmed that a fix has been deployed for this issue. No actions are needed on your end.

Let us know here with URLs and request IDs if you face it.

I just redeployed my project and now its working fine .Thank you so much for your help

It's working now! Thank you

Thank you very much!!! Yes, all fixed!!! @anshumanb you're a rockstar!

Hi @anshumanb I am still facing the issue, URL: https://staging.bloowatch.com/en/ecommerce/booking/terms ID: fra1::cblxg-1778679657263-07ed20da4c56

still facing same issue as well, not resolved.

Check the bot protection; I faced the same problem when it was on, I changed it to log.

Hi @mohamedsaber19, sorry that you're facing this issue. Let me share the request ID with our team.

It is still not working for me either. this is the link REDACTED. it's broken inside the iframe but works in a separate browser tab

I have the same problem with my website docs https://enumhq.com/docs and https://enumhq.com/blog