MDS Connection Time

I'm running Firefox with Verizon internet speed of 50/25. For some time now connecting to MDS seems to take an inordinate amount of time. Is it me or are others experiencing slow connection?

Thanks.

I'm having slow speeds with Verizon on everything.

Norton said:

I'm having slow speeds with Verizon on everything.

Click to expand...

For the past couple of weeks, we have been having problems with our Verizon internet. Sometimes I can't get logged into my email all day. We called them and they said they are upgrading their system and it will get better.

I have Verizion 25/15, and I am also finding MDS to be slow much of the time lately, when other web sites seem fine.

KL1 said:

I have Verizion 25/15, and I am also finding MDS to be slow much of the time lately, when other web sites seem fine.

Click to expand...

Same here

Verizon here. No problems for me. I still hate Verizon.

Comcast for the win!

Phew...great to hear!

I was about to upgrade to Verizon's superduper "it'll connect before ya turn the machine on" promotion.

Verizon here too. No problems. It may be regional.

Comcast here. MDS has been slow off and on for the past few weeks. Fast right now.

Slow Verizon and slow Firefox here.

Verizon Fios 75/35

Slow on Verizon in Elkridge....

Hmmm...

I had this problem earlier this year. Then I added no-script to the browsers. Speed spiffed right up, 1/2 the web pages no longer work correctly, but they are much faster.

Full function, or full speed? Sigh.

Mine is something like this:

WARNING <TECHNOBABBLE> AHEAD

Slow on my Verizon as well from my home. It is not a bandwidth issue, which most of the speed tests look at. I believe it is a network routing issue between Verizon and Cogentco.

When I do a traceroute from my home on Verizon there is a large delay once you leave the Verizon network and enter the Cogentco network. There are then multiple hops in Cogentco before you get to the actual server. Those hops in the Cogentco network are slower than normal.

mark$ traceroute www.mdshooters.com
traceroute to mdshooters.com (199.91.126.234), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 39.150 ms 34.828 ms 44.902 ms
2 x.x.x.x 11.656 ms 18.750 ms 22.382 ms
3 g1-8-0-7.washdc-lcr-22.verizon-gni.net (100.41.201.31) 19.843 ms 24.708 ms 36.115 ms
4 ae2-0.res-bb-rtr2.verizon-gni.net (130.81.199.138) 30.105 ms
xe-13-1-2-0.res-bb-rtr2.verizon-gni.net (130.81.174.228) 28.154 ms
so-7-1-0-0.res-bb-rtr2.verizon-gni.net (130.81.199.32) 32.808 ms
5 * * *
6 te0-1-0-14.ccr41.iad02.atlas.cogentco.com (154.54.12.45) 54.199 ms 41.651 ms
te0-3-0-14.ccr41.iad02.atlas.cogentco.com (154.54.13.137) 57.704 ms
7 be2176.ccr21.dca01.atlas.cogentco.com (154.54.41.54) 69.421 ms 49.582 ms 69.105 ms
8 be2152.ccr21.ord01.atlas.cogentco.com (154.54.30.122) 91.520 ms 73.604 ms 55.915 ms
9 be2156.ccr21.mci01.atlas.cogentco.com (154.54.6.85) 80.955 ms 120.343 ms 103.415 ms
10 * * *
11 * static-199-193-244-249.a.awsrdns.net (199.193.244.249) 61.122 ms 51.727 ms
12 te2-1.cr04.mci02.awscore.net (162.208.87.34) 49.128 ms 54.841 ms 66.227 ms
13 * static-199-193-245-54.a.awsrdns.net (199.193.245.54) 61.172 ms *

When you run this a couple of times in a row, sometimes it is very fast to respond. Other times it seems to get bogged down when you hit this block of hops.

7 be2176.ccr21.dca01.atlas.cogentco.com (154.54.41.54) 69.421 ms 49.582 ms 69.105 ms
8 be2152.ccr21.ord01.atlas.cogentco.com (154.54.30.122) 91.520 ms 73.604 ms 55.915 ms
9 be2156.ccr21.mci01.atlas.cogentco.com (154.54.6.85) 80.955 ms 120.343 ms 103.415 ms

It is fast from my office on a different network. It is also fast from external traceroute sources.

http://network-tools.com/default.asp?prog=trace&host=www.mdshooters.com

TraceRoute from Network-Tools.com to 199.91.126.234 [www.mdshooters.com]
Hop (ms) (ms) (ms) IP Address Host name
1 0 0 0 8.9.232.73 8-1-18.ear1.dallas1.level3.net
2 Timed out 0 0 4.69.145.75 ae-2-70.edge2.dallas1.level3.net
3 1 1 2 4.68.111.102 -
4 1 1 1 154.54.7.45 be2031.ccr21.dfw01.atlas.cogentco.com
5 12 11 11 154.54.2.113 be2012.ccr21.mci01.atlas.cogentco.com
6 11 11 11 38.104.86.86 -
7 29 28 28 199.193.244.249 static-199-193-244-249.a.awsrdns.net
8 28 28 28 162.208.87.34 te2-1.cr04.mci02.awscore.net
9 25 25 25 199.193.245.54 static-199-193-245-54.a.awsrdns.net
10 29 28 28 199.91.126.234 static-199-91-126-234.b.awsrdns.net
Trace complete

I checked from a server I have in Chicago and the traceroute is good from there as well. These are just data points that can be taken to the web host to see if they can check the network routing from Verizon.

</TECHNOBABLE>

I have Verizon too and, perhaps in line with what MacMoov said, the connections speed is fine, once things start moving. However, when I click on a link on MDS, for instance to select a message from a forum list, it sometimes takes several seconds, or a 2nd click, to actually start loading the page. Once it does, the page displays almost instantaneously. I use Firefox on linux and am basing this observation partially on looking at the little "spinner" firefox uses on the browser tabs to show connection progress.

Problems with Cogent here as well. I'm fast from AT&T's LTE network, but it doesn't transit the Cogent router. Specifically it's 38.104.86.86 that is holding everything back for me.

-Jim

Sloooow and a bit frustrating. This site takes longer than about any other one I go to.

I have Verizon 50/25 and Firefox. MDS has a huge delay loading pages (10 to 40 seconds per page) All other websites seem fine, its been this way for about a week or two now.