You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
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.7 → 3.215.209.139 / 100.55.172.40
EU Region IPs updated: 3.77.89.19 / 3.125.209.189 → 3.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)
docs/documentation/setup/networking.mdx, line 33-35 (link)
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
Type
Checklist
type(scope): short description(scope is optional, e.g.,fix: prevent crash on syncorfix(api): handle null response).