Well, it happens again. My server at webreseller is getting very slow again:

04:26:00 (665.00 KB/s) - `uumap.tar.Z' saved [8520221]

Worse, download speed has been dropping to 50 KB/s (used to be 1.5 MB/s). I've submitted a trouble ticket about it.

If you have servers at webreseller, could you please test the speed now? I'm curious if I'm the only one who's unlucky? :(

Getting in excess of 2 MB/s - which is somewhat slower than normal, but not really what I would call slow...

Download speed (from NAC) is however slow: 'only' about 400 kb/s... Unusually slow for Webreseller...

I think there's a network packet loss problem in their network cause until now, I can only download a file from my server at 100-300 KB/s and the speed is unstable.

Yeap the speed on webreseller has slowed down almost by half.

This is the result for this morning

08:45:45 (2.09 MB/s) - `uumap.tar.Z.1' saved [8520221]

This is the result for yesterday morning

10:57:26 (4.21 MB/s) - `uumap.tar.Z.1' saved [8520221]

The speed is not bad I mean 2.0mb/sec is not bad most providers can't do even half of that. But there should be a reason as to why the speed has been reduced so drastically. Let me submit a ticket see what happends.

there seems to be a problem between yipes and their border router:
11 66.54.144.190 (66.54.144.190) 167.551 ms 126.635 ms 124.502 ms
12 66.7.139.82 (66.7.139.82) 138.146 ms 139.370 ms 139.715 ms
13 * webreseller.net (66.54.216.242) 145.432 ms 140.162 ms

Originally posted by WCSWEB
Yeap the speed on webreseller has slowed down almost by half.

This is the result for this morning

08:45:45 (2.09 MB/s) - `uumap.tar.Z.1' saved [8520221]

This is the result for yesterday morning

10:57:26 (4.21 MB/s) - `uumap.tar.Z.1' saved [8520221]

The speed is not bad I mean 2.0mb/sec is not bad most providers can't do even half of that. But there should be a reason as to why the speed has been reduced so drastically. Let me submit a ticket see what happends.

Please try to run the test several times. The result of downloading uumap.tar.Z should be random. Sometimes it can reach 2 MB/s, other times it's less than 1 MB/s.

Also the problem will be more visible if you try to download any file on your server from another location.

I am currently not showing any network latency and I am located in Chicago.

From doing speed tests I am at the same speed as I normally get.


10 30 ms 30 ms 40 ms 66.54.175.194
11 30 ms 30 ms 30 ms 66.54.144.109
12 30 ms 40 ms 30 ms 66.54.144.190
13 30 ms 40 ms 30 ms 66.7.139.82
14 30 ms 40 ms 30 ms webreseller.net [66.54.216.242]

My ISP acts funny during midday. I lose total acces to anything on webresellers network too, on a daily basis. I started a thread about it and it was a problem that wasnt with webreseller.net. That thread is here. (http://www.webhostingtalk.com/showthread.php?s=&threadid=65538) Just take my results with a grain of salt.


C:\>ping webreseller.net

Pinging webreseller.net [66.54.216.242] with 32 bytes of data:

Reply from 66.54.216.242: bytes=32 time=16ms TTL=239
Reply from 66.54.216.242: bytes=32 time<10ms TTL=239
Reply from 66.54.216.242: bytes=32 time=16ms TTL=239
Reply from 66.54.216.242: bytes=32 time<10ms TTL=239

Ping statistics for 66.54.216.242:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 16ms, Average = 8ms

C:\>tracert webreseller.net

Tracing route to webreseller.net [66.54.216.242]
over a maximum of 30 hops:

1 15 ms <10 ms 16 ms 10.9.128.1
2 <10 ms <10 ms 16 ms 167.206.32.33
3 15 ms 16 ms <10 ms r1-ge9-1.mhe.hcvlny.cv.net [167.206.32.1]
4 <10 ms 15 ms <10 ms r1-srp1-0.cr.hcvlny.cv.net [167.206.12.38]
5 <10 ms 16 ms <10 ms r2-srp5-0.in.hcvlny.cv.net [167.206.12.2]
6 <10 ms 16 ms <10 ms jfk3-core4-pos2-3.atlas.algx.net [198.180.44.101]
7 <10 ms <10 ms 16 ms jfk3-core3-pos6-0.atlas.algx.net [165.117.48.169]
8 <10 ms <10 ms 15 ms jfk3-level3.peer.algx.net [165.117.69.46]
9 <10 ms 15 ms <10 ms ae0-53.mp1.NewYork1.Level3.net [64.159.17.65]
10 <10 ms 16 ms 15 ms so-0-1-0.mp1.Philadelphia1.Level3.net [64.159.0.141]
11 <10 ms 16 ms 15 ms gige9-0.hsipaccess1.Philadelphia1.Level3.net [64.159.0.146]
12 <10 ms 15 ms 16 ms unknown.Level3.net [63.209.178.162]
13 31 ms 16 ms 16 ms 66.54.175.194
14 <10 ms 16 ms 15 ms 66.54.144.109
15 <10 ms 15 ms 16 ms 66.54.144.190
16 16 ms 15 ms 16 ms 66.7.139.82
17 <10 ms <10 ms 16 ms webreseller.net [66.54.216.242]

Trace complete.

C:\>

Well, it seems to be back to full speed now as I can download the file on my server at 1.2 MB/s.

I'm sure there was a network problem in their Yipes connection starting from this morning, around 4 am.

Did you contact our support department.
Im not showing a problem and have not all day today.

Please let me know if you still need help.

Yes, I've contacted support about it. I hope there's a good explanation about the slow problem though to make sure it wouldn't happen again. I swear it was pretty damn slow just to download a file from the server.

Originally posted by JBIZ718
I am currently not showing any network latency and I am located in Chicago.

That is because currently, the network is back up to speed. Your timing is impeccable, BTW, since it came back up not three minutes before you posted.

There has been a problem with the webreseller network since just after 4am EST. Ping times alone don't tell the story here, but packet loss does. In order for any tests to give accurate results, they have to be run from both directions.

Here are the results of a test I ran about a half-hour ago from each of my servers to the second hop upstream. Please note the packet loss numbers:

--- 66.54.144.190 ping statistics ---
100 packets transmitted, 65 packets received, 35% packet loss
round-trip min/avg/max/mdev = 15.335/18.276/21.443/1.399 ms
[root@ns /root]#

--- 66.54.144.190 ping statistics ---
100 packets transmitted, 62 packets received, 38% packet loss
round-trip min/avg/max/mdev = 16.064/18.578/20.749/1.142 ms
[root@ns root]#

Here is the route to 66.54.144.190 from my boxes:

[root@ns root]# traceroute 66.54.144.190
traceroute to 66.54.144.190 (66.54.144.190), 30 hops max, 38 byte packets
1 66.54.168.1 (66.54.168.1) 1.060 ms 0.794 ms 0.703 ms
2 66.54.144.190 (66.54.144.190) 1.093 ms 1.728 ms 1.075 ms

Currently (1:16pm EST), the problem seems to be resolved.

<edit>

Spoke too soon - 1:56pm EST, packet loss back up to the 15% range. <sigh>.

</edit>

-Bob

Thanks Bob, that's what I was trying to explain :D

Well, I have to admit that webreseller network (via Yipes) is very fast most of the time, but still seems unstable. There are times when it's very slow. I have no idea about the cause, maybe it's in Yipes, Level3, or maybe the network is overloaded. Maybe someone from webreseller could explain it further.

I'm running some important client sites in this server so if the speed is dropping, they will start yelling at me :D

Just to let you know

Any problems that some are having will be resolved shortly.

A update will come after that.

Thanks

Joe

Originally posted by JBIZ718
Just to let you know

Any problems that some are having will be resolved shortly.

A update will come after that.



At what point, Joe, can we expect notification/updates from webreseller when network issues arise? It's getting quite tiresome having to chase you guys down via WHT for answers every time something comes up.


-Bob

First no one contacted me about this, you can contact me via email and or icq, or aim.

We have a toll free # you can call and someone is there during the week 24/7. To be honest this really is the last place you should come, I happen to come here all the time so I see the posts, but this isnt our support forum, it just to be a place I come to and if I didnt you would have to contact us via the methods we have available.

So im not really sure how hard it is to track us down, but from talking to customers all the time they find rather easy to get ahold of us. Maybe WHT is not the best way to go about it. My recommendation is if there is a problem you can always send me a email to joew@webreseller.net

I will get it and respond asap. I do recommend going through the correct support channels though, but I happen to be online alot of the time.

Joe

does webreseller need somebody to tell them about any network problem? I thought the answer would be something like "Yes, we are aware of the problem and are currently working on it", instead of "next time, please contact us if you think there is a problem with our network".

Or perhaps Joe, since you are director of sales, you probably should not be answering questions directed for other deparments (technical support, or network engineer, in this case). Otherwise, it will create confusions like what I was thinking above.

Hope you solve the problem soon.

I, like seemingly the rest of us, am getting really fed up with these latency problems. Near midday my pings start reaching 250ms, when normally they used to be 40ms. I've contacted support 2 times saying they were on the problem, then I received this response:

Tracing route to mywebsite [theip]
over a maximum of 30 hops:

....
5 22 ms 20 ms 22 ms gbr1-p57.phlpa.ip.att.net [12.123.205.98]
6 75 ms 33 ms 25 ms gbr4-p20.n54ny.ip.att.net [12.122.2.17]
7 51 ms 19 ms 24 ms ggr1-p370.n54ny.ip.att.net [12.123.1.125]
8 159 ms 158 ms 154 ms pos6-1.core2.NewYork1.Level3.net [63.211.54.97]

9 165 ms 166 ms 169 ms ae0-53.mp1.NewYork1.Level3.net [64.159.17.65]
10 168 ms 168 ms 142 ms so-0-2-0.mp2.Philadelphia1.Level3.net [64.159.0
133]
11 145 ms 201 ms 141 ms gig4-1.hsa1.Philadelphia1.level3.net [64.159.3.
0]
12 153 ms 155 ms 214 ms unknown.Level3.net [63.209.178.162]
13 142 ms 143 ms 138 ms 66.54.175.194
14 146 ms 140 ms 164 ms 66.54.144.109
15 168 ms 214 ms 179 ms 66.54.144.190
16 156 ms 154 ms 159 ms 66.7.139.82

Trace complete.

I normally get 50, now its averaging 180.
--------------
Answer : Unfortunately it\'s a problem that keeps happening between AT&T and Level 3. We have absolutely no control over that. There are currently no problems with our network. Your best bet is to contact AT&T and find out what the problem is and why it keeps reoccuring. Unfortunately, there\'s nothing we can do on our end.
--------------



Webreseller is my provider and they should not be telling their customers it is someone elses fault and to call someone else about this. They cannot start telling people to blame others.. I understand this may not be their direct problem, but don't you think it is an obligation of a provider to get a problem like this resolved? I run a couple of game servers off my machine, and I've already lost money from clients complaining of the horrible pings (mind you this it not just from my provider.. Most of my clients are in PA and GA). I'm just about ready to cancel my service and move to a more reliable host.. to me this is unacceptable. I can't keep service with them when pings from various locations are 200+ half of the day.

In addition to FHDave's post, I think Webreseller should have some kind of page to let customers know of the network status and what they are doing to fix it. Unfortunately right now, that page would say "Level 3 problems, nothing we can do".

Originally posted by SynHost
Tracing route to mywebsite [theip]
over a maximum of 30 hops:

....
5 22 ms 20 ms 22 ms gbr1-p57.phlpa.ip.att.net [12.123.205.98]
6 75 ms 33 ms 25 ms gbr4-p20.n54ny.ip.att.net [12.122.2.17]
7 51 ms 19 ms 24 ms ggr1-p370.n54ny.ip.att.net [12.123.1.125]
8 159 ms 158 ms 154 ms pos6-1.core2.NewYork1.Level3.net [63.211.54.97]

9 165 ms 166 ms 169 ms ae0-53.mp1.NewYork1.Level3.net [64.159.17.65]
10 168 ms 168 ms 142 ms so-0-2-0.mp2.Philadelphia1.Level3.net [64.159.0
133]
11 145 ms 201 ms 141 ms gig4-1.hsa1.Philadelphia1.level3.net [64.159.3.
0]
12 153 ms 155 ms 214 ms unknown.Level3.net [63.209.178.162]
13 142 ms 143 ms 138 ms 66.54.175.194
14 146 ms 140 ms 164 ms 66.54.144.109
15 168 ms 214 ms 179 ms 66.54.144.190
16 156 ms 154 ms 159 ms 66.7.139.82

Trace complete.

I normally get 50, now its averaging 180.
--------------
Answer : Unfortunately it\'s a problem that keeps happening between AT&T and Level 3. We have absolutely no control over that. There are currently no problems with our network. Your best bet is to contact AT&T and find out what the problem is and why it keeps reoccuring. Unfortunately, there\'s nothing we can do on our end.
--------------

Webreseller is my provider and they should not be telling their customers it is someone elses fault and to call someone else about this. They cannot start telling people to blame others.. I understand this may not be their direct problem, but don't you think it is an obligation of a provider to get a problem like this resolved?

Sure they should do everything to get this problem resolved, but looking at your traceroute, this time it really doesn't seem to be their problem, nor yipes, it's a problem between att & level3's peering. So all they can do is to phone up yipes, tell them there's a problem so yipes can/will hand the information over to Level3.
What you could do, is phone/mail ATT telling them the same, and asking them to resolve this!

best regards,

Originally posted by JBIZ718
So im not really sure how hard it is to track us down, but from talking to customers all the time they find rather easy to get ahold of us. Maybe WHT is not the best way to go about it. My recommendation is if there is a problem you can always send me a email to joew@webreseller.net

I have been sitting here editing this reply for about a half hour now, so as to not get myself permanently banned from WHT. It has not been easy.

Let's be honest here, Joe - your personal record for responding to email and/or PM stinks. Email to sales@webreseller.net, cs@webreseller.net, and rob@webreseller.net go unanswered. I call, I get the webreseller voice mail, leave my phone number and email address, and never hear back from anyone. So please, let's cut the baloney.

In the interest of fairness, your tech support people (Jon, the other Joe, and Paul) have always been fast to respond at all hours of the day/night, and have proven themselves competent as well as courteous. Same goes for "Leslie".

That said, would it kill you guys to send out notifications to your clients when your network goes tits-up, or at least put up a status page somewhere? The last time this happened, I expressed my dissatisfaction to Rob over the fact that no notification or updates were given as to network status. His response was that he was "concerned that I hadn't been receiving the updates that were being sent out". To date, I have yet to hear from any other webreseller customers that have ever received anything other than forwarded Yipes maintenence notices.

What I find most interesting, however, is your rather drastic change of tune from our email exchange of the other day, where I basically expressed these same concerns and you agreed with me.

-Bob

Ok, I hope that you are all ready for a nice reply. My experience with Webreseller has been great. I notified them via their helpdesk that there was a network problem this morning at 1am PST as I was getting packet loss like the rest of you. They responded in a timely manner. Now for the juicy part.

It seems that our server contributed in some way to the network problem. (we were not ddosed, nor comprimised so don't worry)We had a client upload a file at around 2:15am PST (video game download file) last night that was being downloaded like crazy. Rob who is the CEO of Webreseller called us in the morning, as we called the noc at around 9:00 am or so to check on the network problems and to reboot our server which was taken offline. We worked out an arrangement with them that our server would be put back online for obvious reasons, and that we would hunt down the culprit. We found the culprit in about 5 minutes. Our MRTG stats at around 10:00 am PST showed something close to 150 gb. Needless to say that client has been terminated for obvious reasons a long time ago, and we for the last 4-5 hours or so have been experiencing speeds as they were before. I apologize to everyone for any inconvenience that this may have caused, as we monitor our sites very carefully and keep a vigilant eye on our servers at all times.

-Steven

Originally posted by TMX



That said, would it kill you guys to send out notifications to your clients when your network goes tits-up, or at least put up a status page somewhere?


Hello,
We are working on getting a better means of notification of network trouble. The problem that we had today, was that only a smaller segment of our network was being affected by this massive download issue. My concern with sending out a mass email as notification, was that it would alert customers that were not experiencing any problems. In the past this has caused even more problems than issues like this (overloaded network segment). We get inundated with emails and support tickets asking "Is my server being effected?" and other similar type emails. I will have something in place within the next 30 days that will give a network overview or at the very least notification of trouble. Once that is in place, we will continue to expand upon that.

I apologize for the lack of communication in this matter.

-Paul Rice
CTO - WebReseller.Net
paulrice@webreseller.net

A status page for members only would be the perfect thing. If one of the members feels there is a problem, that person would just have to visit the network status page and that's it. The problem is not that the network is having dificulties, the problem is the anxiety that builds up with clients asking questions when you have a server losing packets. Trying to call or e-mail your provider with no response is very frustrating.

I think webreseller.net should have a members only forum where people can report this stuff. Something similar to what rackshack has with their forums. We could have fellow users report problems and then WR research them if they are meaningful.

I had a couple of customers complain to me when I woke up this morning about it. My first intention was to check these forums and viola, I saw this thread near the top :D

jt

Originally posted by insiderhosting
Our MRTG stats at around 10:00 am PST showed something close to 150 gb.

Over how long? 5 minutes interval? or what? What's the total bandwith used by this download?

I'll add that I've yet to have problems with webresellers network.

I consistently get 90ms or less.

Web Host Weather Report

http://east.hwr.us

Number 2 On The East Coast

Very impressive. You even beat up pair in ping speed. Keep up the great speed!