{"slug":"serverless-egress-ips","title":"Rapids Egress IP Addresses","description":"When a Rapids container makes an outbound request, that request leaves our platform from one of a small set of public IPv4 addresses. If you need to allowlist Rapids traffic at a firewall, CDN or WAF,...","section":"Features","url":"https://docs.danubedata.ro/serverless-egress-ips","markdown_url":"https://docs.danubedata.ro/serverless-egress-ips.md","breadcrumbs":[{"title":"Features","slug":null},{"title":"Rapids","slug":"serverless-overview"},{"title":"Egress IP Addresses","slug":"serverless-egress-ips"}],"headings":[{"level":1,"title":"Rapids Egress IP Addresses","id":"rapids-egress-ip-addresses"},{"level":2,"title":"Current addresses","id":"current-addresses"},{"level":2,"title":"How we announce changes","id":"how-we-announce-changes"},{"level":2,"title":"Two things to know before you rely on this","id":"two-things-to-know-before-you-rely-on-this"},{"level":2,"title":"IPv6","id":"ipv6"}],"format":"markdown","word_count":309,"content":"# Rapids Egress IP Addresses\n\nWhen a Rapids container makes an outbound request, that request leaves our platform from one of a small set of public IPv4 addresses. If you need to allowlist Rapids traffic at a firewall, CDN or WAF, these are the addresses to use.\n\n## Current addresses\n\nThe authoritative, machine-readable list lives at:\n\n```\nhttps://docs.danubedata.ro/rapids-egress-ips-v4.txt\n```\n\nOne address per line, plain text, nothing else — so you can poll and diff it from a script:\n\n```bash\ncurl -s https://docs.danubedata.ro/rapids-egress-ips-v4.txt\n```\n\nAlways read the file rather than hard-coding a copy of it.\n\n## How we announce changes\n\n- **New addresses are published at least 14 days before they carry customer traffic.** Poll it more often than that and you'll see planned additions before they carry traffic.\n- **Removed addresses get no advance notice.** A stale allow-rule for a retired address cannot break you, so removals are safe to pick up whenever you next poll.\n- **Emergency capacity may go live sooner than 14 days.** This is rare. The file is updated immediately when it happens.\n\nIn short: additions are the only change you need to react to, and you get 14 days.\n\n## Two things to know before you rely on this\n\n**These addresses are shared.** Every Rapids container on the platform egresses through the same set, not just yours. An IP allow-rule therefore admits other customers' containers too. That is fine for cutting down noise and drive-by scanning, but it is not an authorization control.\n\n**If you need \"only my containers can reach this endpoint,\"** use a secret your container holds and your origin verifies — an injected environment variable checked as a custom header, a Cloudflare service token, or mTLS. You can keep the IP rule on top for defense in depth.\n\n## IPv6\n\nRapids containers egress over IPv4 only, so there is no IPv6 list to allowlist.\n","prev":{"title":"Private Container Registry","slug":"serverless-private-registry","url":"https://docs.danubedata.ro/serverless-private-registry","markdown_url":"https://docs.danubedata.ro/serverless-private-registry.md","json_url":"https://docs.danubedata.ro/serverless-private-registry.json"},"next":{"title":"Automation & Diagnostics","slug":"rapids-automation","url":"https://docs.danubedata.ro/rapids-automation","markdown_url":"https://docs.danubedata.ro/rapids-automation.md","json_url":"https://docs.danubedata.ro/rapids-automation.json"},"index_url":"https://docs.danubedata.ro/index.json"}