Portal Home > Knowledgebase > Articles Database > PacketLoss once again @ Managed.com


PacketLoss once again @ Managed.com




Posted by Crocket, 04-03-2004, 11:49 AM
Looks like im getting packet loss, only like 45% of the packets are getting through. 1 <1 ms <1 ms <1 ms 192.168.0.1 2 18 ms 17 ms 17 ms lo1-bba1.th.eclipse.net.uk [212.104.130.141] 3 18 ms 18 ms 18 ms ge1-2-core3.th.eclipse.net.uk [81.5.191.37] 4 19 ms 18 ms 18 ms cr02.ldn01.pccwbtn.net [195.66.224.167] 5 203 ms 202 ms 203 ms pos1-1.cr02.sjo01.pccwbtn.net [63.218.6.74] 6 211 ms 250 ms 397 ms 63.218.7.6 7 202 ms 198 ms 199 ms f2-0-1.core1.sjc.layer42.net [69.36.239.61] 8 209 ms 199 ms 200 ms f0-0.core2.sjc.layer42.net [69.36.239.57] 9 205 ms 204 ms 211 ms bungi-gw4.layer42.net [69.36.239.134] 10 189 ms 190 ms 190 ms 66-154-102-41.assertivenetworks.net [66.154.102. 41] 11 186 ms 185 ms 187 ms assertive.managed.com [66.154.102.5] 12 191 ms 191 ms * 66.79.175.2 13 * * 190 ms 66.79.189.*** Reply from 66.79.189.***: bytes=32 time=189ms TTL=50 Reply from 66.79.189.***: bytes=32 time=188ms TTL=50 Request timed out. Reply from 66.79.189.***: bytes=32 time=186ms TTL=50 Reply from 66.79.189.***: bytes=32 time=188ms TTL=50 Reply from 66.79.189.***: bytes=32 time=187ms TTL=50 Request timed out. Request timed out. Reply from 66.79.189.***: bytes=32 time=192ms TTL=50 Request timed out. Request timed out. Request timed out. Reply from 66.79.189.***: bytes=32 time=195ms TTL=50 Request timed out. Request timed out. Reply from 66.79.189.***: bytes=32 time=209ms TTL=50 Reply from 66.79.189.***: bytes=32 time=193ms TTL=50 Request timed out. Request timed out. Request timed out. Request timed out. Reply from 66.79.189.***: bytes=32 time=193ms TTL=50 Request timed out. Reply from 66.79.189.***: bytes=32 time=190ms TTL=50 Request timed out. Request timed out. Request timed out. Request timed out. Reply from 66.79.189.***: bytes=32 time=191ms TTL=50 Reply from 66.79.189.***: bytes=32 time=189ms TTL=50 Reply from 66.79.189.***: bytes=32 time=200ms TTL=50 Request timed out. Reply from 66.79.189.***: bytes=32 time=192ms TTL=50 Reply from 66.79.189.***: bytes=32 time=186ms TTL=50 Reply from 66.79.189.***: bytes=32 time=192ms TTL=50 Reply from 66.79.189.***: bytes=32 time=191ms TTL=50 Reply from 66.79.189.***: bytes=32 time=190ms TTL=50 Request timed out. Reply from 66.79.189.***: bytes=32 time=190ms TTL=50 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.189.***: bytes=32 time=188ms TTL=50 Request timed out. Reply from 66.79.189.***: bytes=32 time=193ms TTL=50 Reply from 66.79.189.***: bytes=32 time=196ms TTL=50 Reply from 66.79.189.***: bytes=32 time=202ms TTL=50 Request timed out. Request timed out. Request timed out. Reply from 66.79.189.***: bytes=32 time=191ms TTL=50 Request timed out. Request timed out. Request timed out. Request timed out. Reply from 66.79.189.***: bytes=32 time=279ms TTL=50 Request timed out. Request timed out. Reply from 66.79.189.***: bytes=32 time=189ms TTL=50 Request timed out. Reply from 66.79.189.***: bytes=32 time=342ms TTL=50 Reply from 66.79.189.***: bytes=32 time=344ms TTL=50 Reply from 66.79.189.***: bytes=32 time=271ms TTL=50 Reply from 66.79.189.***: bytes=32 time=207ms TTL=50 Reply from 66.79.189.***: bytes=32 time=186ms TTL=50 Request timed out. Request timed out. Request timed out. Reply from 66.79.189.***: bytes=32 time=231ms TTL=50 Reply from 66.79.189.***: bytes=32 time=257ms TTL=50 Request timed out. Reply from 66.79.189.***: bytes=32 time=189ms TTL=50 Reply from 66.79.189.***: bytes=32 time=193ms TTL=50 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 66.79.189.***: bytes=32 time=225ms TTL=50 Request timed out. Request timed out. Reply from 66.79.189.***: bytes=32 time=212ms TTL=50 Request timed out. Request timed out. Request timed out. Reply from 66.79.189.***: bytes=32 time=188ms TTL=50 Reply from 66.79.189.***: bytes=32 time=186ms TTL=50 Request timed out. Request timed out. Request timed out. Reply from 66.79.189.***: bytes=32 time=186ms TTL=50 Reply from 66.79.189.***: bytes=32 time=189ms TTL=50 Request timed out. Request timed out. Request timed out. Request timed out. Reply from 66.79.189.***: bytes=32 time=190ms TTL=50 Request timed out. Reply from 66.79.189.***: bytes=32 time=184ms TTL=50 Request timed out. Reply from 66.79.189.***: bytes=32 time=192ms TTL=50 Request timed out. Reply from 66.79.189.***: bytes=32 time=235ms TTL=50 Request timed out. Request timed out. Reply from 66.79.189.***: bytes=32 time=191ms TTL=50 Request timed out. Request timed out. Request timed out. Request timed out. Reply from 66.79.189.***: bytes=32 time=192ms TTL=50 Request timed out. Request timed out. Request timed out. Reply from 66.79.189.***: bytes=32 time=191ms TTL=50 Reply from 66.79.189.***: bytes=32 time=192ms TTL=50 Request timed out. Request timed out. Does Managed.com have a news page? where there are updates on the service?!

Posted by WirralNet Matt, 04-03-2004, 11:55 AM
That the problem hen your ISP routes via Layer42. No problem here, but then I get there via AboveNet on my DSL: I get some packet loss when I use my ntl cable connection - it too routes via Layer42.

Posted by Crocket, 04-03-2004, 12:19 PM
well im on DSL! and its going via layer42. I take it there is no way to get it switched?! How long is this packetloss going to go on for!?

Posted by WirralNet Matt, 04-03-2004, 12:29 PM
As long as your ISP (it does not matter if its cable or DSL its the actual ISP) routes via Layer42. Unless Layer42 suddenly starts working for a change. But then when that happens you will see pigs flying.

Posted by AA2004, 04-03-2004, 12:48 PM
I've been having packet losses all day with my site on a Managed.com server; According to your rule 'Ping' (rule nr 6), your ping-service is not working as specified. Message: Packets lost (10%) Regards, - the WatchMouse Team

Posted by thedavid, 04-03-2004, 01:19 PM
Moved to the network issues/outages forum.

Posted by Mfjp, 04-04-2004, 12:25 AM
XO incoming is gone as well. Trace from AS30490 via AS2828: 1 GigE03-FRMT1a (208.37.25.1) 0.404 ms 0.318 ms 0.286 ms 2 206.111.149.130.ptr.us.xo.net (206.111.149.130) 1.544 ms 0.372 ms 0.230 ms 3 ge9-0.DCR1.DC-Fremont-CA.us.xo.net (205.158.60.161) 0.397 ms 0.173 ms 0.126 ms 4 p5-1-0-2.RAR2.SanJose-CA.us.xo.net (65.106.2.153) 1.021 ms 0.839 ms 0.736 ms 5 p1-0.IR1.SanJose2-CA.us.xo.net (65.106.5.186) 1.412 ms 1.159 ms 1.117 ms 6 64.125.12.181.available.above.net (64.125.12.181) 1.617 ms 1.495 ms 1.332 ms 7 so-5-0-0.mpr4.sjc2.us.above.net (64.125.30.178) 1.759 ms 1.517 ms 1.487 ms 8 so-0-0-0.er10a.sjc2.us.above.net (64.125.30.94) 1.945 ms 1.969 ms 11.403 ms 9 reserved.above.net (209.133.64.124) 1.823 ms 1.606 ms 1.615 ms 10 66-154-102-52.assertivenetworks.net (66.154.102.52) 2.074 ms 1.609 ms 1.574 ms 11 66.79.175.2 (66.79.175.2) 2.038 ms 1.916 ms 1.744 ms 12 www.managed.com (66.79.160.10) 1.768 ms 1.622 ms 1.571 ms So, either their XO feed is gone, or XO's NOC nullroute/stop announcing their IP.

Posted by Division Host, 04-05-2004, 12:51 AM
ive been having them all day also i thought it was me till customer complaining ftp is slow.

Posted by RackRhino, 04-05-2004, 09:24 AM
Yea, seem's my servers are running slow, and the sites are taking some time to load. It would be nice if they had a forum on there site, so they can atleast post information (god knows how much money they make and they cant afford online asst.)

Posted by mark1hos, 04-07-2004, 04:37 AM
We were looking at getting a server from them for private use not public use. However, a couple of things put us off: 1. Their uptime guarantee states if for more than 45mins in any given 30 days of downtime is incurred they will give you 100GB of additional bandwidth for use next month??? Is it me or does this not really help if you were to host clients and all you got was extra bandwidth for experiencing 2 hours of downtime? 2. Every time I come to visit WHT they always appear in the host down section. Is there anyone that can give me their opinion? Is managed.com that bad when it comes to downtime etc? Thanks in advance. Regards,

Posted by music, 04-07-2004, 04:50 AM
Managed.com seems to have made improvements with the addition of XO. Keep in minded that any discount operation is going to have a fare share of posts that are related to individual server problems. A forum at managed.com would go a long way to improve communications.

Posted by wheimeng, 04-07-2004, 08:14 AM
Remember, can't complain for the price that you are paying.

Posted by rcthost, 04-07-2004, 10:35 PM
All of my servers appear to be unreachable.

Posted by rcthost, 04-07-2004, 11:07 PM
Nevermind, only my main servers is down. Managed network is up!

Posted by MiSV, 04-08-2004, 04:34 AM
No packet loss observed here, albeit for some reason the outgoing bandwith doesn't exceed 150KB/sec (routed via above.net)



Was this answer helpful?

Add to Favourites Add to Favourites    Print this Article Print this Article

Also Read
Burst down?? (Views: 629)