Skip to content

chore: update static IP for US and EU shared cloud#5750

Merged
PrestigePvP merged 1 commit intomainfrom
worktree-update-static-ips
Mar 18, 2026
Merged

chore: update static IP for US and EU shared cloud#5750
PrestigePvP merged 1 commit intomainfrom
worktree-update-static-ips

Conversation

@PrestigePvP
Copy link
Copy Markdown
Contributor

Context

  • Update US & EU prod IPv4 to match new infrastructure

Type

  • Fix
  • Feature
  • Improvement
  • Breaking
  • Docs
  • Chore

Checklist

  • Title follows the conventional commit format: type(scope): short description (scope is optional, e.g., fix: prevent crash on sync or fix(api): handle null response).
  • Tested locally
  • Updated docs (if needed)
  • Updated CLAUDE.md files (if needed)
  • Read the contributing guide

@maidul98
Copy link
Copy Markdown
Collaborator

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Mar 18, 2026

Greptile Summary

This PR updates the documented static egress IP addresses for Infisical's US and EU shared cloud regions to reflect new infrastructure. The change is documentation-only and affects one file.

  • US Region IPs updated: 3.213.63.16 / 54.164.68.73.215.209.139 / 100.55.172.40
  • EU Region IPs updated: 3.77.89.19 / 3.125.209.1893.72.169.163 / 51.102.78.137
  • The documentation itself contains a warning that IP changes are communicated with 60-day advance notice — please confirm customers were notified before the underlying infrastructure was switched.
  • The US IP 100.55.172.40 is worth verifying as a confirmed public egress IP, as 100.x.x.x addresses are atypical for cloud NAT/elastic IPs.

Confidence Score: 4/5

  • Safe to merge from a code perspective, but process compliance (60-day advance notice) and IP correctness should be verified before the infrastructure switch goes live.
  • This is a single-file documentation change with no code logic involved. The primary risks are operational: the 60-day advance notice commitment to customers and the unusual IP range of one of the new US addresses. Neither blocks merging the docs, but both warrant confirmation before the underlying infrastructure change takes effect.
  • docs/documentation/setup/networking.mdx — verify the new IPs, particularly 100.55.172.40, are correct public egress addresses and that the 60-day notice obligation has been met.

Important Files Changed

Filename Overview
docs/documentation/setup/networking.mdx Updates static egress IP addresses for US Region (3.213.63.16, 54.164.68.7 → 3.215.209.139, 100.55.172.40) and EU Region (3.77.89.19, 3.125.209.189 → 3.72.169.163, 51.102.78.137) to reflect new infrastructure.

Comments Outside Diff (1)

  1. docs/documentation/setup/networking.mdx, line 33-35 (link)

    P2 60-day advance notice policy vs. immediate IP change

    The warning on line 34 states that IP address changes will be communicated with 60-day advance notice. Customers who have whitelisted the old IPs (3.213.63.16, 54.164.68.7, 3.77.89.19, 3.125.209.189) in their firewall ingress rules will experience broken integrations as soon as the new IPs go live, unless they were already notified at least 60 days in advance.

    Please confirm that the 60-day advance notice was sent to affected customers before the underlying infrastructure switch, or clarify the rollout timeline to ensure continuity for customers relying on the old IPs.

Last reviewed commit: "chore: update static..."

Copy link
Copy Markdown
Contributor

@scott-ray-wilson scott-ray-wilson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@PrestigePvP PrestigePvP merged commit e98296d into main Mar 18, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants