Possible Network or Virus hit Problems?

[Monsoonstorm]

Having a hard time connecting to my server today. Anyone else experiencing he same? Don't want to bore everyone with my Trace Route. My trace goes through Denver where I get time outs and 220ms pings. Found a great Site to check for those who don't know about this link yet: http://www.internettrafficreport.com/namerica.htm

[JohnScott]

I'm on 4 Mbps cable and every other site I go to is coming up fast, except the sites on my serverbeach server, and serverbeach itself - including this forum. Very slow. ServerBeach itself did not completely load after 60 seconds.

Is somebody on top of this?

[Tino Didriksen]

I quite agree...feels like someone ate the SB bandwidth.

I can also see my MRTG graph suddenly going from 42KB/s to 4KB/s around 3am server time...this is not a normal drop at that hour. It's still hanging down by the 3-5KB/s.


Obligatory traceroutes...
From me to my SB server:
1 <10 ms <10 ms <10 ms 192.168.1.1
2 10 ms 20 ms 20 ms odnxx5.ip.tele.dk [195.249.61.79]
3 10 ms 10 ms 20 ms ge0-0-6.1000M.odnxg1.ip.tele.dk [80.160.66.97]
4 20 ms 20 ms 20 ms so-0-2-1.kd4nxu1.ip.tele.dk [195.249.14.89]
5 90 ms 100 ms 140 ms pos3-1.622M.newyork2nxg1.ip.tele.dk [195.249.6.134]
6 90 ms 101 ms 100 ms bb1-p3-0.pxnyny.sbcglobal.net [151.164.89.49]
7 90 ms 101 ms 100 ms bb1-p4-0.nycmny.sbcglobal.net [151.164.189.61]
8 90 ms 100 ms 101 ms bb2-p14-0.nycmny.sbcglobal.net [151.164.243.206]
9 110 ms 110 ms 101 ms core2-p6-0.crnyny.sbcglobal.net [151.164.188.94]
10 110 ms 110 ms 101 ms core2-p3-0.crhnva.sbcglobal.net [151.164.188.198]
11 140 ms 111 ms 120 ms core2-p3-0.cratga.sbcglobal.net [151.164.241.94]
12 110 ms 121 ms 120 ms core1-p8-0.cratga.sbcglobal.net [151.164.241.85]
13 120 ms 131 ms 130 ms core2-p11-0.crhstx.sbcglobal.net [151.164.240.113]
14 120 ms 130 ms 150 ms bb2-p10-1.hstntx.sbcglobal.net [151.164.240.214]
15 120 ms 130 ms 130 ms bb1-p15-0.hstntx.sbcglobal.net [151.164.241.165]
16 130 ms 130 ms 130 ms bb2-p6-0.snantx.swbell.net [151.164.188.142]
17 130 ms 130 ms 130 ms ded2-fa1-1-0.snantx.swbell.net [151.164.17.245]
18 1642 ms 1633 ms 1622 ms vip-3027462.cust-rtr.swbell.net [151.164.19.174]
19 * * * Request timeout.
20 1693 ms 1672 ms * server1.projectjj.com [66.135.33.101]
21 1662 ms 1652 ms 1633 ms server1.projectjj.com [66.135.33.101]

From my SB server to me:
1 66.135.33.65 (66.135.33.65) 0.731 ms 0.641 ms 0.615 ms
2 10.10.10.4 (10.10.10.4) 0.511 ms 0.371 ms 0.292 ms
3 209.49.35.5 (209.49.35.5) 1.199 ms 0.984 ms 1.371 ms
4 sat10-core1-so-3-0-0.atlas.algx.net (165.117.59.5) 1.045 ms 1.102 ms 0.972 ms
5 aus10-core2-so-2-0-0-0.atlas.algx.net (165.117.200.13) 3.294 ms 3.192 ms 3.374 ms
6 aus10-core1-so-1-0-0-0.atlas.algx.net (165.117.192.5) 3.259 ms 3.307 ms 3.124 ms
7 dfw10-core2-so-7-0-0-0.atlas.algx.net (165.117.200.10) 9.234 ms 9.371 ms 9.033 ms
8 ord10-core1-so-7-0-0-0.atlas.algx.net (165.117.200.38) 32.306 ms 32.597 ms 32.365 ms
9 jfk11-core2-so-0-2-0-0.atlas.algx.net (165.117.200.33) 52.602 ms 52.693 ms 52.560 ms
10 jfk11-core1-so-0-1-0-0.atlas.algx.net (165.117.192.29) 52.723 ms 52.552 ms 52.675 ms
11 jfk11-core10-pos6-0.atlas.algx.net (165.117.192.94) 52.753 ms 52.729 ms 52.683 ms
12 pos2-0.155M.NewYork2nxg2.ip.tele.dk (195.215.109.17) 52.531 ms 52.535 ms 52.687 ms
13 ge4-0.1000M.newyork2nxg1.ip.tele.dk (80.63.80.33) 1518.936 ms 1536.812 ms *
14 so-0-2-3.622M.kd4nxu1.ip.tele.dk (195.249.6.133) 1606.932 ms * 1586.836 ms
15 * pos2-0.622M.odnxg1.ip.tele.dk (195.249.14.90) 1633.811 ms 1623.774 ms
16 fe0-0.100M.odnxx5.ip.tele.dk (80.63.83.198) 1608.769 ms 1608.234 ms 1613.387 ms
17 Me 1624.814 ms * 1624.812 ms

[icerat]

This has been going on for at least 4-5hours now ... anyone had any word from Server Beach about what's going on? I'm in Europe so not that keen on calling!

david

[JohnScott]

I have no replies from customer service. No replies from staff here on the forum either. I'm losing confidence.

[icerat]

My experiences so far with ServerBeach are that if problems occur during Texas weekday business hours, they are great. Outside of those times though, response has been deplorable. The VERY least they could do is post a message in the Network Status forum.

Most people in this industry understand that problems do occur, but to completely fail to communicate after an outage lasting now more than 7 hours is just showing contempt for their customers.

Anyone have recommendations for alternate providers?

[Monsoonstorm]

I don't think this has anything to do with SB. For me, I think it was a bottleneck in Denver where I had 200+ ms pings and time outs. This lasted only a few hours. Today, the same router in Denver is getting pings around 70ms and connections to my server is fast again. I was just curious if anyone else experienced any slow downs so I can determine if the problem was isolated to the route my ISP uses. I often get these "slow downs" (only through my ISP- my dialup broadband backup always has a fast route) but yesterday's was the most severe ever to where I couldn't connect at all to my server.

[JohnScott]

I don't think this has anything to do with SB.

Oh! I should have told my clients that instead of refunding hundreds of dollars!

Where is support? I've been waiting for hours for a reply, without any word.

It did just finally speed up. Kinda late, though.

[icerat]

The packet loss/latency is at 151.164.19.174 which is SB connection to swbell.net.

And it is still there :-(

[JohnScott]

Seems to be coming and going. It sped up there for a second.