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 ?