I have a reseller plan with them
MY customers compains about its stabilities again.
It is up and down...not very stable today..

anyone got the same?

Hope they can really resolve the problems soon

it is down now

Yes they've been having network problems for the past few days.

20-30% packet loss for nearly 2 days and they don't even answer support tickets anymore.

We have not been having network problems the past few days.
If you are having a problem, it may be specific to your server, but overall the network is running just fine.

Sean R.
BurstNET

are you sure ???:mad:
check the resale brick 2
it has been down for "SEVERAL TIMES" in the past two days.

What's your URL, howard? I haven't noticed anything today.

Burst, yes You do have network problems !
You just don't notice that.
At least sub-net 64.191.7xxx where my server is, is slow , very slow:

traceroute to vipsnet.com (64.191.7.107), 30 hops max, 40 byte packets
1 157.25.5.193 (157.25.5.193) 9.194 ms 9.857 ms 9.949 ms
2 217.153.3.149 (217.153.3.149) 9.738 ms 7.421 ms 2.240 ms
3 war-p2r1-g8-0-310 (195.94.192.129) 7.500 ms 1.032 ms 1.048 ms
4 sl-gw10-fra-8-3.sprintlink.net (217.147.97.61) 43.059 ms 43.169 ms 43.157 ms
5 sl-bb21-fra-8-0.sprintlink.net (217.147.96.41) 49.642 ms 43.952 ms 45.640 ms
6 sl-bb20-par-14-0.sprintlink.net (213.206.129.65) 107.764 ms 211.716 ms 232.430 ms
7 sl-bb21-par-15-0.sprintlink.net (217.118.224.34) 53.213 ms 53.237 ms 54.015 ms
8 sl-bb20-lon-13-0.sprintlink.net (213.206.129.69) 56.524 ms 56.555 ms 58.719 ms
9 sl-bb21-lon-15-0.sprintlink.net (213.206.128.38) 56.823 ms 56.703 ms 56.819 ms
10 sl-bb20-msq-10-0.sprintlink.net (144.232.19.69) 131.033 ms 130.942 ms 130.724 ms
11 sl-bb20-nyc-11-3.sprintlink.net (144.232.9.102) 132.315 ms 132.084 ms 132.160 ms
12 sl-bb26-nyc-6-0.sprintlink.net (144.232.13.9) 128.583 ms 128.969 ms 128.558 ms
13 sl-bb23-pen-12-0.sprintlink.net (144.232.20.95) 139.211 ms 136.183 ms 136.587 ms
14 sl-bb20-pen-14-0.sprintlink.net (144.232.16.25) 133.705 ms 132.694 ms 133.645 ms
15 sl-gw1-pen-9-0.sprintlink.net (144.232.5.2) 133.862 ms 134.879 ms 136.743 ms
16 sl-hostnoc-1-0.sprintlink.net (144.228.171.178) 154.300 ms 154.041 ms 153.988 ms
17 indiana.vipsnet.com (64.191.7.107) 157.705 ms * *



another:

1 gip-oakh-us-bar-1-fe0-0-0.gip.net (204.59.152.205) 3.192 ms 2.603 ms 2.695 ms
2 S2-0-0.WASAR1.Washington.opentransit.net (193.251.250.37) 3.679 ms 3.58 ms 3.817 ms
3 H3-0-0.PENAR3.Pennsauken.opentransit.net (193.251.250.249) 62.049 ms 54.608 ms 60.725 ms
4 Sr4-0.PENBB1.Pennsauken.opentransit.net (193.251.132.244) 66.915 ms 60.655 ms 68.874 ms
5 P5-1.NYKBB4.New-york.opentransit.net (193.251.154.121) 83.406 ms 70.273 ms 89.395 ms
6 P11-0.NYKCR1.New-york.opentransit.net (193.251.241.30) 70.536 ms 76.732 ms 75.646 ms
7 P5-0.NYKBB1.New-york.opentransit.net (193.251.241.21) 72.905 ms 90.548 ms 74.844 ms
8 ATT.GW.opentransit.net (193.251.242.154) 70.458 ms 81.064 ms 69.286 ms
9 tbr2-p013901.n54ny.ip.att.net (12.123.3.5) 78.586 ms 79.84 ms 106.643 ms
10 gbr6-p40.n54ny.ip.att.net (12.122.11.30) 81.058 ms 70.792 ms 83.379 ms
11 gar2-p370.n54ny.ip.att.net (12.123.1.205) 65.103 ms 55.856 ms 33.883 ms
12 12.124.179.6 (12.124.179.6) 36.255 ms 74.121 ms 65.564 ms
13 indiana.vipsnet.com (64.191.7.107) 77.045 ms * 3083.66 ms

another

traceroute to vipsnet.com (64.191.7.107): 1-30 hops, 38 byte packets
1 aggr2.fe6-6.ewr.datapipe.net (64.27.64.217) 0.328 ms 0.256 ms 0.254 ms
2 core1.ewr.datapipe.net (216.109.128.49) 0.329 ms (ttl=253!) 0.302 ms (ttl=253!) 0.311 ms (ttl=253!)
3 datapipe-gw.ip.att.net (12.119.140.73) 1.08 ms 0.680 ms 0.717 ms
4 tbr2-p012903.n54ny.ip.att.net (12.123.214.186) 2.73 ms (ttl=251!) 2.37 ms (ttl=251!) 2.63 ms (ttl=251!)
5 gbr6-p40.n54ny.ip.att.net (12.122.11.30) 1.56 ms 0.745 ms 0.984 ms
6 gar2-p370.n54ny.ip.att.net (12.123.1.205) 1.02 ms 0.957 ms 1.48 ms
7 12.124.179.6 (12.124.179.6) 8.54 ms 8.57 ms 8.68 ms
8 indiana.vipsnet.com (64.191.7.107) 572 ms (ttl=236!) 2146 ms (ttl=236!) 2792 ms (ttl=236!)

All 3 traceroutes come from traceroute.org

I have emailed nocster 2 days ago but nothing, tried to talk to someone on AIM yesterday but didn't get reply.

I tried to open and tracerouted getmehosted.com and it's loading fine and traceroutes are fine too, so it might be sub-net issue.

Burst, if you read it check that !

Regards

okay,
I talked to David Wood@Burst and it looks like he solved the problems ! Sub-net is fast again.

regards

Originally posted by BurstNET
We have not been having network problems the past few days.
If you are having a problem, it may be specific to your server, but overall the network is running just fine.

Sean R.
BurstNET

How can you come on these boards and continually claim that you guys are having no problems. Your company has not met your SLA up to this point. If you feel you have, please provide the numbers from last month's monitoring service.

can someone please download http://www.hostsitter.com/uumap.tar.Z and tell me the results, i don't get more than 14kb/s and this is a joke.

keith@nocster.com wrote at 2002-08-17 11:46:40 :

There is some problems with the backbone prov
ider. There is one hop outside our data
center that is loosing packets. We are
currently waiting for the problem to be corre
cted by Cogent.


Keith V
Support Dept


The response to a support ticket

We have not been having network problems the past few days. There is some problems with the backbone prov Hum?

<< Hum? >>
<< There is some problems with the backbone provider. >>

That is not "our" network.

We cannot control what happens upstream on the backbones...just on our own network, and our connections to the backbones...that is why we have multiple providers...

<< How can you come on these boards and continually claim that you guys are having no problems. >>

We do not claim we have not had any problems. I stated we have not had any problems in the last few days. Stop mis-construing my words.

The public should realize the cause for the vast majority of network issues the past several months. BurstNET was the target of massive DOS attacks, due to our US Government co-operation in the hosting of questionable websites. BurstNET was working with the Govt for a long time in regards to investigating these terrorist sites, and the public finally caught wind of it 2-3 months ago, due to a reporter that wouldn't accept our explanation. You can search Google to find proof/info on this. This caused our network to be attacked constantly until we removed the sites, after the Govt gave the okay several weeks ago. Our network has not had any major DOS attacks since that time. During the investigation we couldn't reveal this information, and we still cannot give any specific details, but at this time we can let this be known. Unfortunately our clients, and our reputation, had to suffer as a result of this investigation...but that is a minimal price to pay for fighting terrorism. Hopefully now that this has been made public, you can all understand why we have had so many network issues the past few months. Other than the DOS attacks our network has had a few issues, including hardware issues with a new router install, as well as some power issues...which are all being corrected and are part of the growth of a large data center. We hope now to get back to the high level of service, and even higher, that BurstNET provided during the first year of our data center opening. Thank you for your understanding.

<< http://www.hostsitter.com/uumap.tar.Z >>

I tested a download from my house on a cable modem and I get 115k/sec...on a connection that usually averages 45k/sec only....early morning so not much traffic on Adelphia...but that is still blazing fast from them...

<< are you sure ??? check the resale brick 2
it has been down for "SEVERAL TIMES" in the past two days. >>

I server being down IS NOT "network problems".
That specific server has had hardware issues, and was rebuilt.

<< Burst, yes You do have network problems !
You just don't notice that.
At least sub-net 64.191.7xxx where my server is, is slow , very slow: >>

a specific ip/server can have problems like this for reasons other than network problems. The most likely could be a dying network card...which is my first guess, due to the fact that the traceroutes you have posted are fine up to and including passing over our border router...it only has problems on the last hop...your server. The next logical thing would be a bad port on the switch tyou are on. Regardless, I am glad David W. was able to correct the issue for you.

Sean R.
BurstNET

Sean, you network STILL being the target of massive DOS attacks since you only remove azzam site 66.197.135.110/~azzam.
A lot of flooders has already knew that the owner of 66.197.135.110 (one.hostcreator.com) (which also have another server into your network 66.96.224.160 (umar.serveranda.com) is mohammad syukri and he received alot of money from al qaeda to propagate azzam site. What I believe that you will lost a lot of existing as well as potential clients if you don't turn off those box until further notice from US gov.

Sean.

I would suggest you speak with Matthew...you know the VP of Customer Service. I spoke with him this morning and appartently you two do not have the same information. You are misled and do not have the full facts.

Further, I would suggest that if there is no access to Burst services but everyother providers servers are up......since Sean shows no sense of responsibility for the choices of providers they choose, I can not recommend that anyone choose their services.

<< I spoke with him this morning and appartently you two do not have the same information. You are misled and do not have the full facts. >>

I have the full facts.
The problems is with Cogent's backbone, not our network.
We have pulled their line this morning, until they can solve their network issue.
At this point we are considering dropping their service completely...as it is causing to many problems.

Sean R.
BurstNET

I was getting under 200ms to BurstNET just on traceroute , AOLuk > Level3 > Sprintlink

Very good !

Originally posted by BurstNET

At this point we are considering dropping their [Cogent's] service completely...as it is causing to many problems.



Hey, if you keep us on Sprint you won't hear me complaining ;)

Sean,

Who made the decision to install the Cogent Line?

Who made the decision to use your datacenter? That one was mine...and apparently the wrong decision at that.

I find it somewhat amusing burst claims their not having problems when every day i come to wht i see a new post on how bad they are.

I for one am tired of seeing a new post a day, complaining about burst.

I told you from the beginning burst wouldnt be able to pull of their nocster product (see burst nocster announcement).

Guess i was right...

Sean: "We have not been having network problems the past few days."
Keith: "There is some problems with the backbone provider"

Sean: "That is not "our" network. We can't control that."


So you're saying... even though your connected to that network that's having problems, you are NOT having network problems??

lol burst hosts that taliban-news.com site doesn't it?

That is not "our" network. We cannot control what happens upstream on the backbones...just on our own network, and our connections to the backbones...that is why we have multiple providers... Sean, don't you have redundant providers? Sure, you can control what happens on the upstreams. You do run BGP?

I finally found out what Nocster is; they are the little green men that run around datacenters and cause network slowdowns & outages and cause power and hardware problem (ok, that was my feeble attempt at being funny :))

Originally posted by RackMy.com
Sean, don't you have redundant providers? Sure, you can control what happens on the upstreams. You do run BGP?

I finally found out what Nocster is; they are the little green men that run around datacenters and cause network slowdowns & outages and cause power and hardware problem (ok, that was my feeble attempt at being funny :))

im not too fond of burst
but you should really stop taking shots at them... just my opinion
seriously
you wouldnt like it if they were trying to take a shot at you every chance they got

[Deleted post. Rebooted server on a hunch, took care of my problem. If your Nocster server is still slow even though it's not piping through Cogent, try rebooting]

The onboard network cards that they use do not take a loss of connection very well. Basically this means that if a switch is rebooted or they unplug your connection...which they did Saturday night to all the servers...it will need a reboot. This is an added problem to the cogent problems the were having.