Burst.Net/Nocster Latency Isses Again?

Portal Home > Knowledgebase > Articles Database > Burst.Net/Nocster Latency Isses Again?

Posted by Arsalan, 07-10-2004, 10:50 AM
http://www.space.net/cgi-bin/webtrac...burst.net&ns=y traceroute to burst.net (66.96.192.201), 30 hops max, 38 byte packets 1 Cisco-M-XI-Vlan8.Space.Net (193.149.44.157) 0.831 ms 0.718 ms 0.756 ms 2 Cisco-M-Fa3-0.Space.Net (193.149.44.126) 0.624 ms 0.647 ms 0.468 ms 3 Cisco-M-XII-Fe0-0.Space.Net (195.30.3.210) 0.469 ms 0.778 ms 0.406 ms 4 Cisco-F-V-POS6-1-0.Space.Net (195.30.3.34) 6.493 ms 6.518 ms 6.385 ms 5 DeCIX-Fa2-0.Space.Net (193.149.44.245) 7.513 ms 7.072 ms 7.223 ms 6 cr02.frf02.pccwbtn.net (80.81.192.50) 7.194 ms 7.230 ms 6.862 ms 7 pos2-0.cr01.phl02.pccwbtn.net (63.218.30.33) 109.983 ms 110.711 ms 109.123 ms 8 * hostnoc.ge3-0.2.cr01.phl02.pccwbtn.net (63.218.31.6) 343.363 ms 345.581 ms 9 * * * 10 * burst.net (66.96.192.201) 594.109 ms * 500+ms delays with packet loss. Not good!
Posted by HostJedi, 07-10-2004, 10:52 AM
Yep, another DDOS. :-( Working on it...
Posted by Arsalan, 07-10-2004, 10:54 AM
BurstNET, Thanks for the update! Nice to know some one is waching our back
Posted by jeromegn, 07-10-2004, 10:56 AM
At least that was a fast answer. Now we need fast fixing! Regards, Jerome Gravel-Niquet
Posted by HostJedi, 07-10-2004, 10:57 AM
We work on these as quickly as we can. Some are just harder than others to track down...
Posted by Arsalan, 07-10-2004, 11:06 AM
traceroute to burst.net (66.96.192.201), 30 hops max, 38 byte packets 1 Cisco-M-XI-Vlan8.Space.Net (193.149.44.157) 0.864 ms 0.674 ms 0.736 ms 2 Cisco-M-Fa3-0.Space.Net (193.149.44.126) 0.593 ms 0.555 ms 0.599 ms 3 Cisco-M-XII-Fe0-0.Space.Net (195.30.3.210) 0.472 ms 0.650 ms 0.377 ms 4 Cisco-F-V-POS6-1-0.Space.Net (195.30.3.34) 6.462 ms 6.336 ms 6.313 ms 5 DeCIX-Fa2-0.Space.Net (193.149.44.245) 6.879 ms 7.153 ms 6.854 ms 6 cr02.frf02.pccwbtn.net (80.81.192.50) 6.853 ms 6.879 ms 7.049 ms 7 pos2-0.cr01.phl02.pccwbtn.net (63.218.30.33) 109.419 ms 109.248 ms 109.726 ms 8 hostnoc.ge3-0.2.cr01.phl02.pccwbtn.net (63.218.31.6) 346.770 ms * * 9 ge-7-0-ctsi.rtr0.scra1.hostnoc.net (66.197.191.45) 577.235 ms * 575.738 ms 10 burst.net (66.96.192.201) 575.702 ms 585.549 ms 574.464 ms its already getting better..
Posted by Arsalan, 07-10-2004, 11:28 AM
6 cr02.frf02.pccwbtn.net (80.81.192.50) 7.021 ms 7.413 ms 7.132 ms 7 pos2-0.cr01.phl02.pccwbtn.net (63.218.30.33) 109.088 ms 109.385 ms 109.094 ms 8 hostnoc.ge3-0.2.cr01.phl02.pccwbtn.net (63.218.31.6) 341.932 ms * * 9 * * * 10 * * * 11 * * * 12 * * * 13 burst.net (66.96.192.201) 608.398 ms 592.265 ms * Still there
Posted by nick[x1], 07-10-2004, 12:14 PM
Its painful without my server o well i will live. It looks like it just came back
Posted by ZoneServ.com, 07-10-2004, 12:36 PM
ping 600+!!! 90%+ packet loss.. clients getting pisst off. Gil.
Posted by HostJedi, 07-10-2004, 12:49 PM
<< ping 600+!!! 90%+ packet loss.. >> Post a traceroute please. The majority of flooding has been stopped, and you should be seeing less than 10% packet loss right now. We are working on remainder still... Last edited by HostJedi; 07-10-2004 at 12:59 PM.
Posted by Hwu, 07-10-2004, 01:19 PM
getting better
Posted by ZoneServ.com, 07-10-2004, 01:21 PM
I live in isarel(asia), packet loss is better now. thought still ping 500+-, i can't tracert its just times out everything after my router. Gil.
Posted by Spider210, 07-10-2004, 01:21 PM
I guess its getting somewhat better Ping statistics for 66.96.192.201: Packets: Sent = 1636, Received = 1460, Lost = 176 (10% loss), Approximate round trip times in milli-seconds: Minimum = 37ms, Maximum = 507ms, Average = 183ms
Posted by ZoneServ.com, 07-10-2004, 01:22 PM
C:\tracert burst.net Tracing route to burst.net [66.96.192.201] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms SpeedTouch.lan [10.0.0.138] 2 * * * Request timed out. 3 * * * Request timed out. 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 330 ms 1450 ms 323 ms burst.net [66.96.192.201] Trace complete.
Posted by ZoneServ.com, 07-10-2004, 01:25 PM
Pinging ***.com [66.197.173.***] with 32 bytes of data: Request timed out. Reply from 66.197.173.***: bytes=32 time=462ms TTL=52 Reply from 66.197.173.***: bytes=32 time=483ms TTL=52 Reply from 66.197.173.***: bytes=32 time=465ms TTL=52 Ping statistics for 66.197.173.***: Packets: Sent = 4, Received = 3, Lost = 1 (25% loss), Approximate round trip times in milli-seconds: Minimum = 462ms, Maximum = 483ms, Average = 470ms :\
Posted by nick[x1], 07-10-2004, 02:18 PM
I cant even access any my server now or burst.net
Posted by Spider210, 07-10-2004, 02:29 PM
It seems to be getting worse again. Burst any news???
Posted by above, 07-10-2004, 02:53 PM
Why are you being attacked ? Request timed out. Reply from 66.197.x.x: bytes=32 time=377ms TTL=117 Request timed out. Reply from 66.197.x.x: bytes=32 time=388ms TTL=117 Reply from 66.197.x.x: bytes=32 time=388ms TTL=117 Reply from 66.197.x.x: bytes=32 time=398ms TTL=117 Request timed out. Request timed out.
Posted by Arsalan, 07-10-2004, 03:06 PM
Its better now, but still the ping timings are way out 12 p14-0.core01.phl01.atlas.cogentco.com (66.28.4.2) 100.633 ms 100.786 ms 100.724 ms 13 g8.ba21.b003003-1.phl01.atlas.cogentco.com (38.112.34.142) 97.242 ms 100.645 ms 100.094 ms 14 BurstNet.demarc.cogentco.com (38.112.11.122) 103.409 ms 103.518 ms 103.315 ms 15 ge-7-0-ctsi.rtr0.scra1.hostnoc.net (66.197.191.45) 254.149 ms 257.672 ms * 16 burst.net (66.96.192.201) 260.958 ms 262.892 ms 260.394 ms They have thousands of dedicated servers, any one of them could be under attack.
Posted by RHChristian, 07-10-2004, 03:20 PM
Little off topic, but if you're trying to hide something then hide your username as it is the domain you're tracing. Pings seem stable at 340MS +/-, not getting much packet loss here.
Posted by Cirtex, 07-10-2004, 04:33 PM
It seems to be only getting worse?
Posted by Shaw Networks, 07-10-2004, 04:39 PM
I can only reccomend for anyone hosted by BurstNET to get out while you can. I had a server with them a while back and it was absolutely horrible; I signed up and quit within the same month it was so bad. Had more downtime then uptime.
Posted by Joshua, 07-10-2004, 05:01 PM
Nice self promotion, as you're a competitor, and just happen to leave your signature on. The issue is affecting servers in the new section, more than the servers in the old. I see that you host IRC servers at FDC... I had a bad experience with them a year ago, so... get out while you can. Also, there were no months that Burst was down for more time than they were up... get your facts straight. -Josh
Posted by HostJedi, 07-10-2004, 05:12 PM
Thanks for the recommendation. I'm sure your new provider can handle incoming attacks from thousands of locations then...
Posted by Shaw Networks, 07-10-2004, 06:01 PM
Joshua: I am hardly a competitor of BurstNET who provides mainly dedicated server solutions and we only reseller dedicated server solutions. I am giving these people dire advice to beware of the problems that BurstNET has. And to clarify, the time that I was with them no we weren't down more than we were up but there were 15 days where there was complete downtime or serious problems of some sort i.e. all of our cPanel licenses were disabled for a while. Hope some people find this helpful.
Posted by Spider210, 07-10-2004, 06:02 PM
When will this stop!?!?!?
Posted by HostJedi, 07-10-2004, 06:15 PM
<< there were 15 days where there was complete downtime or serious problems of some sort i.e. all of our cPanel licenses were disabled for a while. >> Not quite...this was three days only - Feb 29th thru March 2nd. You seem to like to exaggerate quite a bit. Since then our network has been pretty solid, with only a core switch failure that was replaced in less than an hour, and a few minor ddos attacks. Our network has been more solid since then that a lot of popular competitors networks...just count the number of threads in the outages section here in WHT the past 4 months... Today's DDoS is quote complex, and we have been working to resolve it non-stop since it started.
Posted by above, 07-10-2004, 06:15 PM
any explanation on why its happening ?
Posted by HostJedi, 07-10-2004, 06:18 PM
<< any explanation on why its happening ? >> No idea, and it makes no difference in a resolution in this case. Probably just some kid playing games, and angry that he lost a game o something to that affect. We know the server/ip that it is targetted at, but it's proving to be a complex attack that is not easy to resolve as most.
Posted by Angelo, 07-10-2004, 06:20 PM
Some foolish kids maybe.. Please leave our Burst.NET in peace! )
Posted by Spider210, 07-10-2004, 06:23 PM
Ok kiddies you have had your fun... NOW LEAVE OUR BURST.NET ALONE!
Posted by Spider210, 07-10-2004, 06:42 PM
Pings are down in the 90's here (40's normal)
Posted by mainarea, 07-10-2004, 06:47 PM
Looks normal now to me, they're trying a few new things. Let's hope it's worked. - Matt
Posted by ZoneServ.com, 07-10-2004, 06:59 PM
Still bad from here.. BTW, the server i was tracing is ZoneServ.com my company :\.. lol i was bored so I used *** ! Hate those kiddies! leave us alone.. and get a life! Best regards, Gil.
Posted by ZoneServ.com, 07-10-2004, 07:03 PM
Oh sorry, just checked everything looks fine.. Thank you burst.net! Gil.
Posted by bhaputi, 07-10-2004, 07:23 PM
This has been resolved. Just in time for the very nice sunny saturday to be over with....
Posted by sightz, 07-10-2004, 07:30 PM
Has anyone looked at the Network Status section on the Burstnet "support" forums?!? They have had at least 5 DDOS's this month alone! Even if they were a great data center who cared about their customers, how do you people justify staying with someone who has made enough enemies to be DDOSed every 6 days? WHY are they being DDOSed weekly? WHY can't they deal with it? WHY don't other big DC's suffer from this? All I can say is that we are happy to have been Burst-free for 108 days now: No downtime, (as in ZERO - ZILCH - NONE) no weekly DDOS's, no "somebody cut a fiber somewhere", no "it was the telco's fault", no "fire at somebody else's location that has mysteriously killed our network", no "we though it was redundant but it wasn't" no sunspots, aliens, russkies, northern lights, black hellicopters, geo-magnetic shifts either Your mileage may vary.
Posted by above, 07-10-2004, 07:44 PM
hmm maybe i should have read their forums first... oh well
Posted by hostbox, 07-10-2004, 08:14 PM
Keep it up. Burst free. That is my Recommendation. If you don't like how they do business keep distanced from them, use another company instead. BurstNET is not the last Coke in the Dessert you know?
Posted by Dacsoft, 07-10-2004, 08:21 PM
Where do you see "at least 5"? I just looked at the Network Status section and only see 3 (1st, 9th, and today). BurstNet has upset enough people over the years. They probably initiated the DDOS for the same reason you feel compelled to post negative remarks in this thread even though you have been "Burst free" for 108 days -- they want to hurt the company. I apologize if this comes across too negative. I just don't see any positive reason for the negative posts. There are plenty of "what do you think about Burst.Net" threads out there. I use this specific thread to find out status and see how it is effecting everybody else.
Posted by Spider210, 07-10-2004, 08:26 PM
hmm pings are back and speeds were too but now I am down to only being able to pull 8kbs from it... anyone else?
Posted by Dacsoft, 07-10-2004, 08:33 PM
Right now I am getting 340+ when downloading. Didnt' try uploading.
Posted by hostbox, 07-10-2004, 09:12 PM
Moving out eh?
Posted by whmcsguru, 07-10-2004, 10:23 PM
Read through the forums, specifically this downtime related ones. This is BN's excuse for 99% of their downtimes. When will it stop? When the staff @ BN actually understand how to run a network and realize that widening the pipes won't do jack to stop the real problems. Preventative measures must be taken, unfortunately, for 3 years (or longer), Burst has failed to take them. As someone said: get out while you still have business. It's a very true statement.
Posted by Arsalan, 07-10-2004, 10:31 PM
Things seem to be running quite smoothly right now.. traceroute to burst.net (66.96.192.201), 30 hops max, 38 byte packets 1 Cisco-M-XI-Vlan8.Space.Net (193.149.44.157) 2.635 ms 0.926 ms 0.897 ms 2 Cisco-M-Fa3-0.Space.Net (193.149.44.126) 0.874 ms 0.465 ms 0.441 ms 3 Cisco-M-XII-Fe0-0.Space.Net (195.30.3.210) 0.596 ms 0.491 ms 0.338 ms 4 Cisco-F-V-POS6-1-0.Space.Net (195.30.3.34) 15.554 ms 6.324 ms 6.276 ms 5 DeCIX-Fa2-0.Space.Net (193.149.44.245) 6.875 ms 6.741 ms 6.756 ms 6 f6-0.core01.fra01.atlas.cogentco.com (80.81.192.63) 6.764 ms 6.819 ms 6.967 ms 7 p5-0.core01.ams03.atlas.cogentco.com (130.117.1.61) 13.698 ms 13.783 ms 14.058 ms 8 p5-0.core01.lon01.atlas.cogentco.com (130.117.1.58) 22.263 ms 22.803 ms 22.377 ms 9 p6-0.core01.jfk01.atlas.cogentco.com (154.54.1.57) 97.527 ms 97.300 ms 94.562 ms 10 p15-0.core02.jfk01.atlas.cogentco.com (66.28.4.166) 97.675 ms 96.026 ms 97.581 ms 11 p12-0.core02.jfk02.atlas.cogentco.com (66.28.4.169) 94.745 ms 94.952 ms 97.760 ms 12 p14-0.core01.phl01.atlas.cogentco.com (66.28.4.2) 100.068 ms 99.907 ms 97.183 ms 13 g8.ba21.b003003-1.phl01.atlas.cogentco.com (38.112.34.142) 100.170 ms 97.475 ms 100.099 ms 14 BurstNet.demarc.cogentco.com (38.112.11.122) 103.730 ms 103.380 ms 97.117 ms 15 ge-7-0-ctsi.rtr0.scra1.hostnoc.net (66.197.191.45) 108.806 ms 107.867 ms 101.553 ms 16 burst.net (66.96.192.201) 109.094 ms 108.350 ms 108.117 ms
Posted by mainarea, 07-10-2004, 10:47 PM
Most of the DDOS attacks are not service affecting, or only have an effect on one VLAN/server. Notice the lack of complaints lately. Burst isn't the one being targetted most likely, it's probably a client. They host over 1500 servers, remember... Burst frequently announces when they are being DDOSed, even if it is not service affecting. I can guarantee that at your current host, if they are large enough, get small DDOS attacks on a regular basis. Small DDOS attacks are easy to filter. Large ones are not. Is that still happening? We didn't receive any complaints from other clients on our main VLAN which you're on, and Dacsoft's server is also on that VLAN. It may have been your ISP, or just a quick drop off for some odd reason. - Matt
Posted by Spider210, 07-10-2004, 10:49 PM
Speeds are back now
Posted by Arsalan, 07-11-2004, 05:10 AM
Yep, but cpanel.net is down.. cant run the mail server updates that i wanted to.. I guess bad timing.
Posted by mainarea, 07-11-2004, 10:02 AM
CPanel.net was down due to the DedicatedNow/PWebTech move, and is still down at this time for many people. - Matt
Posted by Arsalan, 07-11-2004, 11:05 AM
Matt, I know, but since i couldent get into the server since yesterday (too much lag), i could not work on a failing exim mail server. I logged in today, and just as i was running the exim rebuild, found cpanel to be down So, right now i have a server with 250 sites, and not accepting mail
Posted by Spider210, 07-11-2004, 12:33 PM
hmmm where did www.burst.net go and ALL OF THE SERVERS!
Posted by HostJedi, 07-11-2004, 12:36 PM
BGP reload...takes a few seconds...
Posted by Spider210, 07-11-2004, 12:38 PM
ok thanks its back now
Posted by Arsalan, 07-11-2004, 12:41 PM
Yep, back now..
Posted by mainarea, 07-11-2004, 12:53 PM
Nice, I now get 18ms pings going over Level3 incoming & outgoing. - Matt