> ## Documentation Index > Fetch the complete documentation index at: https://gcore.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # List cloud egress public IPs > Returns the complete list of IPv4 and IPv6 address ranges that Cloud uses for outbound (egress) traffic. Typical reasons to call this endpoint: - Host-file delivery workflows – You upload images or other assets to the Cloud and share a download link that points to your own infrastructure. Add these egress prefixes to your firewall or object-storage allow-list so our clients can fetch the files without being blocked. - Push integrations / webhooks – You subscribe to the user-actions event log and Cloud pushes events to your listener endpoint. Whitelisting the egress IP ranges lets you accept only traffic that originates from us. - General security controls, audit tooling, or SIEM rules that need to verify that traffic truly comes from the Cloud. The list is global (covers all regions) and refreshed automatically whenever the provider allocates new egress IP space. The response is an array of CIDR blocks; duplicate prefixes are not returned. ## OpenAPI ````yaml /api-reference/services_documented/cloud_api.yaml get /cloud/public/v1/ipranges/egress openapi: 3.1.0 info: title: Gcore OpenAPI – Cloud API description: >- This OpenAPI is an aggregated OpenAPI specification that unifies all Gcore products into a single file. It covers Cloud, CDN, DNS, WAAP, DDoS Protection, Object Storage, Streaming, and FastEdge services. version: '2026-05-11T15:10:30.328297+00:00' servers: - url: https://api.gcore.com security: - APIKey: [] tags: - name: Bare Metal x-displayName: Bare Metal - name: Container as a Service x-displayName: Container as a Service - name: Cost Reports x-displayName: Cost Reports - name: DDoS Protection x-displayName: DDoS Protection - name: Everywhere Inference x-displayName: Everywhere Inference - name: Everywhere Inference Apps x-displayName: Everywhere Inference Apps - name: File Shares x-displayName: File Shares - name: Floating IPs x-displayName: Floating IPs - name: Function as a Service x-displayName: Function as a Service - name: GPU Bare Metal x-displayName: GPU Bare Metal - name: GPU Virtual x-displayName: GPU Virtual - name: IP Ranges x-displayName: IP Ranges - name: Images x-displayName: Images - name: Instances x-displayName: Instances - name: Load Balancers x-displayName: Load Balancers - name: Logging x-displayName: Logging - name: Managed Kubernetes x-displayName: Managed Kubernetes - name: Managed PostgreSQL x-displayName: Managed PostgreSQL - name: Networks x-displayName: Networks - name: Placement Groups x-displayName: Placement Groups - name: Projects x-displayName: Projects - name: Quotas x-displayName: Quotas - name: Regions x-displayName: Regions - name: Registry x-displayName: Registry - name: Reservations x-displayName: Reservations - name: Reserved IPs x-displayName: Reserved IPs - name: Routers x-displayName: Routers - name: SSH Keys x-displayName: SSH Keys - name: Secrets x-displayName: Secrets - name: Security Groups x-displayName: Security Groups - name: Snapshot Schedules x-displayName: Snapshot Schedules - name: Snapshots x-displayName: Snapshots - name: Tasks x-displayName: Tasks - name: User Actions x-displayName: User Actions - name: User Role Assignments x-displayName: User Role Assignments - name: Volumes x-displayName: Volumes paths: /cloud/public/v1/ipranges/egress: get: tags: - IP Ranges summary: List cloud egress public IPs description: >- Returns the complete list of IPv4 and IPv6 address ranges that Cloud uses for outbound (egress) traffic. Typical reasons to call this endpoint: - Host-file delivery workflows – You upload images or other assets to the Cloud and share a download link that points to your own infrastructure. Add these egress prefixes to your firewall or object-storage allow-list so our clients can fetch the files without being blocked. - Push integrations / webhooks – You subscribe to the user-actions event log and Cloud pushes events to your listener endpoint. Whitelisting the egress IP ranges lets you accept only traffic that originates from us. - General security controls, audit tooling, or SIEM rules that need to verify that traffic truly comes from the Cloud. The list is global (covers all regions) and refreshed automatically whenever the provider allocates new egress IP space. The response is an array of CIDR blocks; duplicate prefixes are not returned. operationId: EgressIPRangesViewSet.get parameters: [] responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/IPRangesSerializer' security: [] x-codeSamples: - lang: Python source: |- from gcore import Gcore client = Gcore() ip_ranges = client.cloud.ip_ranges.list() print(ip_ranges.ranges) - lang: Go source: "package main\n\nimport (\n\t\"context\"\n\t\"fmt\"\n\n\t\"github.com/G-Core/gcore-go\"\n\t\"github.com/G-Core/gcore-go/option\"\n)\n\nfunc main() {\n\tclient := gcore.NewClient(\n\t\toption.WithAPIKey(\"My API Key\"),\n\t)\n\tipRanges, err := client.Cloud.IPRanges.List(context.TODO())\n\tif err != nil {\n\t\tpanic(err.Error())\n\t}\n\tfmt.Printf(\"%+v\\n\", ipRanges.Ranges)\n}\n" components: schemas: IPRangesSerializer: properties: ranges: description: IP ranges list example: - 203.0.113.0/24 examples: - - 203.0.113.0/24 items: anyOf: - format: ipv4interface type: string - format: ipv6interface type: string title: Ranges type: array required: - ranges title: IPRangesSerializer type: object securitySchemes: APIKey: description: >- API key for authentication. Make sure to include the word `apikey`, followed by a single space and then your token. Example: `apikey 1234$abcdef` type: apiKey in: header name: Authorization ````