Is GeoDNS still an issue?

[PeteKnight]

Read his thread:

Load balancing deployment for local blynk server

Right now we use Geo DNS as load balancer. So when app/hardware connects to the closest server it checks if this is correct server. In most cases it is. Otherwise server returns redirect response with correct server address. Every server holds it’s own userbase, so this is more like sharding scheme that is based on location.

It explains why the app and your hardware code that uses Blynk.begin works correctly. You’re seeing the re-direction to the original server where your project lives.

It’s a bit ambiguous as to whether this same redirection occurs when calling the API, but issues with IFTTT and your own experience says that the issue still exists.

Fortunately for you, the solution is simple - update the API calls to 45.55.96.146 instead of blynk-cloud.com
You may get faster re-connections if you also specify 45.55.96.146 and port 80 in your Blynk connection code, rather than relying on the DNS redirection process.

Pete.