The egress IP is necessary because I do have rate limiting based on IP so I needed static ips
When I assign an egress ip to my machine it says it is ‘fra’ but actually when I do ip lookup it is in USA
This is very problematic since the API requests I do need to be from EU and not USA.
Anyone had issues like this before?
Hi 
All egress IPs are assigned in the same region as the machine because that’s the only way they would work. If you are referring to the location of the IP as it appears in some GeoIP database – those are human-maintained entries and are often out-of-date and do not match where IPs are actually used. Do you happen to know which GeoIP database we’re talking about here? We could look into asking them to update this information, though we cannot guarantee when this will be updated and when it will be pulled by all the subscribers to these databases.
Hi @PeterCxy , below are the full ips with the ipv6 too
The ipv6 shows that it is in Netherlands, the ipv4 in USA , while the region I chose for machines is Frankfurt
My app relies on static ips because of the rate limiting of exchanges and also on the location
Before allocating Egress IPs the API calls I was making were working, now after assigning egress ips it clearly suggests in the response that the location is blocked
I will be needing at least 20 ips more across my apps
MACHINE ID REGION TYPE EGRESS IP
6e8296ddf54218 fra v6 2a09:8280:e612::7d:d940:7
6e8296ddf54218 fra v4 209.71.75.133
48e3376fe31d78 fra v6 2a09:8280:e612::7d:d940:1
48e3376fe31d78 fra v4 209.71.75.63
4d896e27f72678 fra v6 2a09:8280:e612::7d:d940:9
4d896e27f72678 fra v4 209.71.75.69
d8dd60ea276498 fra v6 2a09:8280:e612::7d:d940:5
d8dd60ea276498 fra v4 209.71.75.249
287624dc0599d8 fra v6 2a09:8280:e612::7d:d940:6
287624dc0599d8 fra v4 209.71.75.169
7843d55ce49218 fra v6 2a09:8280:e612::7d:d940:2
7843d55ce49218 fra v4 209.71.75.114
7814473a447d28 fra v6 2a09:8280:e612::7d:d940:8
7814473a447d28 fra v4 209.71.75.130
3d8d3620f4d058 fra v6 2a09:8280:e612::7d:d940:3
3d8d3620f4d058 fra v4 209.71.75.58
148e415eb51458 fra v6 2a09:8280:e612::7d:d940:4
148e415eb51458 fra v4 209.71.75.204
2873270a025358 fra v6 2a09:8280:e612::7d:d940:0
2873270a025358 fra v4 209.71.75.127
@PeterCxy any idea?
We are working on publishing a geofeed to Maxmind’s GeoIP database to automatically correct the location of regional IPs recorded by them. If what you are looking at is Maxmind’s GeoIP database, then once we start publishing that you should eventually see the location corrected. However, keep in mind that this all depends on whether and how often the API you’re requesting updates their Maxmind GeoIP database copy – and you might have to request them to manually update the GeoIP database in some cases.
When I switched back to same region but without the egress dedicated IP the APIs got back to working and were not blocked..
@PeterCxy update? I’m certain there is a problem because switching back to non-dedicated egress IPs for same region fixed the requests getting blocked problem .. now I’m just risking having an IP who is banned
Yes, but the problem here is that the GeoIP database needs to be updated, not that these IPs themselves are problematic (i.e. your traffic is NOT actually being routed to another country). GeoIP databases are never guaranteed to be fully accurate – we’re making an attempt to update them but we cannot provide guarantees either since it also depends on them (in this case, Maxmind) to approve of the correction requests.
What I can provide as an update right now is that we do have a geofeed server running, and we’ll be exposing this to GeoIP databases so that GeoIP information can hopefully be kept more up-to-date in the future.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.