API calls taking forever from Chile and Brazil

The Movie Database-ondersteuning

Ondersteuning → API-ondersteuning

geplaatst door peagravel
STAFFMOD
op 18 december 2024 om 11:15 AM

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

6 antwoorden (op pagina 1 van 1)

• Jump to last post

Reactie van Travis Bell

STAFFMOD

op 18 december 2024 om 12:39 PM

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

curl -I -L "https://api.themoviedb.org/3/authentication?api_key=###"

Response

HTTP/2 200
content-type: application/json;charset=utf-8
content-length: 16
date: Wed, 18 Dec 2024 17:38:04 GMT
server: openresty
cache-control: public, max-age=0
vary: accept-encoding
x-cache: Miss from cloudfront
via: 1.1 e76eba87ee47517dc7f2053edfb921bc.cloudfront.net (CloudFront)
x-amz-cf-pop: SEA900-P5
alt-svc: h3=":443"; ma=86400
x-amz-cf-id: pYxlw3M5m1-iNtXmD_l0V7V9rPeUujLMxRrns7PtnlpgMCrcIUNUDQ==
vary: Origin

Reactie van peagravel

STAFFMOD

op 18 december 2024 om 1:02 PM

Thanks for responding, Travis.

Chile:

HTTP/2 200 
content-type: application/json;charset=utf-8
content-length: 16
date: Wed, 18 Dec 2024 17:59:14 GMT
server: openresty
cache-control: public, max-age=0
vary: accept-encoding
x-cache: Miss from cloudfront
via: 1.1 ac14fcc863a89fac74e34ba2c00bfef4.cloudfront.net (CloudFront)
x-amz-cf-pop: MIA3-P6
alt-svc: h3=":443"; ma=86400
x-amz-cf-id: oFDI3mGDhvlLVNwzeUXYQRf4k8IMO2HR4Tc2nfxankoZn6H-WVhoSg==
vary: Origin

Brazil:

HTTP/2 200 
content-type: application/json;charset=utf-8
content-length: 16
date: Wed, 18 Dec 2024 17:59:08 GMT
server: openresty
cache-control: public, max-age=0
vary: accept-encoding
x-cache: Miss from cloudfront
via: 1.1 72effd5076df8f62aaf006d6a0074238.cloudfront.net (CloudFront)
x-amz-cf-pop: MIA50-P4
alt-svc: h3=":443"; ma=86400
x-amz-cf-id: Z19IKAo-nqMtUZpt7AxIMHWaeGN_SLNenwnClL3Po7zvWXX7ykcB1A==
vary: Origin

Germany:

HTTP/2 200 
content-type: application/json;charset=utf-8
content-length: 16
date: Wed, 18 Dec 2024 18:00:17 GMT
server: openresty
cache-control: public, max-age=0
vary: accept-encoding
x-cache: Miss from cloudfront
via: 1.1 b4904c5988fd0eaae341a12cc47f3766.cloudfront.net (CloudFront)
x-amz-cf-pop: FRA60-P3
alt-svc: h3=":443"; ma=86400
x-amz-cf-id: joOPHdEMYJq9lZ5kXRDgqzI4hT2RySURhupbUwqtWEzhHeWg3O692g==
vary: Origin

Reactie van Travis Bell

STAFFMOD

op 18 december 2024 om 1:24 PM

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?

Reactie van peagravel

STAFFMOD

op 19 december 2024 om 7:49 AM

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.

Reactie van peagravel

STAFFMOD

op 19 december 2024 om 11:42 AM

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!

Reactie van Travis Bell

STAFFMOD

op 19 december 2024 om 11:53 AM

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.

Gebruikers in deze discussie

Categorieën

The Movie Database-ondersteuning