Failed to connect to

  • 21 October 2023
  • 2 replies

Badge +3

One of my customers is getting this error: “Failed to connect to”


When I try to ping the IP address from my local machine, the request times out. Any ideas what might be causing this issue? Is the revenuecat API down? Or perhaps API IP changed but DNS issue?

2 replies

Badge +3

It seems to resolve to an AWS IP, which hosts revenuecat servers. Is RevenueCat using dynamic IP for API servers? Can static IP be used? Using dynamic IP can cause problems if there are intermittent DNS issues anywhere between the user and the server (such as wifi, data provider, country DNS, etc). Or perhaps Revenuecat API can provide us a way to override DNS server to something like Cloudflare or Google’s?

Badge +3

I created an issue on github: