<< Hopefully this can be resolved soon once and for all. >>
Unfortunately, it is out of our direct control.
We rely on our vendor to provide updates to the DDOS gear, and sometimes the updates they provide cause these kind of issues.
It's a "worse of two evils" situation....when working...the Top Layer unuts are great, but they cause their own sporadic issues unfortunately :-(
There do FAR more good than bad for the nework, block 99% of the DDOS we receive.
We get hit with DDOS 24/7 constant, and our client base does not know/realize this due to the Top Layers doing there job.
Anybody able to reach 126.96.36.199 from a non-Burst site? I've tried charter, softlayer, qwest, direcway, and earthlink. Been dead since yesterday's blip. Burst tech support says that it's a networking problem, but that the network guys are tucked home all snug in their beds, and can't be disturbed.
However, they also say they have been able to reach it from offsite, but I have yet to be able to...
It also responds just fine from inside Burst via another machine, so it's not hardware or internal networking.
So it's hard to tell who's stretching the truth.
So if you can post a traceroute that gets past yipes.com, I'd love to see it...
10 so-3-0-0.mp1.Philadelphia1.Level3.net (188.8.131.52) 121.658 ms so-1-0-0.mp2.Philadelphia1.Level3.net (184.108.40.206) 120.948 ms 120.886 ms
11 so-10-0.hsa1.Philadelphia1.Level3.net (220.127.116.11) 121.374 ms so-11-0.hsa1.Philadelphia1.Level3.net (18.104.22.168) 120.709 ms so-10-0.hsa1.Philadelphia1.Level3.net (22.214.171.124) 120.670 ms
12 unknown.Level3.net (126.96.36.199) 120.813 ms 121.909 ms 121.978 ms
13 ge-1-3-0.phl004jp02.yipes.com (188.8.131.52) 122.157 ms 121.065 ms 121.372 ms