# Static IP Addresses

Synqly provides static egress IP addresses for end users who need to allowlist our services in their
firewall rules.

## How it works

To use static IPs, route your API traffic through these endpoints:

- **North America**: `api-static.synqly.com`
- **Europe**: `api-eu-static.synqly.com`


All traffic sent through these endpoints will originate from the static IP addresses listed below.

## Static IP addresses

### North America (NA)

- `104.43.240.68`
- `104.43.240.69`
- `104.43.247.222`
- `104.43.247.223`


Location: US Central region

### Europe (EU)

- `20.218.112.228`
- `20.218.112.229`
- `20.218.112.208`
- `20.218.112.209`


## Limitations

- **No geo-routing**: Traffic is not routed based on location, which may result in higher latency
- **North America limitations**: Static IPs are hosted in a single US Central region without
multi-region failover
- **No rate limit differences**: Same rate limits and throughput as standard endpoints


## Implementation

Integrators need to:

1. Configure integrations to use the static endpoint (`api-static.synqly.com`)
2. Provide the IP addresses to end users for firewall allowlisting
3. All API traffic through the static endpoint will originate from these IPs


## Alternative: Bridge

[Bridge](https://docs.synqly.com/bridge/agent-setup) is an agent that runs within your network and
initiates connections to Synqly. Consider Bridge if you:

- Can run an agent in your environment
- Need lower latency


Static IPs are simpler when you cannot install additional software or your policies only permit
specific IP allowlisting.