Burst/Nocster Down

Portal Home > Knowledgebase > Articles Database > Burst/Nocster Down

Posted by SWDevil, 12-01-2003, 03:16 PM
is it just me..or others are seeing the same? Sites are taking forever to load....
Posted by eBoundary, 12-01-2003, 03:22 PM
--- nocster.com ping statistics --- 53 packets transmitted, 53 packets received, 0% packet loss round-trip min/avg/max = 13.979/15.937/32.254 ms I dont know of an actual box inside their network, but their main server looks fine.
Posted by server4sale, 12-01-2003, 03:36 PM
ALL servers fine here DO a tracert and see
Posted by SWDevil, 12-01-2003, 04:05 PM
Hum.. sites on my server are working very very very very slow.. hum.. and when I ping it.. I am getting .... (I am pinging from http://www.all-nettools.com/tools1.htm ) P.S.. you can try pinging needscripts.com
Posted by choon, 12-01-2003, 04:08 PM
Most likely it might just your server or your connectivity issue or else I will be notified by my client. So, please ping and/or traceroute to your server IP to see what's up. Then send those results to nocster support so that they can resolve the issue if it is the problem from their end.
Posted by thedavid, 12-01-2003, 04:10 PM
100% uptime and no packet loss as measured from the ev1.net datacenter for the past 24 hours for multiple servers. There may be other issues at hand. Also, FWIW - this post really belongs in here: http://www.webhostingtalk.com/forumd...?s=&forumid=59 -David
Posted by choon, 12-01-2003, 04:13 PM
Ping test from Atjeu's server: ping -c 30 needscripts.com PING needscripts.com (64.191.116.135) 56(84) bytes of data. 64 bytes from 64.191.116.135: icmp_seq=1 ttl=55 time=163 ms 64 bytes from 64.191.116.135: icmp_seq=2 ttl=55 time=194 ms 64 bytes from 64.191.116.135: icmp_seq=3 ttl=55 time=206 ms 64 bytes from 64.191.116.135: icmp_seq=4 ttl=55 time=151 ms 64 bytes from 64.191.116.135: icmp_seq=5 ttl=55 time=210 ms 64 bytes from 64.191.116.135: icmp_seq=7 ttl=55 time=125 ms 64 bytes from 64.191.116.135: icmp_seq=8 ttl=55 time=174 ms 64 bytes from 64.191.116.135: icmp_seq=10 ttl=55 time=145 ms 64 bytes from 64.191.116.135: icmp_seq=11 ttl=55 time=211 ms 64 bytes from 64.191.116.135: icmp_seq=12 ttl=55 time=233 ms 64 bytes from 64.191.116.135: icmp_seq=13 ttl=55 time=160 ms 64 bytes from 64.191.116.135: icmp_seq=14 ttl=55 time=159 ms 64 bytes from 64.191.116.135: icmp_seq=16 ttl=55 time=162 ms 64 bytes from 64.191.116.135: icmp_seq=17 ttl=55 time=189 ms 64 bytes from 64.191.116.135: icmp_seq=18 ttl=55 time=220 ms 64 bytes from 64.191.116.135: icmp_seq=19 ttl=55 time=165 ms 64 bytes from 64.191.116.135: icmp_seq=20 ttl=55 time=215 ms 64 bytes from 64.191.116.135: icmp_seq=21 ttl=55 time=206 ms 64 bytes from 64.191.116.135: icmp_seq=22 ttl=55 time=171 ms 64 bytes from 64.191.116.135: icmp_seq=24 ttl=55 time=173 ms 64 bytes from 64.191.116.135: icmp_seq=25 ttl=55 time=143 ms 64 bytes from 64.191.116.135: icmp_seq=26 ttl=55 time=121 ms 64 bytes from 64.191.116.135: icmp_seq=27 ttl=55 time=206 ms 64 bytes from 64.191.116.135: icmp_seq=29 ttl=55 time=194 ms 64 bytes from 64.191.116.135: icmp_seq=30 ttl=55 time=226 ms --- needscripts.com ping statistics --- 30 packets transmitted, 25 received, 16% packet loss, time 29247ms rtt min/avg/max/mdev = 121.208/181.371/233.148/30.924 ms Ping test from my desktop (in Singapore): ping -c 30 needscripts.com PING needscripts.com (64.191.116.135) 56(84) bytes of data. 64 bytes from 64.191.116.135: icmp_seq=0 ttl=48 time=300 ms 64 bytes from 64.191.116.135: icmp_seq=1 ttl=48 time=283 ms 64 bytes from 64.191.116.135: icmp_seq=3 ttl=48 time=284 ms 64 bytes from 64.191.116.135: icmp_seq=4 ttl=48 time=288 ms 64 bytes from 64.191.116.135: icmp_seq=6 ttl=48 time=304 ms 64 bytes from 64.191.116.135: icmp_seq=7 ttl=48 time=295 ms 64 bytes from 64.191.116.135: icmp_seq=8 ttl=48 time=288 ms 64 bytes from 64.191.116.135: icmp_seq=9 ttl=48 time=317 ms 64 bytes from 64.191.116.135: icmp_seq=10 ttl=48 time=321 ms 64 bytes from 64.191.116.135: icmp_seq=11 ttl=48 time=315 ms 64 bytes from 64.191.116.135: icmp_seq=13 ttl=48 time=306 ms 64 bytes from 64.191.116.135: icmp_seq=15 ttl=48 time=320 ms 64 bytes from 64.191.116.135: icmp_seq=16 ttl=48 time=301 ms 64 bytes from 64.191.116.135: icmp_seq=17 ttl=48 time=300 ms 64 bytes from 64.191.116.135: icmp_seq=18 ttl=48 time=308 ms 64 bytes from 64.191.116.135: icmp_seq=19 ttl=48 time=313 ms 64 bytes from 64.191.116.135: icmp_seq=20 ttl=48 time=292 ms 64 bytes from 64.191.116.135: icmp_seq=21 ttl=48 time=312 ms 64 bytes from 64.191.116.135: icmp_seq=23 ttl=48 time=302 ms 64 bytes from 64.191.116.135: icmp_seq=24 ttl=48 time=290 ms 64 bytes from 64.191.116.135: icmp_seq=25 ttl=48 time=287 ms 64 bytes from 64.191.116.135: icmp_seq=26 ttl=48 time=312 ms 64 bytes from 64.191.116.135: icmp_seq=28 ttl=48 time=314 ms --- needscripts.com ping statistics --- 30 packets transmitted, 23 received, 23% packet loss, time 29228ms rtt min/avg/max/mdev = 283.522/302.823/321.786/11.867 ms, pipe 2
Posted by Odd Fact, 12-01-2003, 04:23 PM
And moved.
Posted by mrl14, 12-01-2003, 04:24 PM
Yes some users are reporting massive slow downs. I'm ok, but a few clients that are a few KM away from me are having slowdowns. I also usually route through cogent, but now i'm going through XO, it's possible cogent went down?
Posted by thedavid, 12-01-2003, 04:28 PM
Here's what I'm seeing from there: 40 packets transmitted, 40 received, 0% loss, time 39390ms rtt min/avg/max/mdev = 47.083/47.438/47.797/0.349 ms Can you post a trace? Should show where things are getting kinked up at.
Posted by Przemek, 12-01-2003, 04:34 PM
My packets go through XO and it's very very slow. 20 packets transmitted, 12 received, 40% packet loss
Posted by choon, 12-01-2003, 04:37 PM
From Atjeu's server: /usr/sbin/traceroute needscripts.com traceroute to needscripts.com (64.191.116.135), 30 hops max, 38 byte packets 1 Atjeu_Gateway (69.50.192.1) 0.445 ms 0.267 ms 0.274 ms 2 wsip-66-210-249-9.ph.ph.cox.net (66.210.249.9) 1.357 ms 1.805 ms 0.916 ms 3 ip68-2-7-202.ph.ph.cox.net (68.2.7.202) 1.397 ms 1.135 ms 2.291 ms 4 ip68-2-0-17.ph.ph.cox.net (68.2.0.17) 1.848 ms 1.709 ms 1.421 ms 5 ip68-2-0-9.ph.ph.cox.net (68.2.0.9) 2.845 ms 2.731 ms 2.957 ms 6 chnddsrc02-gew0601.rd.ph.cox.net (68.2.14.29) 15.963 ms 3.008 ms 3.877 ms 7 chndbbrc02-pos0101.rd.ph.cox.net (68.1.0.168) 2.511 ms 4.171 ms 3.725 ms 8 so-1-0.hsa1.Phoenix1.Level3.net (64.154.128.29) 5.219 ms 4.333 ms 4.187 ms 9 ge-6-0-0.mp2.Phoenix1.Level3.net (64.159.3.109) 5.428 ms 9.279 ms 11.995 ms 10 so-0-1-0.bbr1.LosAngeles1.Level3.net (64.159.1.125) 16.090 ms 14.595 ms 15.607 ms 11 unknown.Level3.net (209.247.9.142) 13.837 ms 13.727 ms 14.999 ms 12 xo-level3-oc12.LosAngeles1.Level3.net (209.0.227.34) 14.752 ms 14.464 ms 14.275 ms 13 p4-0-0.RAR2.LA-CA.us.xo.net (65.106.5.49) 14.435 ms 18.281 ms 16.133 ms 14 p6-0-0.RAR1.Dallas-TX.us.xo.net (65.106.0.13) 50.647 ms 64.829 ms 49.753 ms 15 p0-0-0-0.RAR2.Dallas-TX.us.xo.net (65.106.1.38) 48.277 ms 48.270 ms 48.038 ms 16 p6-0-0.RAR1.Atlanta-GA.us.xo.net (65.106.0.9) 77.983 ms 77.079 ms 78.536 ms 17 p0-0-0-0.RAR2.Atlanta-GA.us.xo.net (65.106.1.26) 77.284 ms 83.022 ms 76.842 ms 18 p1-0-0.RAR2.Washington-DC.us.xo.net (65.106.0.5) 86.041 ms 84.513 ms 86.574 ms 19 p4-0-0.MAR2.Philadelphia-PA.us.xo.net (65.106.3.154) 88.969 ms 88.177 ms 88.831 ms 20 p15-0.CHR1.Philadelphia-PA.us.xo.net (207.88.87.46) 88.382 ms 88.415 ms 89.210 ms 21 66-236-204-10.hostnoc.net (66.236.204.10) 131.868 ms 90.609 ms 81.615 ms 22 66.197.191.45 (66.197.191.45) 88.423 ms 101.809 ms 101.658 ms 23 64.191.116.135 (64.191.116.135) 126.532 ms 124.714 ms 134.385 ms From my home connection in Singapore: /usr/sbin/traceroute needscripts.com traceroute to needscripts.com (64.191.116.135), 30 hops max, 38 byte packets 1 192.168.2.1 (192.168.2.1) 0.759 ms 0.815 ms 0.725 ms 2 10.17.0.1 (10.17.0.1) 20.377 ms 10.600 ms 13.471 ms 3 172.20.17.65 (172.20.17.65) 14.425 ms 14.223 ms 7.817 ms 4 172.26.17.1 (172.26.17.1) 8.922 ms 10.966 ms 15.776 ms 5 172.20.6.7 (172.20.6.7) 14.561 ms 12.290 ms 14.730 ms 6 61.8.233.25 (61.8.233.25) 12.916 ms 19.305 ms 11.438 ms 7 ge-0-0-0.r00.sngpsi01.sg.bb.verio.net (61.8.234.61) 12.479 ms 21.403 ms 12.072 ms 8 p1-0-1-3.r80.sttlwa01.us.bb.verio.net (129.250.3.33) 185.612 ms 179.853 ms 180.084 ms MPLS Label=273200 CoS=3 TTL=1 S=0 9 p16-0-1-2.r20.sttlwa01.us.bb.verio.net (129.250.2.68) 174.690 ms 190.440 ms 175.257 ms MPLS Label=435697 CoS=3 TTL=1 S=0 10 p16-0-0-0.r03.sttlwa01.us.bb.verio.net (129.250.2.15) 191.830 ms 192.986 ms 176.857 ms 11 so1-2-0-622M.ar4.SEA1.gblx.net (208.51.243.5) 204.592 ms 215.731 ms 202.079 ms 12 pos3-0-2488M.cr1.SEA1.gblx.net (67.17.71.205) 206.111 ms 204.333 ms 204.616 ms 13 pos1-0-2488M.cr2.JFK1.gblx.net (67.17.72.10) 270.915 ms pos1-0-2488M.cr1.JFK1.gblx.net (67.17.72.6) 276.135 ms 266.191 ms 14 so0-0-0-2488M.ar1.JFK1.gblx.net (67.17.72.14) 267.827 ms 276.781 ms so3-0-0-2488M.ar1.JFK1.gblx.net (67.17.72.18) 268.111 ms 15 * * * 16 pos-5-0-cmbn.rtr0.phla.hostnoc.net (66.197.191.29) 316.353 ms 260.193 ms 262.169 ms 17 66.197.191.45 (66.197.191.45) 266.336 ms 288.110 ms 282.947 ms 18 * 64.191.116.135 (64.191.116.135) 305.357 ms 302.993 ms
Posted by solboy, 12-01-2003, 04:49 PM
My sites are slow also. Their support told me that they were looking into it. Then the AOL support went offline..... as usual
Posted by CybexHost, 12-01-2003, 04:54 PM
Well, what are we going to do? As usual, people will be upset... It's still slow for me.
Posted by bhaputi, 12-01-2003, 05:17 PM
We are currently investigating some possible issues with Cogent that could be affecting some of our customers. This would likely only affect certain customers coming in via certain paths.
Posted by mrl14, 12-01-2003, 05:22 PM
Ok please update us on the burst forums as we shouldn't have to come here Thanks
Posted by Innerplanet, 12-01-2003, 05:26 PM
Slow here also........I'll check the Burst forums.
Posted by MikeMc, 12-01-2003, 05:37 PM
For me it's 5 minutes that is not slow but completely dead (Cogent -> Nocster). I also notice that when at moments they change to xo or gblx, pings are lower but not good at all. Of course this is what I see. So it's not just cogent ..maybe. edit : now it goes through xo for me but still slow.
Posted by MikeMc, 12-01-2003, 05:37 PM
oops..sorry for the double post...I had for a moment browser issues. Mods, please delete this post. Thanks.
Posted by Innerplanet, 12-01-2003, 06:04 PM
I can't even get the Burst Forums to load.......
Posted by sysc, 12-01-2003, 06:15 PM
1 69.28.171.1 (69.28.171.1) 0.372 ms 0.280 ms 0.263 ms 2 so0-3-0.jr1.phx1.llnw.net (69.28.139.225) 0.804 ms 0.706 ms 0.726 ms 3 g6-0.hr2.phx1.gblx.net (64.211.60.165) 0.689 ms 0.647 ms 0.663 ms 4 pos5-2-622M.cr1.PHX1.gblx.net (67.17.72.186) 0.781 ms 0.745 ms pos2-1-622M.cr1.PHX1.gblx.net (67.17.71.37) 0.819 ms 5 pos1-0-2488M.cr1.JFK1.gblx.net (67.17.72.6) 55.523 ms 55.428 ms 55.519 ms 6 so0-0-0-2488M.ar1.JFK1.gblx.net (67.17.72.14) 55.618 ms 65.566 ms 56.978 ms 7 Customer.ge-2-1-0.ar1.JFK1.gblx.net (64.215.82.150) 56.053 ms 55.895 ms 55.734 ms 8 pos-5-0-cmbn.rtr0.phla.hostnoc.net (66.197.191.29) 449.515 ms 555.361 ms 473.391 ms 9 66.197.191.45 (66.197.191.45) 794.219 ms 724.453 ms * Doesnt look like a cogent issue to me, but blame it on them
Posted by peruda.com, 12-01-2003, 06:26 PM
The whole Burst network has been extremely slow for me during the past couple hours. Exemplary traceroute: C:\>tracert root.burst.net Tracing route to root.burst.net [66.96.192.201] over a maximum of 30 hops: 1 5 ms 4 ms 4 ms 192.168.2.1 2 19 ms * 20 ms c-67-160-84-1.client.comcast.net [67.160.84.1] 3 19 ms * 25 ms 12.244.82.97 4 24 ms * 22 ms 12.244.64.65 5 21 ms * 16 ms 12.119.199.21 6 23 ms * 19 ms gbr2-p20.st6wa.ip.att.net [12.123.44.150] 7 30 ms * 22 ms tbr1-p012601.st6wa.ip.att.net [12.122.12.161] 8 19 ms * * ggr1-p340.st6wa.ip.att.net [12.123.44.129] 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. Things seem to be better now, but pings are still timing out far too often. I don't have enough knowledge about the backbone providers and BGP etc . . . Does the trace above indicate that the problem was in AT&T's network? Or just after it? Or something else entirely? Thanks! -John
Posted by Innerplanet, 12-01-2003, 06:41 PM
Ok, same here. All is back to norm (for now). I thought this was going to end up like another one of those 200+ posts about Burst threads.
Posted by Przemek, 12-01-2003, 06:47 PM
But still the pings response is extremly high: 2 62.29.255.65 41ms None 3 62.29.240.162 55ms e-waw-dbp-r01p10.plwaw.energis.pl 4 207.218.80.49 96ms so-1-3-1.ar2.FRA2.gblx.net 5 67.17.65.53 68ms pos5-0-2488M.cr2.FRA2.gblx.net 6 67.17.71.254 151ms pos0-0-2488M.cr1.JFK1.gblx.net 7 67.17.72.14 151ms so0-0-0-2488M.ar1.JFK1.gblx.net 8 64.215.82.150 549ms Customer.ge-2-1-0.ar1.JFK1.gblx.net 9 66.197.191.29 563ms pos-5-0-cmbn.rtr0.phla.hostnoc.net 10 66.197.191.45 769ms None 11 66.197.2xx.xxx 783ms my.server.here
Posted by HADhost, 12-01-2003, 08:45 PM
Good thing I don't host anyone on this network anymore, but I still have a server left there til it expires and it would be nice to be able to throw some files up there for friends that don't need critical speed and uptime (cause they sure as hell won't get it from a nocster server). Anyway, here's the tracert to my server Tracing route to 64.191.40.xx over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 * * * Request timed out. 3 32 ms 15 ms 18 ms 12.244.27.17 4 27 ms 36 ms 40 ms 12.244.71.78 5 15 ms 13 ms 27 ms 12.244.73.138 6 23 ms 19 ms 19 ms gbr2-p70.dvmco.ip.att.net [12.123.36.78] 7 42 ms 20 ms 13 ms gbr3-p80.dvmco.ip.att.net [12.122.5.25] 8 50 ms 64 ms 59 ms tbr2-p013801.sffca.ip.att.net [12.122.12.129] 9 39 ms 38 ms 67 ms ggr1-p3100.sffca.ip.att.net [12.122.11.230] 10 67 ms 40 ms 48 ms p14-0.IR1.PaloAlto-CA.us.xo.net [206.111.12.145] 11 57 ms 46 ms 40 ms p5-0-0.RAR1.SanJose-CA.us.xo.net [65.106.5.173] 12 94 ms 95 ms 97 ms p1-0-0.RAR1.Washington-DC.us.xo.net [65.106.0.37] 13 92 ms 93 ms 97 ms p4-0-0.MAR1.Philadelphia-PA.us.xo.net [65.106.3.150] 14 97 ms 96 ms 111 ms p0-0.CHR1.Philadelphia-PA.us.xo.net [207.88.87.42] 15 97 ms 114 ms 99 ms 66-236-204-10.hostnoc.net [66.236.204.10] 16 104 ms * * 66.197.191.45 17 * 114 ms * 64.191.40.xx 18 138 ms * 199 ms 64.191.40.xx
Posted by Dacsoft, 12-01-2003, 09:33 PM
Am I the only 1 still having problems. Ping is still timing out or losing 24-50%
Posted by SWDevil, 12-01-2003, 09:39 PM
Nope Nocster/Burst still sucks and is still down.
Posted by jasonl813, 12-01-2003, 09:41 PM
Still extremely slow for me too. 33% packet loss too.
Posted by Innerplanet, 12-01-2003, 09:42 PM
No, I'm back to the same problems also. Here's what Burst had to say in the their forum: We believe that after days after days after days of works we have found the issue. At the present time we are attempting to locate a non-utterly braindead person with among the IP engineering group in one of our providers. Unfortunately we are not being overly successful. Since our choices are the badly magled packets that the customers see in a form of bizzare errors or congestion, we are choosing the congestion. We apologize for the inconvinience. Ahhh, ok......
Posted by michaelcap, 12-02-2003, 03:12 PM
completely down right now....
Posted by michaelcap, 12-02-2003, 03:13 PM
sorry, spoke to soon. back up after 1 minute of complete downtime
Posted by server4sale, 12-02-2003, 03:16 PM
doubted
Posted by jasonl813, 12-02-2003, 03:17 PM
And back down....
Posted by MGnet, 12-02-2003, 03:18 PM
down down down.....
Posted by michaelcap, 12-02-2003, 03:18 PM
scratch that. down again...
Posted by CybexHost, 12-02-2003, 03:19 PM
Argh, yet again...
Posted by jasonl813, 12-02-2003, 03:19 PM
It of course happens as I am migrating clients off their servers.
Posted by mrl14, 12-02-2003, 03:20 PM
THIS IS RIDICULOUS!! Nothing more can be said anymore.
Posted by dolbyac3, 12-02-2003, 03:20 PM
Any one call them yet? What they say? hmm back up atm.
Posted by jasonl813, 12-02-2003, 03:23 PM
Working again... for now...
Posted by michaelcap, 12-02-2003, 03:24 PM
just spoke with probably the friendliest Burst.net tech person. A very nice change from the people who normally answer the phones. She said that the present network issues are related to the Cogent problems they are currently facing. The network is not actually down, but flooded...
Posted by dolbyac3, 12-02-2003, 03:26 PM
Weird bursts forums are down though.
Posted by server4sale, 12-02-2003, 03:27 PM
its up now... Well why it always happen to be in PEAK timings???
Posted by CybexHost, 12-02-2003, 03:32 PM
Cogent always seems to be the trouble.... *sigh*
Posted by bhaputi, 12-02-2003, 04:02 PM
I am glad to hear you are getting good assistance from our staff. Flooding is not the issue, rather an apparent problem with the BGP session with Cogent. We are working to get it all smoothed out, and we apologize for the inconvenience.
Posted by bhaputi, 12-02-2003, 06:40 PM
Please see http://forums.burst.net/showthread.php?s=&threadid=1939 for the latest information