Skip to content

Documenting Egress After ISP Modem Swaps

Home Wi-Fi router with glowing status lights

TL;DR: Technician modem replacements and gateway refreshes often change your public IP without changing Wi-Fi names. Capture the new egress immediately, update allowlists and dynamic DNS, and keep a short change log. Confirm with an IP lookup before you blame the remote SaaS.

What usually changes when the ISP touches the CPE

Swapping a modem or combo gateway can issue a new DHCP lease on the WAN, reset PPPoE credentials handling, enable IPv6 where none existed, or move you behind a CGNAT pool. Your SSID might look identical; outbound identity does not.

Small businesses that allowlist office IPs on cloud firewalls feel this first: vendors suddenly reject API calls the morning after an “equipment upgrade” visit.

A five-minute capture ritual

Before the tech leaves—or as soon as service restores:

  • From a machine on the LAN, open an IP inquiry page; save address, ASN, and local time.
  • Check whether IPv6 global addresses appeared on the workstation.
  • Compare the gateway’s WAN status page to the inquiry result (mismatch can hint CGNAT).
  • Note the ticket or work-order number from the ISP.

Store that bundle in the same place you keep DNS records. Future-you will not remember the visit date.

Dynamic DNS and VPN concentrators

If a hostname tracks your office IP, force an update after the swap. Site-to-site VPNs with peer IPs burned into configs need edits, not reboots. Split the work: network owner updates tunnels; app owners update SaaS allowlists.

Symptoms that look like application outages

OAuth callbacks fail, webhook deliveries time out, SFTP vendor lockouts, and “invalid source” errors on payment gateways often share one cause: stale allowlists. Check egress before redeploying microservices. Also retest from cellular hotspot; if hotspot works and office fails, DNS is probably fine and IP policy is not.

Communicating to vendors without noise

Send a short message: old IP (if known), new IP, ASN, effective timestamp, and whether both IPv4 and IPv6 must be permitted. Avoid pasting entire traceroute novels unless asked. Ask them to confirm which header or socket field they filter on—especially if you also use a reverse proxy.

Preventing the next surprise

Prefer provider features that reserve a stable IP when the business depends on allowlists. Where budgets forbid it, schedule a quarterly egress audit: compare today’s lookup to the documented value. Home-lab enthusiasts can automate checks; offices can assign the task to whoever owns the firewall.

After every ISP truck roll, make the inquiry step muscle memory via www.whatismyipaddressinquire.com. Ten seconds of documentation beats two hours of cross-team debugging.

Modems change. Identities change with them. Write the new egress down while the technician’s van is still outside.