Linode Forum
Linode Community Forums 		 FAQFAQ    SearchSearch    MembersMembers      Register Register 
 LoginLogin [ Anonymous ] 
Post new topic  Reply to topic

Board index » Linode.com Related Forums » Feature Request/Bug Report
  Previous topic | Next topic 
Author Message
jstarks
PostPosted: Mon Feb 09, 2004 4:08 pm 
Offline
Senior Newbie

Joined: Wed Jan 28, 2004 10:06 pm
Posts: 11
I'm getting pretty bad network performance with host15 when connecting to/from certain networks. For example, to the Yale network:

Code:
traceroute to yale.edu (130.132.59.127), 30 hops max, 38 byte packets
 1  gige-g1-0-21.gsr12012.fmt.he.net (64.71.157.17)  1.034 ms  1.013 ms  1.184 ms
 2  pos5-0.gsr12012.pao.he.net (64.62.249.122)  2.244 ms  2.854 ms  2.440 ms
 3  sntcca2lce1-gige.wcg.net (64.200.150.49)  490.177 ms  540.087 ms  521.842 ms
 4  snfccapaix-qwest-pos.wcg.net (64.200.199.126)  537.824 ms  532.005 ms  539.778 ms
 5  svl-core-03.inet.qwest.net (205.171.205.29)  539.081 ms  535.883 ms  547.197 ms
 6  chi-core-01.inet.qwest.net (205.171.8.194)  631.134 ms  528.630 ms  518.622 ms
 7  chi-core-03.inet.qwest.net (205.171.20.174)  558.820 ms  490.596 ms  470.053 ms
 8  jfk-core-01.inet.qwest.net (205.171.8.161)  489.166 ms  541.292 ms  521.442 ms
 9  bos-core-02.inet.qwest.net (205.171.8.17)  533.777 ms  544.543 ms  528.641 ms
10  bos-edge-02.inet.qwest.net (205.171.28.30)  529.626 ms  562.503 ms  567.633 ms
11  63.145.0.14 (63.145.0.14)  559.494 ms  565.896 ms  572.791 ms
12  new-greed.net.yale.edu (130.132.1.19)  574.333 ms  586.483 ms  593.355 ms
13  yale.edu (130.132.59.127)  597.956 ms  573.903 ms  569.470 ms


Now to host1, on the other hand:
Code:
traceroute to host1.linode.com (64.5.53.6), 30 hops max, 38 byte packets
 1  gige-g1-0-21.gsr12012.fmt.he.net (64.71.157.17)  1.274 ms  2.218 ms  2.072 ms
 2  pos5-0.gsr12012.pao.he.net (64.62.249.122)  2.645 ms  2.045 ms  1.988 ms
 3  peer-01.palo.twtelecom.net (198.32.176.111)  2.413 ms  2.480 ms  2.929 ms
 4  dist-01-so-3-2-0-0.okld.twtelecom.net (66.192.250.37)  4.432 ms  4.317 ms  4.286 ms
 5  core-01-so-0-0-0-0.mdso.twtelecom.net (168.215.55.78)  6.425 ms  6.314 ms  6.317 ms
 6  core-01-so-0-0-0-0.dlfw.twtelecom.net (66.192.255.90)  64.919 ms  64.466 ms  64.471 ms
 7  66-192-253-113.gen.twtelecom.net (66.192.253.113)  64.810 ms  66.102 ms  64.805 ms
 8  168.215.241.150 (168.215.241.150)  65.038 ms  64.950 ms  65.131 ms
 9  car1-1-v2.dllstx2.theplanet.com (12.96.160.43)  48.900 ms  49.261 ms  49.381 ms
10  host1.linode.com (64.5.53.6)  48.845 ms  49.224 ms  641.221 ms


This kind of congestion seems to come and go. Makes ssh connections pretty tough. I'm also having trouble download Debian updates. Anything you can do about this? Thanks.
Top
   
Reply with quote  
caker
 Post subject:
PostPosted: Mon Feb 09, 2004 4:31 pm 
Offline
Linode Staff
User avatar

Joined: Tue Apr 15, 2003 6:24 pm
Posts: 3090
Website: http://www.linode.com/
Location: Galloway, NJ
Hurricane Electric informed me last night they're having trouble with two of their peering networks:

Quote:
We are currently experiencing routing issues with Williams Transit and with Level3.net. Our administrators are working with both companies to resolve the issues. (FWIW: Williams Transport is aware of their errors. Level3.net is still trying to figure out what went wrong.)


Your first traceroute shows the trouble with Williams (look at tht time difference between hops 2 and 3). If this keeps up for a few hours more I'll contact HE again.

Thanks,
-Chris
Top
   
Reply with quote  
jstarks
 Post subject:
PostPosted: Mon Feb 09, 2004 6:43 pm 
Offline
Senior Newbie

Joined: Wed Jan 28, 2004 10:06 pm
Posts: 11
Looks like they got it fixed. Thanks, Chris.
Top
   
Reply with quote  
caker
 Post subject:
PostPosted: Mon Feb 09, 2004 7:47 pm 
Offline
Linode Staff
User avatar

Joined: Tue Apr 15, 2003 6:24 pm
Posts: 3090
Website: http://www.linode.com/
Location: Galloway, NJ
jstarks wrote:
Looks like they got it fixed. Thanks, Chris.

Here's the follow up response from HE:

Quote:
We had some congestion this morning which our admins worked on. We also
brought up new transit circuts today to resolve some of these issues,
and are still working to bring more up.

A trace to yale now looks a lot cleaner now:

1 pos5-0.gsr12012.pao.he.net (64.62.249.122) 0 msec 4 msec 0 msec
2 sntcca2lce1-gige.wcg.net (64.200.150.49) [AS 7911] 4 msec 0 msec 4 msec
3 snfccapaix-qwest-pos.wcg.net (64.200.199.126) [AS 7911] 0 msec 4 msec 0 msec
4 svl-core-03.inet.qwest.net (205.171.205.29) [AS 209] 4 msec 4 msec 0 msec
5 chi-core-01.inet.qwest.net (205.171.8.194) [AS 209] 96 msec 60 msec 60 msec
6 chi-core-03.inet.qwest.net (205.171.20.174) [AS 209] 60 msec 60 msec 76 msec
7 jfk-core-01.inet.qwest.net (205.171.8.161) [AS 209] 76 msec 72 msec 72 msec
8 bos-core-02.inet.qwest.net (205.171.8.17) [AS 209] 76 msec 76 msec 80 msec
9 bos-edge-02.inet.qwest.net (205.171.28.30) [AS 209] 76 msec 80 msec 132 msec
10 63.145.0.14 [AS 209] 80 msec 84 msec 76 msec
11 new-greed.net.yale.edu (130.132.1.19) [AS 29] 84 msec 84 sec 80 msec
12 yale.edu (130.132.59.127) [AS 29] 84 msec 84 msec 84 msec

-Chris
Top
   
Reply with quote  
Display posts from previous:  Sort by  
Post new topic  Reply to topic

Board index » Linode.com Related Forums » Feature Request/Bug Report


Who is online

Users browsing this forum: mwchase and 2 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
RSS

Powered by phpBB® Forum Software © phpBB Group