Vercel builds fail with connection error to graphql.datocms.com

🆘 Support
1

Since a few hours some of our Vercel hosted projects are failing during build, specifically during Nextjs static page collection. These projects are running Nextjs 15, others with Nextjs 16 and even 14 are building just fine. Build logs show this error:

[cause]: [Error: getaddrinfo ENOTFOUND graphql.datocms.com] {
  errno: -3008,
  code: 'ENOTFOUND',
  syscall: 'getaddrinfo',
  hostname: 'graphql.datocms.com'
}

I tried to force IPv4 connections via the NODE_OPTIONS environment variable but didn’t change anything. Also opened a support case at Vercel but in the meantime I want to ask here: Has there been a change in the last hours at DatoCMS that could affect networking with Vercel?

3

@dev7

Our nightly E2E deployment test for Vercel also broke around the same time, but it seems to have recovered now. Looks like it might’ve been a temporary network glitch. Could you please try again?

(We didn’t change anything either)

4

Thanks for confirming, our deployments started working again just shortly after I made the post :smiley: Will close this topic, thanks again!

1 Like
5

Just a quick follow-up: That same automatic deployment test we do failed again last night, but then retried and succeeded again a little while later. This suggests to me there is just some amount of flake involved in these systems, but I’m not sure where yet (ours or theirs or just some regional network thing).

I’ll keep an eye on it in case it keeps happening or increases in frequency/duration. For now, though, if a build fails, you can probably just retry again a few minutes later and it should work. As far as I can tell, it’s not anything to do with graphql.datocms.com in particular — we don’t have any other reports of failures outside of this one and our Vercel-specific E2E build test.