I have a script that queries the API using the URL https://api.themoviedb.org/3/movie/539972?api_key=xxx&language=en-US
and up until last night this call would work just fine, but now the calls from Chile and Brazil are taking around 40 seconds, while from Germany everything is working just fine. Using a browser in any of those places also gives me an instantaneous response.
Was there any change to the API that I'll have to update my script? By the way, my script only queries the API 5 times a day, so I don't think is anything related to rate limit.
Chile and Brazil is resolving the domain to the IPs below:
api.themoviedb.org has address 3.166.181.100
api.themoviedb.org has address 3.166.181.57
api.themoviedb.org has address 3.166.181.5
api.themoviedb.org has address 3.166.181.50
api.themoviedb.org has IPv6 address 2600:9000:27a7:3600:c:174a:c400:93a1
api.themoviedb.org has IPv6 address 2600:9000:27a7:fa00:c:174a:c400:93a1
api.themoviedb.org has IPv6 address 2600:9000:27a7:5800:c:174a:c400:93a1
api.themoviedb.org has IPv6 address 2600:9000:27a7:e200:c:174a:c400:93a1
api.themoviedb.org has IPv6 address 2600:9000:27a7:6a00:c:174a:c400:93a1
api.themoviedb.org has IPv6 address 2600:9000:27a7:4800:c:174a:c400:93a1
api.themoviedb.org has IPv6 address 2600:9000:27a7:e400:c:174a:c400:93a1
api.themoviedb.org has IPv6 address 2600:9000:27a7:b400:c:174a:c400:93a1
Germany:
api.themoviedb.org has address 99.86.4.16
api.themoviedb.org has address 99.86.4.8
api.themoviedb.org has address 99.86.4.35
api.themoviedb.org has address 99.86.4.122
api.themoviedb.org has IPv6 address 2600:9000:2057:3400:c:174a:c400:93a1
api.themoviedb.org has IPv6 address 2600:9000:2057:ce00:c:174a:c400:93a1
api.themoviedb.org has IPv6 address 2600:9000:2057:b800:c:174a:c400:93a1
api.themoviedb.org has IPv6 address 2600:9000:2057:6c00:c:174a:c400:93a1
api.themoviedb.org has IPv6 address 2600:9000:2057:2800:c:174a:c400:93a1
api.themoviedb.org has IPv6 address 2600:9000:2057:da00:c:174a:c400:93a1
api.themoviedb.org has IPv6 address 2600:9000:2057:3a00:c:174a:c400:93a1
api.themoviedb.org has IPv6 address 2600:9000:2057:6a00:c:174a:c400:93a1
Any directions will help Thanks
Δεν μπορείτε να βρείτε κάποια ταινία ή σειρά; Συνδεθείτε για να τη δημιουργήσετε.
Θέλετε να αξιολογήσετε ή να προσθέσετε αυτό το στοιχείο σε μια λίστα;
Δεν είσαι μέλος;
Απάντηση από τον/την Travis Bell
στις 18 Δεκέμβριος 2024 στις 12:39 ΜΜ
Sounds like something network related in South America. We don't run the CDN, AWS does, but I'd be curious to know what POP you're hitting in South America. What is the
x-amz-cf-pop
from one of those requests?Request
Response
Απάντηση από τον/την peagravel
στις 18 Δεκέμβριος 2024 στις 01:02 ΜΜ
Thanks for responding, Travis.
Chile:
Brazil:
Germany:
Απάντηση από τον/την Travis Bell
στις 18 Δεκέμβριος 2024 στις 01:24 ΜΜ
Ok, so both of your SA requests are being routed to the same pop in Miami, and your Germany requests are being routed to France.
When you run those cURL commands, are they taking the same ~40 seconds to reply?
Απάντηση από τον/την peagravel
στις 19 Δεκέμβριος 2024 στις 07:49 ΕΊΜΑΙ
It's a hit-and-miss. I'm still investigating but it looks like it's related to IPv6. On my tests, all connections to v4 worked just fine. I'll keep you posted.
Απάντηση από τον/την peagravel
στις 19 Δεκέμβριος 2024 στις 11:42 ΕΊΜΑΙ
Hi Travis, I finally understood what's going on. The DNS is responding with a list of v4 and v6 addresses, and my script was trying to connect using the v6 address instead of v4. However, since my IPv6 wasn't properly set up, the connection started to fail. After fixing my IPv6 configuration, everything went back to normal.
I appreciate your support!
Απάντηση από τον/την Travis Bell
στις 19 Δεκέμβριος 2024 στις 11:53 ΕΊΜΑΙ
Happy to hear you figured it out! I've definitely seen IPv6 cause issues. I actually have it disabled on my own home network because my ISP does some weird things that was causing me some issues on the internet as well.