API network connectivity issues
This reference article touches on API connectivity issues and how to troubleshoot them.
Braze’s API endpoints use a CDN that routes traffic to the closest POP based on DNS information. If you are having issues connecting or notice that you are connecting to a POP that is not efficient, make sure to use your provider’s DNS servers or DNS servers that are set up in the same data center as your server and have proper IP location meta-information associated with them.
We have noticed that a handful of firewalls attempt to modify or secure HTTPS/TLS traffic which interferes with connections to Braze’s API endpoints. If your servers are behind any sort of physical firewall, disable any HTTPS/TLS acceleration or modifications that the firewall(s) and/or router(s) are performing. Additionally, you can allowlist outbound traffic to our CDN providers (Fastly.com) to see if that resolves the issue.
Occasionally, iptables setups that filter on SYN/ACK/RST packets can also cause issues, so if you are using iptables on your host you could also allowlist outbound traffic to our CDN providers (Fastly.com) to see if that resolves the issue.
If you are still having network issues with connecting to Braze’s API endpoint, provide an MTR Test and the results from Fastly Debug while experiencing an issue and submit that with your support request. Note that the test results must be obtained from a server that is having issues connecting to Braze’s API endpoint, not from a development machine. A network capture (tcpdump or .pcap file) will also be helpful if it can be obtained.
For more information about MTR, check out these resources based on your operating system:
Allowlisting Braze’s API endpoint IP ranges
To allowlist Braze’s API endpoint through your firewall, our CDN provides access to the list of assigned IP ranges via a JSON dump. For a list of Fastly IP ranges, refer to their public IP list.