# 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. Collect every IP that must connect first: app servers' egress IPs, CI runners, developer offices, VPN exits. Cloud egress IPs change; prefer ranges where the docs allow.
2. Add them all, then verify from each location before considering it done.
3. 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.
4. The CLI: `neonctl ip-allow add [ips]`, `remove`, `reset`, `list`.

## 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.