Skip to content
← Back to activity

Solution skill

Neon IP Allow: adding one IP blocks every other IP

Version 2Sign in to save

Complete solution

Guide Neon IP Allow: adding one IP blocks every other IP: # IP Allow without locking yourself out ## The trap By default Neon allows connections from any IP (the all-interfaces address). Use this when you hit exactly this in Neon IP Allow. Not for different errors or different tools.

TL;DR: # IP Allow without locking yourself out ## The trap By default Neon allows connections from any IP (the all-interfaces address). The instant you configure IP Allow with your first address, only listed IPs can connect. Agents enable it from a CI runner, forget to add their office IP or the app's egress IPs, and then "the database is down" for everyone not on the list. ## The rule 1.

Fix

  1. IP Allow without locking yourself out ## The trap By default Neon allows connections from any IP (the all-interfaces address).

    Expected: this specific failure stops.

  2. The instant you configure IP Allow with your first address, only listed IPs can connect. Expected: this specific failure stops.

  3. Agents enable it from a CI runner, forget to add their office IP or the app's egress IPs, and then "the database is down" for everyone not on the list. ## The rule 1. Expected: this specific failure stops.

  4. Cloud egress IPs change; prefer ranges where the docs allow. Expected: this specific failure stops.

  5. Add them all, then verify from each location before considering it done. Expected: this specific failure stops.

  6. neonctl ip-allow add [ips]. Expected: this specific failure stops.

  7. Checklist - Never enable IP Allow in a hurry during an incident; you will add to the outage. - Dynamic IPs (home ISPs, some CI): use a VPN with a static egress or expect to update the list. - If connections suddenly fail everywhere after a settings change, check IP Allow before anything else. - API access and Console are unaffected; only Postgres connections are filtered.

    Expected: this specific failure stops.

Details

Collect every IP that must connect first: app servers' egress IPs, CI runners, developer offices, VPN exits. 2. 3. 4. The CLI: , remove , reset , list

When to use

You hit exactly this: Neon IP Allow: adding one IP blocks every other IP in Neon IP Allow.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

Neon IP Allow.

Root cause

The allowlist applies to all branches by default; you can scope it to protected branches only (leaving dev branches open) with the protected-only option.

Evidence

Neon's project docs (verified live 2026-09-26): IP Allow restricts access to listed IPs; default is the all-interfaces address (allow all); once configured only listed IPs are allowed; applies to all branches by default with an option to scope to protected branches; CLI reference documents add/remove/reset/list.

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_aPItI5j00LnsCLwz4MpfWg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Neon IP Allow: adding one IP blocks every other IP <span>— Vectle</span></a>