Hi,
I would like to ask about IP range of {clusterID}.bru-2.zeebe.camunda.io. As my backend application sits within a private subnet, egress rule is required to set to allow its interactions to my Camunda SaaS cluster, i.e. polling. I tried with endpoint /meta/ip-ranges mentioned Hostnames and IP addresses for Camunda connections | Camunda 8 Docs but the result is different from what I’ve got with ping. So may I know what ip ranges are recommended for my egress rule setting? Thanks.
The /meta/ip-ranges endpoint only provides Web Modeler egress IPs, not the complete set of IPs for Zeebe client connections, which explains the discrepancy with your ping results. I found the following relevant resources:
Does this help? If not, can anyone from the community jump in? 
Hints: Use the Ask AI feature in Camunda’s documentation to chat with AI and get fast help. Report bugs and features in Camuda’s GitHub issue tracker. Trust the process. 
I set firewall whitelist with the ip i got from ping; my app can interact with my SaaS cluster, however intermittently receiving grpc exception (believe it’s coming from the polling task), like:
io.grpc.StatusRuntimeException: UNAVAILABLE: io exception
io.grpc.StatusRuntimeException: DEADLINE_EXCEEDED: CallOptions deadline exceeded after 19.999995000s. Name resolution delay 0.000000000 seconds. [closed=[], open=[[buffered_nanos=207133, remote_addr=[clusterid].bru-2.zeebe.camunda.io/[ip from ping]:443]
io.grpc.StatusRuntimeException: UNAVAILABLE: HTTP status code 502
Sometimes the problem persists that will affect the stability of my service, so may I know if there’s anything i can do to resolve this issue? Thanks.
p.s. no proxy is set between my subnet and internet. my app sits in gcp in hk and camunda cluster is in bru; spring-boot-starter-camunda version is 8.3.1 (have to stick with this version with some reason)