another network speed thread

[Julio]

Hi people,

Hope you could help me diagnosing some load issues I've been suffering.

During the day the sites in my VPS (ceres.nocdirect.com node) get very long page loads (20 to 30 seconds). These are standard sites, nothing heavy. Weird part is "top" report loads of: 0.38 - 0.46 - 0.45.

I opened a ticket (twice) and ask support to take a look at the entire node (looking for bad neighbors) but..funny thing...the issue is reported between high traffic hours (9am - 6pm) and the tech inspects the Server at 1 AM...of course, the answer is:
"...I have checked your vps & main node and load/traffic seems to be quite normal..."

Please load any of this sample sites (same VPS) and tell me if they're loading fast:

- www.erathis.com
- www.notiviajeros.com
- www.creasabores.com.pe
- www.pacificoadventures.com

Also, here (lima-Peru) we have some crappy bandwidth, can you tell me what speed you get downloading this:

http://store.obilabs.com/mamp.dmg.zip

I'm getting 30KB/s in average.

Thanks in advance.

[MKT]

20KBps checking from Italy, 7mbps residential line.

Feel free to check this file download test ( VPS network speed ), it's from my VPS ( node washington.nocdirect ).
My problems with speeds happen during USA office hours, techs continue to say that everything is ok.

I opened a support ticket on Sept 10, still no changes at all, it's still open and it contains simply several support reps telling that everything is ok.

[Julio]

Damn, I get 15Kb/s in my modest 2mbps home line.

A tracerout to your IP gives me 18 hops.....

isn't that too many hops? could someone confirm if that is ok?

traceroute to 216.180.245.169 (216.180.245.169), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 1.864 ms 2.414 ms 1.520 ms
2 190.81.6.1 (190.81.6.1) 123.254 ms 86.482 ms 33.103 ms
3 190.223.147.33 (190.223.147.33) 111.537 ms 58.159 ms 121.123 ms
4 190.81.134.90 (190.81.134.90) 123.607 ms 29.676 ms 129.870 ms
5 xe-6-4.r00.nycmny13.us.bb.gin.ntt.net (129.250.193.149) 287.465 ms 234.336 ms 345.632 ms
6 * xe-7-3.r02.nycmny01.us.bb.gin.ntt.net (129.250.4.53) 145.364 ms 226.505 ms
7 ae-5.r23.nycmny01.us.bb.gin.ntt.net (129.250.2.220) 138.998 ms
ae-4.r23.nycmny01.us.bb.gin.ntt.net (129.250.2.40) 144.210 ms
ae-5.r23.nycmny01.us.bb.gin.ntt.net (129.250.2.220) 152.737 ms
8 ae-1.r20.asbnva02.us.bb.gin.ntt.net (129.250.2.9) 162.945 ms 157.835 ms 134.645 ms
9 ae-0.r21.asbnva02.us.bb.gin.ntt.net (129.250.4.5) 152.925 ms 171.393 ms 133.735 ms
10 p64-0-1-0.r21.atlnga05.us.bb.gin.ntt.net (129.250.3.19) 151.542 ms 150.766 ms 167.237 ms
11 * * *
12 xe-7-3.r00.atlnga05.us.ce.gin.ntt.net (204.2.241.30) 142.206 ms 232.687 ms 258.179 ms
13 border10.tge4-1-bbnet2.acs.pnap.net (64.94.0.76) 164.238 ms
border10.tge3-1-bbnet1.acs.pnap.net (64.94.0.12) 213.834 ms
border10.tge4-1-bbnet2.acs.pnap.net (64.94.0.76) 161.650 ms
14 globalaccess-2.border10.acs.pnap.net (64.94.224.162) 221.781 ms 228.260 ms 149.806 ms
15 atl-core-g-g1-6.gnax.net (63.247.69.178) 150.830 ms 234.371 ms 215.263 ms
16 core-gi1-1.nocdirect.com (209.51.131.90) 373.906 ms 189.089 ms 239.436 ms
17 washington.nocdirect.com (216.180.245.130) 246.444 ms * 196.136 ms
18 216.180.245.169 (216.180.245.169) 167.514 ms 166.126 ms 147.089 ms

[Julio]

Man this is ridiculous:

We are making some tests, downloading a file from two different locations. Take a look at the image:



The first download is from a external site (http://www.mamp.info):

The second download is from our server http://store.obilabs.com/mamp.dmg.zip (ceres.nocdirect.com node).

look at the KB/s rate....

[Julio]

and a few minutes later:

[Frank Broughton]

I just checked all of them - CRAZY SLOW load times!

Hi people,

Hope you could help me diagnosing some load issues I've been suffering.

During the day the sites in my VPS (ceres.nocdirect.com node) get very long page loads (20 to 30 seconds). These are standard sites, nothing heavy. Weird part is "top" report loads of: 0.38 - 0.46 - 0.45.

I opened a ticket (twice) and ask support to take a look at the entire node (looking for bad neighbors) but..funny thing...the issue is reported between high traffic hours (9am - 6pm) and the tech inspects the Server at 1 AM...of course, the answer is:
"...I have checked your vps & main node and load/traffic seems to be quite normal..."

Please load any of this sample sites (same VPS) and tell me if they're loading fast:

- www.erathis.com
- www.notiviajeros.com
- www.creasabores.com.pe
- www.pacificoadventures.com

Also, here (lima-Peru) we have some crappy bandwidth, can you tell me what speed you get downloading this:

http://store.obilabs.com/mamp.dmg.zip

I'm getting 30KB/s in average.

Thanks in advance.

[Frank Broughton]

I just tried a file from my VPS at JPC - 41.5KB/s ridiculously slow, something is bad wrong at GNAX! The last few weeks seen to be very bad ones for JPC??? What is going on Greg/Les/Masood ????

20KBps checking from Italy, 7mbps residential line.

Feel free to check this file download test ( VPS network speed ), it's from my VPS ( node washington.nocdirect ).
My problems with speeds happen during USA office hours, techs continue to say that everything is ok.

I opened a support ticket on Sept 10, still no changes at all, it's still open and it contains simply several support reps telling that everything is ok.

[MKT]

you don't show me anything new, I was downloading a backup ( ~ 1.5GB of data ) @ < 10KBps so I had to bump my own ticket

a tech replied that he'd have network techs investigate this further because it seems to be intermittent. Well if we mean "during office hours" with it then yes, it is intermittent.

I guess the next reply will probably come during non-office hours, and in any case will read that there are no problems on the network or on the node, despite problems are undeniable

[Julio]

and it's definitely not a VPS high load issue...

[Ron]

do traceroutes... use WinMTR...

[Julio]

this is the tracerout to my server:

traceroute to archi.obilabs.com (69.73.131.128), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 10.453 ms 1.543 ms 1.625 ms
2 190.81.6.1 (190.81.6.1) 600.842 ms 585.958 ms 581.532 ms
3 190.223.147.33 (190.223.147.33) 576.181 ms * 338.760 ms
4 190.81.134.90 (190.81.134.90) 394.127 ms 504.973 ms 364.867 ms
5 xe-6-4.r00.nycmny13.us.bb.gin.ntt.net (129.250.193.149) 569.901 ms 678.437 ms 656.898 ms
6 xe-5-1.r03.nycmny01.us.bb.gin.ntt.net (129.250.3.173) 667.633 ms
xe-7-3.r02.nycmny01.us.bb.gin.ntt.net (129.250.4.53) 615.748 ms 688.455 ms
7 ae-5.r23.nycmny01.us.bb.gin.ntt.net (129.250.2.220) 839.138 ms
ae-4.r23.nycmny01.us.bb.gin.ntt.net (129.250.2.40) 941.694 ms *
8 ae-1.r20.asbnva02.us.bb.gin.ntt.net (129.250.2.9) 780.928 ms 887.071 ms 840.980 ms
9 ae-0.r21.asbnva02.us.bb.gin.ntt.net (129.250.4.5) 785.441 ms 776.997 ms 786.950 ms
10 p64-0-1-0.r21.atlnga05.us.bb.gin.ntt.net (129.250.3.19) 934.371 ms 854.464 ms 1053.411 ms
11 * * *
12 xe-7-3.r00.atlnga05.us.ce.gin.ntt.net (204.2.241.30) 939.693 ms 587.837 ms 630.632 ms
13 border10.tge3-1-bbnet1.acs.pnap.net (64.94.0.12) 518.591 ms 807.955 ms 1048.404 ms
14 globalaccess-2.border10.acs.pnap.net (64.94.224.162) 1090.530 ms 1001.311 ms 855.538 ms
15 atl-core-g-g1-6.gnax.net (63.247.69.178) 708.995 ms 843.077 ms 790.617 ms
16 core-gi1-1.nocdirect.com (209.51.131.90) 815.273 ms 869.068 ms 975.098 ms
17 ceres.nocdirect.com (69.73.170.26) 875.634 ms 823.140 ms 716.854 ms
18 archi.obilabs.com (69.73.131.128) 648.804 ms 589.189 ms 632.325 ms

[MKT]

I just tried a file from my VPS at JPC - 41.5KB/s ridiculously slow, something is bad wrong at GNAX! The last few weeks seen to be very bad ones for JPC??? What is going on Greg/Les/Masood ????

I just tried a file download from gnax and everything seems regular there.

The problem seems to be somewhere within jpc network.

I've sent them my winmtr output and traceroutes from all over the globe.

I continue to say that, as long as they don't tell us what's going on, the only thing we can suppose is that the network is heavily oversold.
I've been waiting for almost three months for a sign of commitment from JPC to fix this issue, but none has come so far.

[Ron]

this is the tracerout to my server:

traceroute to archi.obilabs.com (69.73.131.128), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  10.453 ms  1.543 ms  1.625 ms
 2  190.81.6.1 (190.81.6.1)  600.842 ms  585.958 ms  581.532 ms
 3  190.223.147.33 (190.223.147.33)  576.181 ms *  338.760 ms
 4  190.81.134.90 (190.81.134.90)  394.127 ms  504.973 ms  364.867 ms
 5  xe-6-4.r00.nycmny13.us.bb.gin.ntt.net (129.250.193.149)  569.901 ms  678.437 ms  656.898 ms
 6  xe-5-1.r03.nycmny01.us.bb.gin.ntt.net (129.250.3.173)  667.633 ms
    xe-7-3.r02.nycmny01.us.bb.gin.ntt.net (129.250.4.53)  615.748 ms  688.455 ms
 7  ae-5.r23.nycmny01.us.bb.gin.ntt.net (129.250.2.220)  839.138 ms
    ae-4.r23.nycmny01.us.bb.gin.ntt.net (129.250.2.40)  941.694 ms *
 8  ae-1.r20.asbnva02.us.bb.gin.ntt.net (129.250.2.9)  780.928 ms  887.071 ms  840.980 ms
 9  ae-0.r21.asbnva02.us.bb.gin.ntt.net (129.250.4.5)  785.441 ms  776.997 ms  786.950 ms
10  p64-0-1-0.r21.atlnga05.us.bb.gin.ntt.net (129.250.3.19)  934.371 ms  854.464 ms  1053.411 ms
11  * * *
12  xe-7-3.r00.atlnga05.us.ce.gin.ntt.net (204.2.241.30)  939.693 ms  587.837 ms  630.632 ms
13  border10.tge3-1-bbnet1.acs.pnap.net (64.94.0.12)  518.591 ms  807.955 ms  1048.404 ms
14  globalaccess-2.border10.acs.pnap.net (64.94.224.162)  1090.530 ms  1001.311 ms  855.538 ms
15  atl-core-g-g1-6.gnax.net (63.247.69.178)  708.995 ms  843.077 ms  790.617 ms
16  core-gi1-1.nocdirect.com (209.51.131.90)  815.273 ms  869.068 ms  975.098 ms
17  ceres.nocdirect.com (69.73.170.26)  875.634 ms  823.140 ms  716.854 ms
18  archi.obilabs.com (69.73.131.128)  648.804 ms  589.189 ms  632.325 ms

Whoa! It looks like your own end is hosed.... compare to mine:

tracert XXXXXXX

Tracing route to XXXXXXX [69.73.189.XXX]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     2 ms     2 ms     3 ms  10.9.44.XXX
  3     4 ms     4 ms     4 ms  G9-0-3-894.BSTNMA-LCR-08.verizon-gni.net [130.81.110.30]
  4     5 ms     4 ms     4 ms  so-0-3-0-0.BOS-BB-RTR2.verizon-gni.net [130.81.29.254]
  5    13 ms    13 ms    13 ms  0.so-0-2-0.XL4.BOS4.ALTER.NET [152.63.16.141]
  6    49 ms    99 ms    13 ms  0.xe-4-1-0.XL4.NYC4.ALTER.NET [152.63.3.102]
  7    16 ms    16 ms    15 ms  GigabitEthernet5-0-0.GW1.NYC4.ALTER.NET [152.63.20.101]
  8    16 ms    15 ms    15 ms  teliasonera-gw.customer.alter.net [157.130.60.14]
  9    13 ms    13 ms    13 ms  nyk-bb1-link.telia.net [80.91.249.17]
 10    22 ms    21 ms    22 ms  ash-bb1-link.telia.net [213.248.83.20]
 11    35 ms    35 ms    34 ms  atl-bb1-link.telia.net [80.91.252.218]
 12    36 ms    36 ms    36 ms  globalnet-127291-atl-bb1.c.telia.net [213.248.90.54]
 13   130 ms   200 ms   199 ms  atl-core-g-g1-6.gnax.net [63.247.69.178]
 14    37 ms    36 ms    36 ms  core-gi1-1.nocdirect.com [209.51.131.90]
 15    38 ms    37 ms    38 ms  XXXXXXX [69.73.189.XXX]

===================================================

tracert XXXXXXX

Tracing route to XXXXXXX [69.73.189.XXX]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     4 ms     2 ms     2 ms  10.9.44.XXX
  3     4 ms     4 ms     4 ms  G9-0-3-894.BSTNMA-LCR-08.verizon-gni.net [130.81.110.30]
  4     4 ms     4 ms     4 ms  so-0-3-0-0.BOS-BB-RTR2.verizon-gni.net [130.81.29.254]
  5    13 ms    13 ms    13 ms  0.so-0-2-0.XL4.BOS4.ALTER.NET [152.63.16.141]
  6    13 ms    13 ms    13 ms  0.xe-4-1-0.XL4.NYC4.ALTER.NET [152.63.3.102]
  7    16 ms    16 ms    13 ms  GigabitEthernet7-0-0.GW1.NYC4.ALTER.NET [152.63.20.53]
  8    16 ms    16 ms    16 ms  teliasonera-gw.customer.alter.net [157.130.60.14]
  9    13 ms    13 ms    13 ms  nyk-bb1-link.telia.net [80.91.249.17]
 10    22 ms    21 ms    22 ms  ash-bb1-link.telia.net [213.248.83.20]
 11    35 ms    49 ms    33 ms  atl-bb1-link.telia.net [80.91.252.214]
 12    55 ms   204 ms   210 ms  globalnet-127291-atl-bb1.c.telia.net [213.248.90.54]
 13    36 ms    36 ms    36 ms  atl-core-g-g1-6.gnax.net [63.247.69.178]
 14    36 ms    35 ms    37 ms  core-gi1-1.nocdirect.com [209.51.131.90]
 15    42 ms    39 ms    40 ms  XXXXXXX [69.73.189.XXX]

Clearly the issue I'm seeing is at hops 12 and 13 but it looks like your comms are hosed at every step along the way. Unless I'm reading that incorrectly, which is always possible...

[Vin DSL]

Also, here (lima-Peru) we have some crappy bandwidth, can you tell me what speed you get downloading this:

http://store.obilabs.com/mamp.dmg.zip

I'm getting 30KB/s in average.

Thanks in advance.

Heh! Okay, I'll bite. Maybe one of these days... oh, never mind!

Anyway, here are the results from dusty Arizona...

Sorry! Current speed: 778.2 KB/s

Would you like me to try it again, standing on my head, in a thunderstorm -- or something?

[Vin DSL]

Here's a traceroute, from my neck of the globe...

vindsl@Zuul:~$ tracepath archi.obilabs.com
 1:  Zuul                                                  0.169ms pmtu 1500
 1:  10.0.0.1                                              1.315ms 
 1:  10.0.0.1                                              1.286ms 
 2:  10.0.0.1                                              1.167ms pmtu 1492
 2:  phnx-dsl-gw41-233.phnx.qwest.net                     53.403ms 
 3:  phnx-agw1.inet.qwest.net                             53.431ms asymm  4 
 4:  lap-brdr-03.inet.qwest.net                           64.177ms asymm  6 
 5:  63.146.26.22                                         64.435ms asymm  6 
 6:  dls-bb1-link.telia.net                              115.970ms 
 7:  atl-bb1-link.telia.net                              127.661ms 
 8:  globalnet-127291-atl-bb1.c.telia.net                161.877ms asymm  9 
 9:  atl-core-g-g1-6.gnax.net                            127.636ms asymm  7 
10:  core-gi1-1.nocdirect.com                            127.139ms asymm  8 
11:  ceres.nocdirect.com                                 131.868ms asymm 10 
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
18:  no reply
19:  no reply
20:  no reply
21:  no reply
22:  no reply
23:  no reply
24:  no reply
25:  no reply
26:  no reply
27:  no reply
28:  no reply
29:  no reply
30:  no reply
31:  no reply
     Too many hops: pmtu 1492
     Resume: pmtu 1492