GitHub's October 29 changelog says new IP ranges for github.com webhook deliveries are now included in the hooks field of the Meta API. The ranges apply across GitHub.com plans, including GitHub Enterprise Cloud.

What maintainers should check

  • If a firewall uses a hand-maintained webhook allowlist, add the current ranges from the official Meta API.
  • If automation already refreshes that API data, GitHub says no change is needed for this addition.
  • Do not assume the published list is permanent; fetch the current values when updating an allowlist.

An allowlist that falls behind can reject legitimate webhook deliveries. Monitoring delivery failures and keeping the source of network ranges automated reduces that operational risk.

Use GitHub's Meta API and webhook guidance as the authoritative reference rather than copying an address list into a long-lived configuration.