BurstNET as usual?

Portal Home > Knowledgebase > Articles Database > BurstNET as usual?

Posted by sysc, 11-27-2003, 02:01 AM
C:\Documents and Settings\Jason>ping 64.191.61.1 Pinging 64.191.61.1 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Reply from 64.191.61.1: bytes=32 time=303ms TTL=237 Ping statistics for 64.191.61.1: Packets: Sent = 4, Received = 1, Lost = 3 (75% loss), Approximate round trip times in milli-seconds: Minimum = 303ms, Maximum = 303ms, Average = 303ms [root@salient root]# ping 64.191.61.1 PING 64.191.61.1 (64.191.61.1) 56(84) bytes of data. 64 bytes from 64.191.61.1: icmp_seq=2 ttl=244 time=478 ms 64 bytes from 64.191.61.1: icmp_seq=4 ttl=244 time=473 ms 64 bytes from 64.191.61.1: icmp_seq=6 ttl=244 time=483 ms 64 bytes from 64.191.61.1: icmp_seq=7 ttl=244 time=478 ms 64 bytes from 64.191.61.1: icmp_seq=8 ttl=244 time=476 ms 64 bytes from 64.191.61.1: icmp_seq=10 ttl=244 time=477 ms 64 bytes from 64.191.61.1: icmp_seq=11 ttl=244 time=630 ms 64 bytes from 64.191.61.1: icmp_seq=12 ttl=244 time=635 ms 64 bytes from 64.191.61.1: icmp_seq=13 ttl=244 time=482 ms 64 bytes from 64.191.61.1: icmp_seq=14 ttl=244 time=472 ms 64 bytes from 64.191.61.1: icmp_seq=15 ttl=244 time=472 ms --- 64.191.61.1 ping statistics --- 16 packets transmitted, 11 received, 31% packet loss, time 15127ms rtt min/avg/max/mdev = 472.843/505.702/635.556/60.126 ms
Posted by CS-Stacie, 11-27-2003, 02:02 AM
Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from IP: bytes=32 time=225ms TTL=47 Request timed out. Request timed out. Reply from IP: bytes=32 time=268ms TTL=47 Request timed out.
Posted by sysc, 11-27-2003, 02:03 AM
Mine's pretty close.
Posted by jusunlee, 11-27-2003, 02:05 AM
heavenly.
Posted by CS-Stacie, 11-27-2003, 02:05 AM
Reply from 12.122.12.54: TTL expired in transit. Reply from 12.122.12.54: TTL expired in transit. Reply from 12.122.12.54: TTL expired in transit. Reply from 12.123.1.126: TTL expired in transit. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from IP: bytes=32 time=481ms TTL=47 Request timed out. Reply from 12.125.39.77: Destination host unreachable. Request timed out. Request timed out. Sorry for the long posts, I know they can become irratating. I'll sit back and wait, I expected it, just not at 1AM, I guess i rather have this happen now when my clients are sleeping
Posted by sysc, 11-27-2003, 02:06 AM
It is becomming the "norm".....
Posted by gret, 11-27-2003, 02:07 AM
Spotcheck Results for Time (US/Eastern) Checked From Result Size Secs 11/27/2003 01:06:33 Los Angeles USA Unable to resolve na N/A 10.03 11/27/2003 01:06:53 Detroit USA Unable to connect N/A 30.47 11/27/2003 01:06:44 Frankfurt GERMANY Unable to resolve na N/A 20.05
Posted by sysc, 11-27-2003, 02:08 AM
What is the non-toll free number again? Need to write it down, usually just go to their site, but since it's down everyday does me no good =)
Posted by CS-Stacie, 11-27-2003, 02:08 AM
I expected their network to become more redundant, after the last attacks.
Posted by elitehst, 11-27-2003, 02:10 AM
1-570-343-2200
Posted by sysc, 11-27-2003, 02:12 AM
"should be fixed soon" "I can not give you any information on that" sigh....
Posted by elitehst, 11-27-2003, 02:14 AM
Yeah, same thing..shoulda put that in my post.......I live 20 mins from the Datacenter...i'm ready to drive up there and knock on the door, and see what they say to me.....
Posted by canfone, 11-27-2003, 02:16 AM
Looks like they are trying to bring their Cogent line backup.. Somehow some of their network is still up.... Tracing route to burst.net [66.96.192.201] over a maximum of 30 hops: 1 31 ms 32 ms 31 ms speede02.access.golden.net 2 47 ms 31 ms 31 ms access-gw.fe0-1-0.core1.ki .39.160.97] 3 31 ms 31 ms 47 ms kitchener-gw.se4-0.core1.t .183.132.17] 4 46 ms 63 ms 47 ms f0-5.na01.b011027-0.yyz01. .250.7.229] 5 31 ms 47 ms 47 ms g1-2.core01.yyz01.atlas.co 229] 6 47 ms 78 ms 47 ms p6-0.core01.bos01.atlas.co 7] 7 47 ms 47 ms 47 ms p5-0.core01.jfk02.atlas.co 8] 8 78 ms 62 ms 47 ms p15-0.core02.jfk02.atlas.c 4] 9 47 ms 47 ms 31 ms p14-0.core01.phl01.atlas.c ] 10 47 ms 46 ms 47 ms g50.ba01.b003003-1.phl01.a 28.5.38] 11 * * * Request timed out. 12 438 ms * 438 ms 66.197.191.45 13 437 ms 438 ms 422 ms burst.net [66.96.192.201]
Posted by sysc, 11-27-2003, 02:16 AM
Anyone submit the sla form for a refund/credit this month? I did, but havnt heard anything.. how long do they usually take to give you some feedback on it?
Posted by sysc, 11-27-2003, 02:19 AM
Back up here, just extremely high pings.
Posted by M7I, 11-27-2003, 02:22 AM
Looks like xo might be down. This is from The Planet. I saw cogent in there a bit ago. (64.191.51.125), 30 hops max, 38 byte pacs 1 69-56-188-209.theplanet.com (69.56.188.209) 0.548 ms 0.543 ms 0.410 ms 2 ibr4-ge-0-0-0-v1.dllstx2.theplanet.com (12.96.160.4) 0.524 ms 0.450 ms 0s 3 ip206-181-190-9.z190-181-206.customer.algx.net (206.181.190.9) 0.530 ms 0s 4 dfw5-edge10-p6-0.atlas.algx.net (165.117.48.9) 0.535 ms 0.616 ms 0.606 ms 5 206.111.5.5.ptr.us.xo.net (206.111.5.5) 0.642 ms 0.698 ms 0.666 ms 6 p5-1-0-3.RAR1.Dallas-TX.us.xo.net (65.106.4.193) 2.023 ms 2.002 ms 1.974s 7 * * * 8 * * * 9 * * * 10 p1-0-0.RAR2.Washington-DC.us.xo.net (65.106.0.5) 39.446 ms 39.359 ms 39.s 11 p4-0-0.MAR2.Philadelphia-PA.us.xo.net (65.106.3.154) 43.112 ms 42.977 ms s 12 p15-0.CHR1.Philadelphia-PA.us.xo.net (207.88.87.46) 42.953 ms 42.994 ms s 13 * * * 14 66.197.191.45 (66.197.191.45) 457.047 ms 458.534 ms 455.681 ms 15 mercury (64.191.51.125) 454.870 ms 454.928 ms 453.109 ms
Posted by CS-Stacie, 11-27-2003, 02:22 AM
I got a reply on that SLA request, and they said they would email me within 48 hours if the request was accepted. It better be accepted =P
Posted by sysc, 11-27-2003, 02:25 AM
Tell me about it, what a bad month eh
Posted by CS-Stacie, 11-27-2003, 02:26 AM
network seems backup, I think you should of waited about 30 minutes before posting, You jumped on it maybe too quick.... thanks very informative I might add.
Posted by HostJedi, 11-27-2003, 02:33 AM
Another DDOS attack. We resolved this one pretty quickly though. Just a few more days until the GIG-E upgrades are completed...Cogent on Friday, and XO the following week. We expect this to allow us to combat such DDOS issues.... SMA PRES/CEO
Posted by blackmoont, 11-27-2003, 04:06 AM
Great . Let have a ddos wat with them j/k
Posted by blackmoont, 11-27-2003, 04:07 AM
Great . Let have a ddos war with them j/k
Posted by deltawolf, 11-27-2003, 04:14 AM
lol...yeah! Great idea! Lets DoS the DDoSers before they can hit us! The total outage was only about 5 minutes, so it wasnt too bad...just pretty annoying.
Posted by sysc, 11-27-2003, 04:20 AM
errrrrrrr ?
Posted by deltawolf, 11-27-2003, 04:21 AM
lol...using their XO, Cogent, Gig-E lines we should be able to take down lil kiddies on 56k.
Posted by FredTT, 11-27-2003, 02:56 PM
I would hope so.