Managed.com Issues <Recent Managed Threads Merged> - Knowledgebase

Portal Home > Knowledgebase > Articles Database > Managed.com Issues

Managed.com Issues

Posted by mil22, 06-28-2004, 06:28 AM
I've noticed the ping to managed.com go up to 500ms from the usual 20-30ms (from CA) with about 10% packet loss, over the last few days. It seems to happen intermittently and last about 10 minutes each time. A traceroute confirms the problem is between the last two xo.net routers before you hit managed. Anyone else noticed this or know why it's happening?
Posted by porcupine, 06-28-2004, 06:33 AM
Why not just paste the traceroute?
Posted by mil22, 06-28-2004, 06:35 AM
OK - when it next happens, I will!
Posted by Cope, 06-28-2004, 06:42 AM
Yeah next time it happens post here so others on different connections can test it for you. Also might be a good idea to make Managed.com aware of it, via their support methods.
Posted by mil22, 06-30-2004, 12:59 AM
Last edited by mil22; 06-30-2004 at 01:10 AM.
Posted by ranjitbhar, 06-30-2004, 03:44 AM
I also have experienced some lags on my server a few times in the recent days, Interesting when I do a tracert and when I am going via abovnet I dont have these issues, but when I get routed via xo I do sometimes get that lag, It must be my local ISP I guess!
Posted by CoolinHL, 06-30-2004, 04:21 AM
If there are issues, I think they're isolated to XO. Here's a traceroute that goes through bungi.net (what network is that?) 3 80 ms 50 ms 20 ms rc1bb-pos13-0.vc.shawcable.net [66.163.76.161] 4 80 ms 30 ms 30 ms rc2wt-pos2-2.wa.shawcable.net [66.163.76.58] 5 50 ms 150 ms 40 ms rc1sj-pos1-0.cl.shawcable.net [66.163.76.46] 6 50 ms 70 ms 90 ms rc2sj-pos0-0.cl.shawcable.net [66.163.67.10] 7 60 ms 51 ms 40 ms paix.bungi.net [198.32.176.7] 8 50 ms 70 ms 50 ms 172.17.31.7 9 51 ms 50 ms 80 ms 66.79.175.17 10 50 ms 50 ms 100 ms 66.79.175.6 11 60 ms 50 ms 60 ms www.managed.com [66.79.160.10]
Posted by Townconx, 06-30-2004, 09:00 AM
i have that problem too. managed.com often have over 500ms from usual 17~25ms of ping. now it's happening again at over 500ms ping, with about 50~75% packet loss. when will they have a stable connection? also, can anyone transfer more than 10mbps? my server can never go beyond 8~9mbps barrier.
Posted by mainarea, 06-30-2004, 11:52 AM
Tracing out of Managed.com: 1 205.209.133.1 (205.209.133.1) 0.330 ms 0.205 ms 0.203 ms 2 66.79.175.19 (66.79.175.19) 0.169 ms 0.137 ms 0.135 ms 3 172.17.1.85 (172.17.1.85) 0.229 ms 0.254 ms 0.242 ms 4 POS4-2.GW3.SJC1.ALTER.NET (157.130.59.53) 1051.579 ms 1077.936 ms 1072.972 ms 5 142.ATM3-0.XR1.SJC1.ALTER.NET (152.63.49.30) 1065.880 ms 1093.706 ms 1136.500 ms 6 0.so-0-0-0.XL1.SJC1.ALTER.NET (152.63.55.114) 1125.415 ms 1146.857 ms 1124.927 ms 7 0.so-3-0-0.TL1.SAC1.ALTER.NET (152.63.53.250) 1127.254 ms 1166.690 ms 1152.577 ms 8 0.so-1-1-0.TL1.DFW9.ALTER.NET (152.63.9.229) 1189.597 ms 1143.737 ms 1168.084 ms 9 0.so-7-0-0.CL1.DFW13.ALTER.NET (152.63.103.218) 1158.056 ms 1155.776 ms 1168.575 ms 10 POS6-0.GW1.DFW13.ALTER.NET (152.63.103.85) 1162.123 ms 1162.594 ms 1185.373 ms 11 theplanet-gw.customer.alter.net (157.130.143.226) 1198.850 ms 1164.121 ms 1131.319 ms 12 car1-2-v1.dllstx2.theplanet.com (12.96.160.12) 1123.681 ms 1149.671 ms 1136.472 ms 13 20.67-18-144.reverse.theplanet.com (67.18.144.20) 1143.660 ms 1105.443 ms 1110.078 ms 14 dallas (67.18.145.58) 1117.173 ms 1126.959 ms 1135.589 ms Tracing into Managed.com: traceroute to 205.209.133.* , 30 hops max, 38 byte packets 1 57.67-18-145.reverse.theplanet.com (67.18.145.57) 0.862 ms 0.597 ms 0.567 ms 2 18.67-18-144.reverse.theplanet.com (67.18.144.18) 0.725 ms 0.579 ms 0.777 ms 3 ibr1-ge-1-0-0-v2.dllstx3.theplanet.com (12.96.160.33) 0.635 ms 0.819 ms 0.926 ms 4 366.ge-6-3-1.cr1.dfw2.us.above.net (216.200.88.138) 1.305 ms 0.755 ms 0.748 ms 5 so-3-1-0.mpr4.sjc2.us.above.net (64.125.29.49) 45.362 ms 45.539 ms 46.115 ms 6 so-0-0-0.er10a.sjc2.us.above.net (64.125.30.94) 45.150 ms 45.344 ms 45.582 ms 7 reserved.above.net (209.133.64.124) 349.598 ms 350.370 ms 348.844 ms 8 66.154.102.5 (66.154.102.5) 1168.700 ms 349.450 ms 1126.603 ms 9 205.209.133.* (205.209.133.*) 351.179 ms 349.937 ms 351.814 ms Trace from NJ: 1 1 ms 1 ms 1 ms 192.168.0.1 2 11 ms 9 ms 9 ms 10.113.72.1 3 11 ms 10 ms 10 ms fe-2-8-rr01.ebrunswick.nj.nj02.comcast.net [68.8 7.48.61] 4 10 ms 13 ms 11 ms srp-8-1-ar01.plainfield.nj.nj02.comcast.net [68. 87.48.193] 5 12 ms 13 ms 12 ms pos-7-1-cr01.plainfield.nj.core.comcast.net [68. 87.19.249] 6 12 ms 11 ms 10 ms 12.118.102.17 7 12 ms 12 ms 11 ms tbr1-p010101.n54ny.ip.att.net [12.123.3.82] 8 11 ms 11 ms 15 ms ggr1-p360.n54ny.ip.att.net [12.123.1.121] 9 14 ms 16 ms 18 ms 206.111.13.5 10 12 ms 12 ms 11 ms p5-0-0.RAR2.NYC-NY.us.xo.net [65.106.3.41] 11 18 ms 20 ms 19 ms p6-0-0.RAR1.Washington-DC.us.xo.net [65.106.0.2] 12 86 ms 85 ms 83 ms 65.106.0.38 13 84 ms 86 ms 84 ms p0-0-0.MAR1.Fremont-CA.us.xo.net [65.106.5.134] 14 84 ms 83 ms 84 ms p0-0.CHR1.Fremont-CA.us.xo.net [207.88.80.178] 15 1244 ms 389 ms * 67.104.60.222.ptr.us.xo.net [67.104.60.222] 16 402 ms 362 ms 357 ms 205.209.133.* From PA: Hostname %Loss Rcv Snt Last Best Avg Worst 1. ge-6-0-core.scr1.hostnoc.net 0% 4 4 0 0 0 0 2. 66.197.191.46 0% 4 4 4 4 4 4 3. ge-8-1-129.hsa1.Philadelphia1.Level 0% 4 4 5 5 5 5 4. ge-6-0-0.mp2.Philadelphia1.Level3.n 0% 4 4 5 5 5 5 5. so-6-1-0.bbr2.NewYork1.Level3.net 0% 4 4 7 7 7 7 6. ge-7-0-0.edge1.NewYork1.Level3.net 0% 4 4 7 7 7 7 7. xo-level3-oc12.NewYork1.Level3.net 0% 4 4 7 7 7 7 8. p5-0-0.RAR2.NYC-NY.us.xo.net 0% 4 4 7 7 7 7 9. p6-0-0.RAR1.Washington-DC.us.xo.net 0% 4 4 11 11 11 12 10. 65.106.0.38 0% 4 4 92 92 92 92 11. p0-0-0.MAR1.Fremont-CA.us.xo.net 0% 4 4 95 94 95 95 12. p0-0.CHR1.Fremont-CA.us.xo.net 0% 4 4 92 92 92 92 13. 67.104.60.222.ptr.us.xo.net 34% 2 4 389 339 364 389 14. 205.209.133.* 67% 1 3 1220 1220 1220 1220
Posted by mainarea, 06-30-2004, 11:54 AM
Traceroute from Managed.com to NectarTech (.1 miles away): 1 205.209.133.1 (205.209.133.1) 0.280 ms 0.213 ms 0.211 ms 2 66.79.175.18 (66.79.175.18) 0.173 ms 0.240 ms 0.238 ms 3 POS4-2.GW3.SJC1.ALTER.NET (157.130.59.53) 300.090 ms 303.005 ms 299.282 ms 4 peer-gw.customer.alter.net (208.214.143.70) 367.101 ms 443.301 ms 446.248 ms 5 sjc-core-01.eng.nectartech.com (65.39.248.98) 451.900 ms 432.125 ms 453.119 ms 6 69.50.242.98.ip.nectartech.com (69.50.242.98) 447.896 ms * 435.795 ms That should be 4ms, not 400+ms. - Matt
Posted by DVD, 06-30-2004, 12:06 PM
I have a server with Angelnetworkz (located in managed.com) , but suddently the access speed is so slow. My ping went as high as 1300 ms (from Asia) but it used to be in the range of 200 - 220 ms. Anyone have this problem as well ? or only me ?
Posted by DeltaAnime, 06-30-2004, 12:20 PM
make sure you aren't rooted at all? A lot of asia based servers/people get taken over, due to the amount of bandwith they get for almost pennies. As for my box at managed, she's been doing great 30ms from where i am (around 1000 KM away) ~Francisco
Posted by xgravity, 06-30-2004, 12:26 PM
my test box over there is getting pings around 1100ms to 1250ms right now. i emailed them, but no reply yet as to what is going on.
Posted by ambirex, 06-30-2004, 12:28 PM
Looking at my outgoing ping graphs from one of my boxes at managed, pings have jumped between 254ms - 1130ms. Double checked and the box isn't rooted. Yeah looks like something is up. edit: pinging google from the box has aprox 45% packet loss. Last edited by ambirex; 06-30-2004 at 12:42 PM.
Posted by DeltaAnime, 06-30-2004, 12:41 PM
my pings report that it's 400 right now, but my ssh still feel's like localhost o_O I did a trace, it got weird and bungi ~Francisco
Posted by ChaosHosting, 06-30-2004, 12:45 PM
I trace it over xo.net to managed and start spiking to 400. -Greg
Posted by ambirex, 06-30-2004, 12:48 PM
edit ^^^ well that blows my theory. Ok, its getting better. google pings are ~350ms (was 650ms)... funny thing is that pings to netcraft (I believe in the UK) were steady. Looking at the traceroute the UK connection went through XO and the google is going through alter.net. maybe it is an alternet problem, because as soon as I get to the first alter.net gw I start having problems.
Posted by ambirex, 06-30-2004, 12:53 PM
anyone who cares, here is my outgoing ping to google graph. Attached Images graph_image.png (3.3 KB, 80 views)
Posted by ChaosHosting, 06-30-2004, 01:03 PM
FYI: View http://www.webhostingtalk.com/showth...hreadid=291185 I traced to managed through xo and started spiking to 400+ and had quite a few packets lost -Greg
Posted by sirius, 06-30-2004, 01:08 PM
I'm seeing slightly higher pings coming from Tampa than normal, but I am also going through XO... ===== Begin ===== 4 gbr1-p24.ormfl.ip.att.net (12.123.200.170) 18.071 ms 18.437 ms 21.465 ms 5 gbr4-p70.ormfl.ip.att.net (12.122.5.125) 25.321 ms 13.134 ms 13.349 ms 6 tbr1-p012302.attga.ip.att.net (12.122.2.181) 22.962 ms 22.675 ms 24.461 ms 7 tbr2-cl1.wswdc.ip.att.net (12.122.10.69) 38.787 ms 45.066 ms 36.062 ms 8 ggr1-p370.abnva.ip.att.net (12.123.217.5) 37.324 ms 38.420 ms 35.329 ms 9 p2-0.IR1.Ashburn-VA.us.xo.net (206.111.0.61) 36.452 ms 35.344 ms 41.820 ms 10 p5-0-0.RAR1.Washington-DC.us.xo.net (65.106.3.133) 38.463 ms 38.341 ms 41.452 ms 11 p1-0-0.RAR1.SanJose-CA.us.xo.net (65.106.0.38) 108.677 ms 105.239 ms 107.897 ms 12 p0-0-0.MAR1.Fremont-CA.us.xo.net (65.106.5.134) 119.423 ms 110.859 ms 106.862 ms 13 p0-0.CHR1.Fremont-CA.us.xo.net (207.88.80.178) 102.503 ms 106.533 ms 110.445 ms 14 67.104.60.222.ptr.us.xo.net (67.104.60.222) 111.729 ms 109.794 ms 107.683 ms 15 66.79.175.6 (66.79.175.6) 122.423 ms 110.911 ms 106.731 ms 16 www.managed.com (66.79.160.10) 108.669 ms 109.934 ms 108.791 ms ===== End ===== From The Planet ===== Begin ===== 2 gig3-8.sm-asr1-2.theplanet.com (69.41.250.77) 0.967 ms 0.916 ms 0.488 ms 3 ibr1-ge-0-1-0-v1.dllstx3.theplanet.com (12.96.160.1) 2.469 ms 2.275 ms 2.536 ms 4 ge12-0.mpr1.dfw2.us.above.net (216.200.6.233) 2.310 ms 1.368 ms 1.625 ms 5 so-3-0-0.cr1.dfw2.us.above.net (64.125.29.213) 1.664 ms 3.133 ms 3.479 ms 6 so-4-1-0.mpr4.sjc2.us.above.net (64.125.29.57) 47.644 ms 46.443 ms 47.810 ms 7 so-0-0-0.er10a.sjc2.us.above.net (64.125.30.94) 45.769 ms 45.445 ms 46.558 ms 8 reserved.above.net (209.133.64.124) 48.656 ms 48.601 ms 49.835 ms ===== End ===== From ServInt ===== Begin ===== 2 ash1-br1-at-1-2-0.gnaps.net (199.232.56.25) 1.117 ms 1.421 ms 4.919 ms 3 nyc1-br1-ge2-1-0.gnaps.net (199.232.131.16) 6.611 ms 6.706 ms 6.755 ms 4 lax1-br1-gi4-2.gnaps.net (199.232.44.22) 81.437 ms 79.575 ms 79.534 ms 5 paix.bungi.net (198.32.176.7) 88.132 ms 88.293 ms 88.541 ms 6 172.17.31.7 (172.17.31.7) 92.330 ms 89.534 ms 89.563 ms 7 66.79.175.17 (66.79.175.17) 89.626 ms 92.533 ms 89.910 ms 8 66.79.175.6 (66.79.175.6) 91.463 ms 93.703 ms 90.066 ms 9 www.managed.com (66.79.160.10) 90.915 ms 90.608 ms 91.729 ms ===== End ==== The paths taking XO are a bit higher, but nothing abnormal for me.... Sirius
Posted by DVD, 06-30-2004, 01:17 PM
the ping is back to normal, at least for me.
Posted by mainarea, 06-30-2004, 01:28 PM
See http://www.webhostingtalk.com/showth...hreadid=291183
Posted by mainarea, 06-30-2004, 01:30 PM
I documented the problem from earlier at http://www.webhostingtalk.com/showth...hreadid=291183 with full traceroutes.
Posted by Jay Cornwall, 06-30-2004, 01:34 PM
ICMP is often given lower priority (both for packet ordering and dropping) to other packet types as it's primarily a monitoring system, non-critical to the network's use. If an uplink fills to near its capacity, routers will push through TCP, UDP and other packet types before allowing ICMP. This can give a false impression of the actual state of the connection when monitoring its responsiveness and integrity with pings/traceroutes. If a router on such a connection is configured to guarantee a maximum delivery time, you'll often see pings become stable at a high value even when TCP / UDP packets are getting through very quickly. Pinging isn't actually a particularly accurate way of measuring network latency, as half of the response time can be faked quite easily. (the details I will leave out, but I think pretty much every script kiddie game host knows about and does it anyway)
Posted by ChaosHosting, 06-30-2004, 01:57 PM
Back to normal for me, 70ms all the way through xo from minnesota.
Posted by joshiee, 06-30-2004, 02:11 PM
C:\Documents and Settings\joshiee>ping 65.75.170.309 Pinging 65.75.170. with 32 bytes of data: Reply from 65.75.170.: bytes=32 time=25ms TTL=49 Reply from 65.75.170.: bytes=32 time=26ms TTL=49 Reply from 65.75.170.: bytes=32 time=26ms TTL=49 Reply from 65.75.170.: bytes=32 time=24ms TTL=49 Ping statistics for 65.75.170.50: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 24ms, Maximum = 26ms, Average = 25ms C:\Documents and Settings\joshiee> looks fine to me..
Posted by Odd Fact, 06-30-2004, 02:45 PM
Moved to the Network Outages forum.
Posted by optimumd, 06-30-2004, 05:20 PM
Still slow here: | 15 | | 67.104.60.222 | 67.104.60.222.ptr.us.xo.net | - | | 1078 | -x | 67.104.60.0 |
Posted by biTe, 06-30-2004, 06:37 PM
Urrgggggg.. still bad for me... 12 67.104.60.222 1286ms 1326ms 1335ms TTL: 0 (67.104.60.222.ptr.us.xo.net ok)
Posted by mil22, 06-30-2004, 06:54 PM
Looks like it's been up and down for the last 6 hours, and mostly down. It's not just ICMP packets either - managed.com's website is very slow for me too, for example...
Posted by Steven, 06-30-2004, 08:05 PM
Mainarea, Thats pretty werid its going outbound with ALTER.NET isent that uunet or something?
Posted by mainarea, 06-30-2004, 09:05 PM
ALTER.NET is uunet, I believe the routing is Managed -> Bungi -> uunet. This was probably a capacity/configuration issue with Managed & Bungi. - Matt
Posted by RHChristian, 07-01-2004, 01:29 AM
Do they even know of the problem? I haven't seen any response from any Managed.com techs from my side. Edit: Big 300, whooo go Christian!
Posted by joshiee, 07-03-2004, 02:55 PM
Uh.. Is this happening again?! Ping statistics for 65.75.170.50: Packets: Sent = 329, Received = 223, Lost = 106 (32% loss), Approximate round trip times in milli-seconds: Minimum = 491ms, Maximum = 545ms, Average = 511ms Control-C ^C C:\Documents and Settings\joshiee>
Posted by optimumd, 07-03-2004, 02:55 PM
Yup, happening here too now.
Posted by joshiee, 07-03-2004, 03:07 PM
1 65.75.170.1 (65.75.170.1) 0.468 ms 0.474 ms 0.390 ms 2 66.79.175.5 (66.79.175.5) 0.411 ms 0.402 ms 0.259 ms 3 67.104.60.221.ptr.us.xo.net (67.104.60.221) 484.569 ms 484.335 ms 485.636 ms 4 p3-0-0.MAR2.Fremont-CA.us.xo.net (207.88.80.181) 475.738 ms 486.260 ms 482.569 ms notice hop3
Posted by yaax, 07-06-2004, 07:53 AM
Yes, it is now happening again - major packet lost: 5 packets transmitted, 1 packets received, 80% packet loss round-trip min/avg/max/mdev = 79.924/79.924/79.924/0.000 ms
Posted by hostace, 07-06-2004, 07:55 AM
Ping statistics for 65.75.179.xxx: Packets: Sent = 223, Received = 114, Lost = 109 (48% loss), Approximate round trip times in milli-seconds: Minimum = 190ms, Maximum = 599ms, Average = 240ms
Posted by -Ley-, 07-07-2004, 11:47 AM
we are called MCI now
Posted by server4sale, 07-07-2004, 01:20 PM
Isnt it WorldCom?
Posted by DeltaAnime, 07-07-2004, 02:47 PM
C:\Documents and Settings\fdias\Desktop>ping 66.79.190.x Pinging [66.79.190.x] with 32 bytes of data: Reply from 66.79.190.x: bytes=32 time=561ms TTL=48 Reply from 66.79.190.x: bytes=32 time=571ms TTL=48 Reply from 66.79.190.x: bytes=32 time=561ms TTL=48 Reply from 66.79.190.x: bytes=32 time=531ms TTL=48 Ping statistics for 66.79.190.x: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 531ms, Maximum = 571ms, Average = 556ms
Posted by mil22, 07-07-2004, 07:31 PM
Seems to be happening intermittently, lasts for about one hour at a time, and we have 2-3 attacks a day. Been going on for at least a week now. Wonder what it could be?
Posted by Joshua, 07-07-2004, 08:22 PM
WorldCom is now known as MCI.
Posted by Lancia, 07-08-2004, 08:52 PM
Is anyone having trouble with a Managed.com server at the moment? EDIT: Nevermind, my server just crashed.
Posted by bendmail, 07-09-2004, 01:58 PM
Managed.com = issues.....serious issues..lol