Very varying degrees of site response

[sundancer 42903xp 0]

Hello who ever reads the tech stuff here:

Almost every time I use OTT/BoW in the evening it’s horribly slow. So I started to dig around a bit. And there are weird things happening:

pinging http://www.beastsofwar.com
Ping wird ausgeführt für www.beastsofwar.com [104.26.15.41] mit 32 Bytes Daten:
Antwort von 104.26.15.41: Bytes=32 Zeit=21ms TTL=55
Antwort von 104.26.15.41: Bytes=32 Zeit=20ms TTL=55
Antwort von 104.26.15.41: Bytes=32 Zeit=20ms TTL=55
Antwort von 104.26.15.41: Bytes=32 Zeit=20ms TTL=55
Antwort von 104.26.15.41: Bytes=32 Zeit=20ms TTL=55
Antwort von 104.26.15.41: Bytes=32 Zeit=20ms TTL=55
Antwort von 104.26.15.41: Bytes=32 Zeit=20ms TTL=55
Antwort von 104.26.15.41: Bytes=32 Zeit=20ms TTL=55
Antwort von 104.26.15.41: Bytes=32 Zeit=21ms TTL=55
Zeitüberschreitung der Anforderung. (timeout)
Antwort von 104.26.15.41: Bytes=32 Zeit=21ms TTL=55
Zeitüberschreitung der Anforderung. (timeout)
Zeitüberschreitung der Anforderung. (timeout)
Antwort von 104.26.15.41: Bytes=32 Zeit=21ms TTL=55
Antwort von 104.26.15.41: Bytes=32 Zeit=20ms TTL=55
Zeitüberschreitung der Anforderung. (timeout)
Antwort von 104.26.15.41: Bytes=32 Zeit=21ms TTL=55
Antwort von 104.26.15.41: Bytes=32 Zeit=20ms TTL=55
Zeitüberschreitung der Anforderung. (timeout)
Antwort von 104.26.15.41: Bytes=32 Zeit=21ms TTL=55

pinging http://www.ontabletop.com

Antwort von 172.67.166.121: Bytes=32 Zeit=19ms TTL=58
Antwort von 172.67.166.121: Bytes=32 Zeit=18ms TTL=58
Antwort von 172.67.166.121: Bytes=32 Zeit=18ms TTL=58
Antwort von 172.67.166.121: Bytes=32 Zeit=18ms TTL=58
Antwort von 172.67.166.121: Bytes=32 Zeit=18ms TTL=58
Antwort von 172.67.166.121: Bytes=32 Zeit=18ms TTL=58
Antwort von 172.67.166.121: Bytes=32 Zeit=18ms TTL=58
Antwort von 172.67.166.121: Bytes=32 Zeit=18ms TTL=58
Antwort von 172.67.166.121: Bytes=32 Zeit=19ms TTL=58
Antwort von 172.67.166.121: Bytes=32 Zeit=18ms TTL=58
Antwort von 172.67.166.121: Bytes=32 Zeit=18ms TTL=58
Antwort von 172.67.166.121: Bytes=32 Zeit=18ms TTL=58
Antwort von 172.67.166.121: Bytes=32 Zeit=18ms TTL=58
Antwort von 172.67.166.121: Bytes=32 Zeit=18ms TTL=58
Antwort von 172.67.166.121: Bytes=32 Zeit=18ms TTL=58
Antwort von 172.67.166.121: Bytes=32 Zeit=19ms TTL=58
Antwort von 172.67.166.121: Bytes=32 Zeit=18ms TTL=58
Antwort von 172.67.166.121: Bytes=32 Zeit=18ms TTL=58
Antwort von 172.67.166.121: Bytes=32 Zeit=19ms TTL=58
Antwort von 172.67.166.121: Bytes=32 Zeit=18ms TTL=58

tracert on BoW

3 5 ms 4 ms 4 ms p3e9bf179.dip0.t-ipconnect.de [62.155.241.121]
4 13 ms 13 ms 13 ms b-eh3-i.B.DE.NET.DTAG.DE [217.5.72.70]
5 13 ms 24 ms 39 ms 4.68.62.205
6 * * * Zeitüberschreitung der Anforderung. (timeout)
7 21 ms 21 ms 40 ms 195.122.183.210
8 * 21 ms * 172.70.240.3
9 * 22 ms * 104.26.15.41
10 * 21 ms 20 ms 104.26.15.41

tracert on OTT

3 5 ms 4 ms 4 ms p3e9bf179.dip0.t-ipconnect.de [62.155.241.121]
4 13 ms 13 ms 14 ms b-eh3-i.B.DE.NET.DTAG.DE [217.5.72.74]
5 13 ms 13 ms 20 ms 4.68.62.205
6 25 ms 24 ms 18 ms ae2.3207.edge6.Dusseldorf1.level3.net [4.69.161.198]
7 19 ms 19 ms 19 ms CLOUDFLARE.edge6.Dusseldorf1.Level3.net [62.67.22.246]
8 19 ms 18 ms 18 ms 172.67.166.121

So since all traffic directed to OTT is flawless but the traffic going to BoW is dropping packets like there is no tomorrow I suspect a bad config at where ever the IP 195.122.183.210 is sitting. Bad Cloudflare config? Rouge load balancer?

Hope this help finding the culprit. If I can do anything more from the diagnostic side please msg me.

[sundancer 42903xp 0]

So it looks like it’s really a problem with some config on the beastofwar.com side of things. BoW URL resolves to three different IPs:

104.26.14.41
104.26.15.41
172.67.72.64

OTT resolves to two IP addresses:

104.27.152.222
104.27.153.222

Tracing and pinging the BoW IPs can result in timeouts while the OTT IPs can’t be traced or pinged. But I’m guessing that is on purpose. (Not being trace- or ping-able is a security feature after all)

[Author]

Posts