I cannot.
And if it’s fast.ly it’s somewhat out of Twitch’s hands anyway and likely fast.ly already looking at it.
The times of my faults don’t line up with your times, and I have way less faults than you (like <10 total distributed across 2 servers in 2 different geographicals (which also spread the faults into different time blocks)) and I hit the API a similar amnount of time as you I imagine)
So it’s just fast.ly things I guess.
And since it’s not a constant issue. I imagine it’s a Twitch Can’t fix and a fast.ly being weird (course that doesn’t account for any BGP schnanigans or other things that could screw with routes or server load balancers load balancing etc)
Sods law it was Paris Data Center maintaince that was screwing up… or follow up rebalancing on fastly’s network