Theres a few reports of this floating around.
Theres a number of things it could be
- bad route from you to fast.ly
- bad routes on fast.ly internally
- fast.ly’s load balancer doing schnanigans
- misc other issues
- bad luck when hitting the API and a server in the backend is restarting in the pool (or late removed from the pool)
Basically retry the request. The second attempt should clear. Since it’s not constant as you have noticed, so even an instant retry should get the required data.
(Fast.ly sits in front of the Twitch API)