3 ms·
I'm surprised a flood that regularly takes an AWS load balancer offline isn't showing more link congestion... get /: tsl@crabapple:~> time curl http://wikil
by trotsky 16y ago
I'm surprised a flood that regularly takes an AWS load balancer offline isn't showing more link congestion...
get /:
tsl@crabapple:~> time curl http://wikileaks.org/ > /dev/null
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 5837 100 5837 0 0 20684 0 --:--:-- --:--:-- --:--:-- 30087
real 0m0.298s
user 0m0.003s
sys 0m0.005s
where:
tsl@crabapple:~> dig wikileaks.org A | grep -A 1 "; ANS"
;; ANSWER SECTION:
wikileaks.org. 2517 IN A 184.72.37.90
tsl@crabapple:~> dig -x 184.72.37.90 PTR | grep -A 1 "; ANS"
;; ANSWER SECTION:
90.37.72.184.in-addr.arpa. 300 IN PTR ec2-184-72-37-90.us-west-1.compute.amazonaws.com.
palo alto:
3 rtr-border1-p2p-core1.slac.stanford.edu (134.79.252.133) 0.796 ms 0.433 ms 0.400 ms
4 slac-mr2-p2p-rtr-border1.slac.stanford.edu (192.68.191.245) 0.371 ms 0.415 ms 0.400 ms
5 sunnsdn2-ip-slacmr2.es.net (134.55.217.2) 0.668 ms 0.709 ms 0.676 ms
6 sunncr1-sunnsdn2.es.net (134.55.209.98) 0.808 ms 0.842 ms 0.823 ms
7 eqxsjrt1-te-sunncr1.es.net (134.55.38.146) 1.231 ms 1.268 ms 1.247 ms
8 equinix01-sfo5.amazon.com (206.223.116.177) 1.930 ms 1.780 ms 1.516 ms
9 * * *
nyc:
3 te2-7.ccr01.jfk07.atlas.cogentco.com (154.54.1.134) 0.564 ms 0.575 ms
4 ntt.jfk07.atlas.cogentco.com (154.54.12.66) 0.664 ms 0.659 ms
5 ae-2.r22.nycmny01.us.bb.gin.ntt.net (129.250.4.174) 0.760 ms 0.731 ms
6 ae-1.r20.asbnva02.us.bb.gin.ntt.net (129.250.2.9) 31.672 ms 7.974 ms
7 ae-0.r20.sttlwa01.us.bb.gin.ntt.net (129.250.2.53) 90.576 ms 98.458 ms
8 ae-4.r20.snjsca04.us.bb.gin.ntt.net (129.250.4.103) 93.544 ms 85.011 ms
9 ae-1.r21.plalca01.us.bb.gin.ntt.net (129.250.5.32) 90.292 ms 108.205 ms
10 po-2.r03.plalca01.us.bb.gin.ntt.net (129.250.5.142) 78.070 ms 82.080 ms
11 xe-3-3.r03.plalca01.us.ce.gin.ntt.net (140.174.28.118) 91.133 ms 91.491 ms
12 * *
dallas:
3 vb1300.rar3.dallas-tx.us.xo.net (216.156.0.81) 4 msec 0 msec 4 msec
4 ae0d1.cir1.dallas2-tx.us.xo.net (207.88.13.125) 12 msec 0 msec 4 msec
5 dap-brdr-04.inet.qwest.net (63.146.26.169) 0 msec 0 msec 0 msec
6 snj-core-01.inet.qwest.net (67.14.34.14) 44 msec 44 msec 44 msec
7 snj-edge-01.inet.qwest.net (205.171.233.38) 48 msec 44 msec
snj-edge-01.inet.qwest.net (205.171.233.34) 44 msec
8 67.128.102.202 48 msec 44 msec 44 msec
9 * * *
- spinlocked 16y agoThe wikileaks tweet was 12 hrs ago. Difficult to sustain a DDOS for long periods.
- trotsky 16y agoIf you look at netcraft's realtime global status link it sure seems like they are saying it's ongoing. They show mostly failure from all sites over the past 8 hours, and all locations minus romania failed the last test ~15m ago. http://uptime.netcraft.com/perf/graph?site=www.wikileaks.org http://uptime.netcraft.com/perf/graph?site=www.wikileaks.org They have enviable RTT stability as well, even for a site not being DDOS'd: tsl@crabapple:~> for i in {1..10}; do curl -s -w "%{time_total}\n" -o /dev/null http://wikileaks.org/4oh4$i; done 0.176 0.180 0.177 0.174 0.176 0.174 0.174 0.177 0.174 0.176