PING burningware.in (172.67.155.203) 56(84) bytes of data.
64 bytes from 172.67.155.203 (172.67.155.203): icmp_seq=1 ttl=56 time=2.90 ms
64 bytes from 172.67.155.203 (172.67.155.203): icmp_seq=2 ttl=56 time=1.75 ms
64 bytes from 172.67.155.203 (172.67.155.203): icmp_seq=3 ttl=56 time=1.56 ms
64 bytes from 172.67.155.203 (172.67.155.203): icmp_seq=4 ttl=56 time=1.74 ms
64 bytes from 172.67.155.203 (172.67.155.203): icmp_seq=5 ttl=56 time=1.70 ms
--- burningware.in ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 1.564/1.932/2.902/0.489 ms
traceroute to burningware.in (104.21.80.247), 30 hops max, 60 byte packets
1 ip-10-0-0-119.ec2.internal (10.0.0.119) 0.903 ms 0.194 ms 0.866 ms
2 ec2-3-236-63-87.compute-1.amazonaws.com (3.236.63.87) 11.788 ms ec2-3-236-62-29.compute-1.amazonaws.com (3.236.62.29) 4.703 ms ec2-3-236-60-41.compute-1.amazonaws.com (3.236.60.41) 4.165 ms
3 240.3.12.98 (240.3.12.98) 1.654 ms 240.4.112.67 (240.4.112.67) 1.638 ms 240.0.56.96 (240.0.56.96) 1.622 ms
4 100.66.11.214 (100.66.11.214) 10.518 ms * 240.3.184.36 (240.3.184.36) 2.611 ms
5 242.10.91.49 (242.10.91.49) 2.553 ms 240.3.184.38 (240.3.184.38) 2.535 ms 242.10.91.53 (242.10.91.53) 3.238 ms
6 100.66.3.141 (100.66.3.141) 99.971 ms 99.83.93.218 (99.83.93.218) 3.198 ms 2.095 ms
7 242.10.90.177 (242.10.90.177) 3.149 ms 100.66.0.121 (100.66.0.121) 4.131 ms 99.83.93.218 (99.83.93.218) 2.548 ms
8 173.245.63.121 (173.245.63.121) 2.533 ms 99.83.93.219 (99.83.93.219) 2.979 ms 173.245.63.113 (173.245.63.113) 3.745 ms
9 104.21.80.247 (104.21.80.247) 2.420 ms 2.292 ms 2.267 ms
Warum „BurningWare“ offline ging, bleibt wohl reine Spekulation? Aber komplett abgeschaltet hat man dort ja nicht, da es ja ansonsten von Cloudflare einen 522-Fehler geben würde. CF antwortet aber korrekt für den eigentlichen Server.