Neon integration branch creation timeout and access denied errors on Vercel

Help
1

Hi everyone,

We’ve been completely blocked for 48+ hours due to issues with the Neon integration.

Symptoms:

  • Branch creation times out (~2m49s) on every preview deployment
  • Access denied when clicking Open in Neon from Vercel dashboard
  • I’m the owner of the Vercel project but can’t access the linked Neon organization

Support responses:

  • Vercel support closed my ticket and told me to contact Neon
  • Neon support confirmed the org is “managed by Vercel” and opened a case on Vercel’s side

So I’m stuck in the middle with no resolution.

Questions:

  • Anyone else experiencing this since Jan 13?
  • Is there a way to “unlink” a Vercel-managed Neon organization and regain control without losing the database?

This is a production app with paying customers. Any help appreciated.

4

Hi @quentin-4242, welcome to the Vercel Community!

I’m sorry that you are facing this issue.

Can you share the team slug in question with the neon db name and project IDs/preview deployment IDs for the Vercel project using the db?

5

Hi, thanks for looking into this!

Here are the details:

  • Team slug: eagr/app

  • Neon db name: eagr-neon-db

  • Vercel Project ID: prj_lM8Arf3Dc6Nz8pq2KE2aaz5r7GNt

  • Failed deployment IDs: [ajoute 2-3 IDs de deploys qui ont timeout]

Let me know if you need anything else.

1 Like
6

Thanks. Seems like you mistakingly missed the deployment IDs.

8

Sorry, here’s a failed deployment ID (last one):

  • ZoCNTiRA828oeakyhPW3YCsu5SP7

Let me know if you need more.

1 Like
9

I’m checking the timeout issue with our engineers. But, in the meantime can you share a screenshot of “Open in Neon” error that you see? Maybe a GIF or screengrab. Because as an owner you should that flow should work.

For me, even if I go directly to Neon and login with same email as with my Vercel account, I see the projects and teams on Neon dashboard.

10

The situation has changed slightly:

My colleagues re-invited me to the Neon project, so I no longer see the “Access denied” error when clicking “Open in Neon” while logged in.

However:

  • I’m only a collaborator, not an admin

  • I am the owner of the Vercel project but don’t have admin rights on the linked Neon organization

To reproduce the original issue: When I try the flow in a private browser window (login to Vercel → click “Open in Neon”), I land on an “Unauthorized” page. See screenshot attached.

This confirms there’s something broken in how Vercel passes authentication to Neon for this integration.

Screenshot at Jan 15 10-54-37
Screenshot at Jan 15 10-54-375246×582 109 KB

1 Like
11

Hi @quentin-4242, I got a confirmation that the underlying issue was resolved today. Can you check in your project if the deployments are working?

Can you also retry this today:

When I try the flow in a private browser window (login to Vercel → click “Open in Neon”), I land on an “Unauthorized” page. See screenshot attached.

12

Hi,

Yes, I confirm that everything is working now.

Thank you all for your assistance!

1 Like
13

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.