Missing GitHub data

What to do

• Check whether you use Vanta 3rd Party Integrations. 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 3d 22h it lasted.

  Anything that failed between 2026-04-27 18:56 UTC and 2026-05-01 17:42 UTC may need a replay.

• Subscribe to Vanta's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=vanta works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Vanta 4

1. identifiedApr 27, 2026, 6:56 PM UTC

   We've identified an issue that may cause GitHub Pull Requests, Issues, and Dependabot vulnerabilities not to appear in Vanta and may affect the status of related tests. The root cause is a downstream GitHub incident (https://www.githubstatus.com/incidents/ql942tw29yl6). We are working on mitigation.

   provider

2. identifiedApr 28, 2026, 3:27 AM UTC

   The underlying GitHub incident has been resolved, and GitHub data in Vanta is gradually being restored. We expect the remaining missing data to be restored within the next few hours, and we will finish the remaining remediation actions in the morning.

   provider

3. identifiedApr 28, 2026, 5:31 PM UTC

   A follow-up GitHub incident (https://www.githubstatus.com/incidents/x69zbgdyfzg0) is now active, which may be causing missing Pull Request data in Vanta. We're waiting for this to be resolved before completing the final mitigation steps.

   provider

4. resolvedMay 1, 2026, 5:42 PM UTC

   The underlying GitHub incidents have been resolved, and remediation steps on Vanta's end are complete.

   provider

Corrections

None so far.

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