Hello everyone,
I`ve made a simple discord bot that uses twitch api to check when the stream is live and then posts a link on discord. Everything was working smooth and fine for 2 months until yesterday.
The bot is still working but now in my logs i get loads of these : Error: connect ETIMEDOUT 23.10.139.185:443
This error occurs once every 2-15 mins.
When i ping api.twitch.tv from my home pc i get 100% packets and the ip is 23.78.59.245. But when i ping the same url from my server (located in NY) i get 50% packets loss and ip is 23.10.139.185. I tried pinging google, twitch.tv, youtube.com and everything is fine no packets loss. Yet api.twitch.tv is lagging. Anyone else experiencing this ?
Generally looks ok here.
Their could just be a bad API server in the pool that you are RNG’ing against. Or theres something awry with outbound connections for you on your host
This is really weird and i dont get it what is going on. Now when i ping api.twitch.tv from home pc, i get this:
Pinging e9221.e2.akamaiedge.net [104.66.123.117] with 32 bytes of data:
Reply from 104.66.123.117: bytes=32 time=56ms TTL=54
Reply from 104.66.123.117: bytes=32 time=56ms TTL=54
Reply from 104.66.123.117: bytes=32 time=56ms TTL=54
Reply from 104.66.123.117: bytes=32 time=56ms TTL=54
Reply from 104.66.123.117: bytes=32 time=56ms TTL=54
Reply from 104.66.123.117: bytes=32 time=57ms TTL=54
Reply from 104.66.123.117: bytes=32 time=56ms TTL=54
Reply from 104.66.123.117: bytes=32 time=56ms TTL=54
Ping statistics for 104.66.123.117:
Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 57ms, Average = 56ms
If i ping the same ip from my server:
PING 104.66.123.117 (104.66.123.117) 56(84) bytes of data.
64 bytes from 104.66.123.117: icmp_seq=1 ttl=58 time=102 ms
64 bytes from 104.66.123.117: icmp_seq=2 ttl=58 time=102 ms
64 bytes from 104.66.123.117: icmp_seq=3 ttl=58 time=102 ms
64 bytes from 104.66.123.117: icmp_seq=4 ttl=58 time=102 ms
64 bytes from 104.66.123.117: icmp_seq=5 ttl=58 time=102 ms
64 bytes from 104.66.123.117: icmp_seq=6 ttl=58 time=102 ms
64 bytes from 104.66.123.117: icmp_seq=7 ttl=58 time=102 ms
^C
— 104.66.123.117 ping statistics —
7 packets transmitted, 7 received, 0% packet loss, time 6005ms
rtt min/avg/max/mdev = 102.220/102.259/102.352/0.298 ms
But if i ping api.twitch.tv from the server i get:
PING e9221.e2.akamaiedge.net (23.10.139.185) 56(84) bytes of data.
64 bytes from a23-10-139-185.deploy.static.akamaitechnologies.com (23.10.139.185): icmp_seq=1 ttl=58 time=0.577 ms
64 bytes from a23-10-139-185.deploy.static.akamaitechnologies.com (23.10.139.185): icmp_seq=3 ttl=58 time=0.570 ms
64 bytes from a23-10-139-185.deploy.static.akamaitechnologies.com (23.10.139.185): icmp_seq=4 ttl=58 time=0.566 ms
64 bytes from a23-10-139-185.deploy.static.akamaitechnologies.com (23.10.139.185): icmp_seq=5 ttl=58 time=0.578 ms
64 bytes from a23-10-139-185.deploy.static.akamaitechnologies.com (23.10.139.185): icmp_seq=7 ttl=58 time=0.578 ms
64 bytes from a23-10-139-185.deploy.static.akamaitechnologies.com (23.10.139.185): icmp_seq=8 ttl=58 time=0.575 ms
64 bytes from a23-10-139-185.deploy.static.akamaitechnologies.com (23.10.139.185): icmp_seq=13 ttl=58 time=0.600 ms
64 bytes from a23-10-139-185.deploy.static.akamaitechnologies.com (23.10.139.185): icmp_seq=14 ttl=58 time=0.564 ms
64 bytes from a23-10-139-185.deploy.static.akamaitechnologies.com (23.10.139.185): icmp_seq=15 ttl=58 time=0.586 ms
64 bytes from a23-10-139-185.deploy.static.akamaitechnologies.com (23.10.139.185): icmp_seq=18 ttl=58 time=0.568 ms
^C
— e9221.e2.akamaiedge.net ping statistics —
18 packets transmitted, 10 received, 44% packet loss, time 17002ms
rtt min/avg/max/mdev = 0.564/0.576/0.600/0.018 ms
And if i ping 23.10.139.185 from my home pc:
Pinging 23.10.139.185 with 32 bytes of data:
Reply from 23.10.139.185: bytes=32 time=116ms TTL=54
Reply from 23.10.139.185: bytes=32 time=116ms TTL=54
Reply from 23.10.139.185: bytes=32 time=116ms TTL=54
Reply from 23.10.139.185: bytes=32 time=116ms TTL=54
Reply from 23.10.139.185: bytes=32 time=116ms TTL=54
Reply from 23.10.139.185: bytes=32 time=116ms TTL=54
Reply from 23.10.139.185: bytes=32 time=117ms TTL=54
Reply from 23.10.139.185: bytes=32 time=116ms TTL=54
Reply from 23.10.139.185: bytes=32 time=116ms TTL=54
Reply from 23.10.139.185: bytes=32 time=117ms TTL=54
Reply from 23.10.139.185: bytes=32 time=116ms TTL=54
Reply from 23.10.139.185: bytes=32 time=116ms TTL=54
Ping statistics for 23.10.139.185:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 116ms, Maximum = 117ms, Average = 116ms
Did twitch suddenly decided to rate limit my server ip or something ?
If it was rate limiting your IP.
You would of got an email to the email associated with the ClientID making the requests.
Maybe akamai is having a bad day, or the datacenter your server is physically located in is having a bad day. It’s more likely to be something in the chain between you and twitch rather than twitch itself
1 Like
Well i guess there is not much i can do apart from waiting, if it persists i might have to contact my vps provider. Thanks
So it seems that the problem persists. I contacted my vps provider and they said there were no problems on their end. The DNS that i used on my vps were googles 8.8.8.8 so i changed it to 1.1.1.1 cloudflare and twitch api resolved to a different ip (ip`s end was different) and i imitiately noticed a difference NO MORE PACKET LOSS. However it only took half an hour and the same thing started happening again… I tried swapping my DNS servers but the problem still persisted until i decided to use the SAME bot with the SAME libraries, EVERYTHING was the same a part from the fact that i now used NY proxy. And the problems stopped. So now i am convinced that twitch is throttling my ip. I have not received any emails from them. Who do i contact on twitch and ask them what is going on ?
It’s not Twitch. Twitch doesn’t thottle IP’s they’ll flat block you and email you.
8.8.8.8 has had some issues this week. Completely went down.
In your example you have changed your routing.
This likely means you are bypassing a faulty node in the route between you and twitch.
But if you really think it’s Twitch, which it isn’t because they don’t IP throttle.
https://twitchdev.zendesk.com/hc/en-us is the direct line to Dev Support. And they;ll tell you the same thing.
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.