DatoCMS: Builds failing on Vercel (or near San Jose California USA)

What to do

Check whether you use DatoCMS in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2023-05-01 17:34 UTC and 2023-05-01 17:34 UTC may need a replay.
Subscribe to DatoCMS's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=datocms works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

resolvedMay 1, 2023, 5:34 PM UTC
Resolved — A fix has been implemented by Fastly Identified — We have received reports from our customers of failing builds on Vercel with error 502 I/O Error while performing requests to graphql.datocms.com It looks like that our CDN provider (Fastly) has an open issue related to the San Jose California datacenter: https://www.fastlystatus.com/incident/375837 Since Vercel is building your projects from San Francisco, it's very likely that they will end to the San Jose California (SJC) Fastly datacenter. This is not related to Vercel. You might get these errors if you build your project in California.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is DatoCMS still down?

No, this incident was resolved 2023-05-01 17:34 UTC. For DatoCMS's live state, see https://down.guide/datocms.

How long did it last?

0m, from 2023-05-01 17:34 UTC to 2023-05-01 17:34 UTC, by the times DatoCMS posted.

What was affected?

DatoCMS named in us.

What caused it?

DatoCMS hasn't published a root cause. If it does, it shows here.

Where does this come from?

DatoCMS's official status page, https://status.datocms.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.