| Posted by kaleshnikov, 01-14-2004, 08:41 PM | |
I'm getting some packet loss when pinging to my server as well as the FTP dropping out sometimes. I did a ping test on their website IP as well and it seems to be the same problem. Any word from MGS?
Here is ping result when pinging managed.com:
Ping statistics for 66.79.160.10:
Packets: Sent = 70, Received = 42, Lost = 28 (40% loss),
Approximate round trip times in milli-seconds:
Minimum = 105ms, Maximum = 352ms, Average = 127ms
|
| Posted by Cloudster, 01-14-2004, 09:33 PM | |
Perhaps you should email them support@managed.com
|
| Posted by kaleshnikov, 01-14-2004, 09:55 PM | |
I already did but I doubt they'll look at it. Their support only seems to be online from like 9AM-5PM.
|
| Posted by Incognito, 01-14-2004, 09:56 PM | |
Then what do you expect us to do?
|
| Posted by kaleshnikov, 01-14-2004, 10:13 PM | |
Did I ask anyone of you to do anything?
I was simply letting people know, hopefully get a reply from MGS and maybe some confirmation from other Managed.com customers. Please read
|
| Posted by Incognito, 01-14-2004, 10:24 PM | |
One more person trying to get support here from managed.com instead of directly from them. It isn't an outage-it's just the same lousy connectivity everyone appears to be getting coupled with the lack of true 24/7/365 support. What you are describing seems to be the norm, not an unusual situation. Also, if you go to the main forums, you will see dozens of customers saying the same thing.
Sorry, but this just isn't the place anyone can help you. If you can't get help when you need it from managed.com, maybe you need to relook at things.
|
| Posted by NE-Andy, 01-14-2004, 10:31 PM | |
It seems to me that only clusters of their servers are having problem. If you browse through hosts with prices suspiciously low and IP range within Managed.com network; you'll notice that some are running just fine while others are dead like sh*t.
Someone accidentally deleted my reseller account and I was in the progress of reloading the whole thing and then it just went poof on me... yet again. *Sigh* such a long day for a small MMORPG fansite....
|
| Posted by Mrdredd, 01-14-2004, 10:34 PM | |
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 66.79.178.180: bytes=32 time=90ms TTL=46
Request timed out.
Request timed out.
Request timed out.
Reply from 66.79.178.180: bytes=32 time=90ms TTL=46
Request timed out.
Reply from 66.79.178.180: bytes=32 time=91ms TTL=46
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
|
| Posted by IGobyTerry, 01-14-2004, 10:43 PM | |
Pinging managed.com [66.79.160.10] with 32 bytes of data:
Reply from 66.79.160.10: bytes=32 time=85ms TTL=52
Reply from 66.79.160.10: bytes=32 time=83ms TTL=52
Reply from 66.79.160.10: bytes=32 time=84ms TTL=52
Reply from 66.79.160.10: bytes=32 time=82ms TTL=52
Reply from 66.79.160.10: bytes=32 time=85ms TTL=52
Reply from 66.79.160.10: bytes=32 time=86ms TTL=52
Reply from 66.79.160.10: bytes=32 time=84ms TTL=52
Reply from 66.79.160.10: bytes=32 time=93ms TTL=52
Reply from 66.79.160.10: bytes=32 time=84ms TTL=52
Reply from 66.79.160.10: bytes=32 time=85ms TTL=52
Reply from 66.79.160.10: bytes=32 time=85ms TTL=52
Reply from 66.79.160.10: bytes=32 time=86ms TTL=52
Reply from 66.79.160.10: bytes=32 time=85ms TTL=52
Reply from 66.79.160.10: bytes=32 time=84ms TTL=52
Reply from 66.79.160.10: bytes=32 time=86ms TTL=52
Reply from 66.79.160.10: bytes=32 time=83ms TTL=52
Reply from 66.79.160.10: bytes=32 time=83ms TTL=52
Reply from 66.79.160.10: bytes=32 time=84ms TTL=52
Reply from 66.79.160.10: bytes=32 time=85ms TTL=52
Reply from 66.79.160.10: bytes=32 time=84ms TTL=52
Ping statistics for 66.79.160.10:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 82ms, Maximum = 93ms, Average = 84ms
|
| Posted by kaleshnikov, 01-14-2004, 10:45 PM | |
Incognito, I DID NOT ASK FOR SUPPORT.
|
| Posted by demonmoo, 01-14-2004, 10:46 PM | |
Do people want to post some traceroutes?
I seem to be takieng a completely different path the normal (layer42???)
1 10.0.0.4 (10.0.0.4) 0.355 ms 0.317 ms 0.286 ms
2 207.164.179.1 (207.164.179.1) 12.885 ms 8.383 ms 6.738 ms
3 if-3-0-T10.core.o.trytel.com (207.164.228.57) 7.169 ms 6.759 ms 6.731 ms
4 h209-71-218-109.gtconnect.net (209.71.218.109) 7.398 ms 7.470 ms 7.314 ms
5 h216-18-112-142.gtconnect.net (216.18.112.142) 7.641 ms 7.376 ms 7.644 ms
6 h216-18-72-137.gtcust.grouptelecom.net (216.18.72.137) 63.570 ms 33.786 ms 33.476 ms
7 POS6-0.WANB-TOROON.IP.GROUPTELECOM.NET (216.18.63.197) 46.039 ms 31.785 ms 31.745 ms
8 POS4-0.PEERA-CHCGIL.IP.GROUPTELECOM.NET (66.59.191.86) 50.245 ms 30.755 ms 31.247 ms
9 ge3-0.cr01.chc01.pccwbtn.net (206.223.119.48) 39.905 ms 31.068 ms 30.670 ms
10 pos3-0.cr02.sjo01.pccwbtn.net (63.218.6.66) 94.874 ms 95.604 ms 95.219 ms
11 63.218.7.6 (63.218.7.6) 196.493 ms 99.590 ms 97.976 ms
12 f3-0.core1.eqx.layer42.net (69.36.239.42) 98.570 ms 99.239 ms 98.082 ms
13 f2-0-1.core1.sjc.layer42.net (69.36.239.61) 87.574 ms 99.276 ms 99.642 ms
14 69.36.242.68 (69.36.242.68) 99.525 ms 100.074 ms 99.385 ms
|
| Posted by bimmer, 01-14-2004, 10:48 PM | |
Incognito.
Don't be a dork, we're just reporting outages just as the forum topic says "Network Outages and Updates"
If you don't want to hear this stuff, maybe you should surf elsewhere.
|
| Posted by kaleshnikov, 01-14-2004, 10:49 PM | |
Tracing route to managed.com [66.79.160.10]
over a maximum of 30 hops:
1 72 ms * 48 ms mcr4.mtun.phub.net.cable.rogers.com [24.101.128.
1]
2 54 ms 43 ms 33 ms 66.185.92.129
3 * * * Request timed out.
4 * 29 ms 52 ms gw01.ajax.phub.net.cable.rogers.com [66.185.81.1
70]
5 17 ms 21 ms 20 ms gw02.bloor.phub.net.cable.rogers.com [66.185.80.
134]
6 39 ms 38 ms 42 ms gw02.chi.phub.net.cable.rogers.com [66.185.81.1]
7 117 ms 41 ms 35 ms ge3-1.cr01.chc01.pccwbtn.net [63.218.5.5]
8 101 ms 112 ms 114 ms pos3-0.cr02.sjo01.pccwbtn.net [63.218.6.66]
9 90 ms 95 ms 110 ms 63.218.7.6
10 90 ms 106 ms 123 ms f3-0.core1.eqx.layer42.net [69.36.239.42]
11 108 ms 101 ms 115 ms f2-0-1.core1.sjc.layer42.net [69.36.239.61]
12 135 ms * 147 ms 69.36.242.68
13 * 187 ms 116 ms www.managed.com [66.79.160.10]
Trace complete.
|
| Posted by ExtremeIS, 01-14-2004, 10:51 PM | |
Looks to me like you are using WHT to get a hold of the representative from Managed.com who frequents these forums. In my opinion that's looking for support.
Just my 2 cents.
|
| Posted by kaleshnikov, 01-14-2004, 10:53 PM | |
That was not my intention.
My intention was to simply outline this and get some confirmation from other Managed.com customers. If MGS does reply, good.
Their phones are down and their helpdesk is down, no way to contact them
|
| Posted by bimmer, 01-14-2004, 10:58 PM | |
Back up =) That was weird. All is well now.
How about you Andrej? Are you oK?
|
| Posted by kaleshnikov, 01-14-2004, 11:01 PM | |
Still getting some packet loss. I think they might be getting DDoS'ed again.
Ping statistics for 66.79.184.210:
Packets: Sent = 86, Received = 72, Lost = 14 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 99ms, Maximum = 167ms, Average = 119ms
|
| Posted by bimmer, 01-14-2004, 11:03 PM | |
DDos you think?
There are alot of managed.com haters out there. Punks.
|
| Posted by kaleshnikov, 01-14-2004, 11:08 PM | |
Possibly DDoS. I don't see any other problem that'd cause packet loss at such unsteady variables.
|
| Posted by Mark_YH, 01-14-2004, 11:12 PM | |
Pinging managed.com [66.79.160.10] with 32 bytes of data:
Reply from 66.79.160.10: bytes=32 time=113ms TTL=48
Reply from 66.79.160.10: bytes=32 time=116ms TTL=48
Reply from 66.79.160.10: bytes=32 time=111ms TTL=48
Reply from 66.79.160.10: bytes=32 time=113ms TTL=48
That's still some pretty high pings...
|
| Posted by demonmoo, 01-14-2004, 11:13 PM | |
They could be propegating a new route.
All my connections in seem to go over layer42.net
That would explain why some places have an ok (no problem) connection and others are having problems.
|
| Posted by kaleshnikov, 01-14-2004, 11:21 PM | |
Ping statistics for 66.79.160.10:
Packets: Sent = 42, Received = 42, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 95ms, Maximum = 152ms, Average = 110ms
Seems all good now. Maybe they were propegating a new route.
As for the high pings, depends where you live. I live in Toronto, Canada; therefore California is quite the distance.
|
| Posted by carlos_pires, 01-15-2004, 02:22 PM | |
Is it just me, or it only takes 50 minutes of downtime or even some minutes of high pings or packetloss to most people start posting 'WTFing' msgs in here?
As anyone ever had hosting with no downtime, or that never was under any attack, or never had a network/router/DC problem? Maybe there's some kind of virus which attacks only webhostingpeople and causes a slightly psychotic behaviour...
Regards
|
| Posted by kaleshnikov, 01-15-2004, 05:40 PM | |
That was the most retarded post ever.
I've not once said WTF in this thread. Do not post unless it adds to the ORIGINAL discussion.
|
| Posted by demonmoo, 01-15-2004, 05:44 PM | |
Indeed . This forum is for posting of downtime notices . Quite handy . For example lets say a server I have with DC Y is down , I check this place to see if its my server (then I try and contact support) if its the providers entire network I'll leave it be since I wont be able to do anything to influence when my server comes back online .
|
| Posted by jason012, 01-15-2004, 07:27 PM | |
you know, I have a server with them and its never down. are you guys sure it isnt like... your isp or something?
|
|
 Add to Favourites
 Print this Article
|
