Topic 'April 14th, 11 PM Tests - START account' in forum 'Start Communications users forum' - dslreports.com http://www.dslreports.com/forum/April-14th-11-PM-Tests-START-account-27068594 en Fri, 24 May 2013 23:47:08 EDT Fri, 24 May 2013 23:47:08 EDT Re: Cogeco to START - Changeover Logistics http://www.dslreports.com/forum/Re-Cogeco-to-START-Changeover-Logistics-27342147
Now to cancel cogeco and I am going to go mark the box with a label saying TPIA no disconnecty. :-p]]> http://www.dslreports.com/forum/Re-Cogeco-to-START-Changeover-Logistics-27342147 Wed, 18 Jul 2012 18:45:23 EDT Re: Cogeco to START - Changeover Logistics http://www.dslreports.com/forum/Re-Cogeco-to-START-Changeover-Logistics-27306715 http://www.dslreports.com/forum/Re-Cogeco-to-START-Changeover-Logistics-27306715 Sat, 07 Jul 2012 12:41:13 EDT Re: Cogeco to START - Changeover Logistics http://www.dslreports.com/forum/Re-Cogeco-to-START-Changeover-Logistics-27305925 http://www.dslreports.com/forum/Re-Cogeco-to-START-Changeover-Logistics-27305925 Sat, 07 Jul 2012 07:47:13 EDT Re: April 14th, 11 PM Tests - START account http://www.dslreports.com/forum/Re-April-14th-11-PM-Tests-START-account-27297142 After the Phantom PING was taken into custody for the 2nd time, my latest Ping is down to 10 or 11ms :) , using nexicom.speedtest.com , which seems to be the fastest test server, and one of 2 now in Toronto (Teksavvy is sponsoring the other).]]> http://www.dslreports.com/forum/Re-April-14th-11-PM-Tests-START-account-27297142 Wed, 04 Jul 2012 07:40:13 EDT Re: April 14th, 11 PM Tests - START account http://www.dslreports.com/forum/Re-April-14th-11-PM-Tests-START-account-27141695 Here are a couple of updates related to the current thread.

This one contains some newer better speed test results :

»Phantom PING Apprehended !

This next direct link summarizes why I left Cogeco in the first place, links to some further threads for more details, explains some of what I like better about START, and is sort of like a couple of reviews bundled together :

»Re: Cogeco's Broken Usage Meter]]> http://www.dslreports.com/forum/Re-April-14th-11-PM-Tests-START-account-27141695 Sun, 13 May 2012 03:18:58 EDT April 14th, 11 PM Tests - START account http://www.dslreports.com/forum/April-14th-11-PM-Tests-START-account-27119064 BTW,

April 14th, 11 PM
Montreal (FibreNoire server) :


NOW, the both cities' numbers look right together. :)

Except of course for that elusive character, 'The Phantom Ping of the Hop-era Number Three'. :D]]> http://www.dslreports.com/forum/April-14th-11-PM-Tests-START-account-27119064 Sat, 14 Apr 2012 23:09:30 EDT April 14th, 11 PM Tests - START account http://www.dslreports.com/forum/April-14th-11-PM-Tests-START-account-27119041 said by rocca:

Nexicom peering is complete.

 
No Kidding ! :)

Toronto (Nexicom server) :


Tracing route to nexicom.com [216.168.96.37]
over a maximum of 30 hops:

1 - 1 ms 1 ms 1 ms 192.168.67.1
2 - 7 ms 9 ms 7 ms 10.205.36.1
3 - 45 ms 43 ms 42 ms asr-link1-burlington1.net.start.ca [64.140.112.154]
4 - 42 ms 43 ms 43 ms core1-toronto1-te3-3.net.start.ca [64.140.112.153]
5 - 48 ms 43 ms 41 ms xe4-3-0-56.core1.toronto1.nexicom.net [206.108.34.66]
6 - 42 ms 43 ms 42 ms xe3-3-0.core2.toronto1.nexicom.net [98.124.50.241]
7 - 53 ms 52 ms 51 ms dis2-rtr-mb-ge7-3-vl4.nexicom.net [98.124.0.225]
8 - 50 ms 55 ms 52 ms ge6-0-23.dis3.millbrook1.nexicom.net [98.124.59.130]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * ^C

Hey, START's routers/switches even have names now.

[Dave breaks out some bubbly for christenings - ginger ale, that is....]

= = = = = = = = = =

And, I had not tested this next way before, but it says we get an 'A'. :)

April 15th, 2 AM
Toronto (Nexicom server) :
]]> http://www.dslreports.com/forum/April-14th-11-PM-Tests-START-account-27119041 Sat, 14 Apr 2012 22:55:19 EDT Re: Anticipation http://www.dslreports.com/forum/Re-Anticipation-27119024 said by Last Parade:

I'm on TekSavvy at the moment. And they've forgotten to shut down the line. Don't say anything.

 
"Hey M@@@@@@@@@@RC !" :p]]> http://www.dslreports.com/forum/Re-Anticipation-27119024 Sat, 14 Apr 2012 22:43:18 EDT Re: Cogeco to START - Changeover Logistics http://www.dslreports.com/forum/Re-Cogeco-to-START-Changeover-Logistics-27119010 http://www.dslreports.com/forum/Re-Cogeco-to-START-Changeover-Logistics-27119010 Sat, 14 Apr 2012 22:35:52 EDT Re: Anticipation http://www.dslreports.com/forum/Re-Anticipation-27118826 said by Davesnothere:

said by Last Parade:

said by Davesnothere:

 
Is Last Parade up and running on START yet, with the fancy D3 Cisco beast ?

No, I can't wait for my 9 hour install window on the 18th though.

 
Ironic that the only one of us GOUGEco lemmings with a proper Kosher D3 modem has to endure latency in his INSTALL DATE ! :o

4 more Sleeps, then.... :)

I'm on TekSavvy at the moment. And they've forgotten to shut down the line. Don't say anything.]]> http://www.dslreports.com/forum/Re-Anticipation-27118826 Sat, 14 Apr 2012 21:29:29 EDT Re: Cogeco to START - Changeover Logistics http://www.dslreports.com/forum/Re-Cogeco-to-START-Changeover-Logistics-27118264 Try other stream sites, as may be just YT.

Speed Tests are anywhere from 7 to 12 Mb on various servers right now.

Pings R similar to our other recent tests.

Specific DLs ? - not done any today so far.]]> http://www.dslreports.com/forum/Re-Cogeco-to-START-Changeover-Logistics-27118264 Sat, 14 Apr 2012 17:10:12 EDT Re: Cogeco to START - Changeover Logistics http://www.dslreports.com/forum/Re-Cogeco-to-START-Changeover-Logistics-27118193
Just wondering if anyone else is getting slower d/ls right now.]]> http://www.dslreports.com/forum/Re-Cogeco-to-START-Changeover-Logistics-27118193 Sat, 14 Apr 2012 16:34:43 EDT Re: Cogeco to START - Changeover Logistics http://www.dslreports.com/forum/Re-Cogeco-to-START-Changeover-Logistics-27117945 said by spikernum1:

Quite awesome today. - Why would it be GRADE B?

 
One of my best with START was almost exactly as yours, at 2 AM today to Montreal, and was also judged that way.

I'm with Gone on that.]]> http://www.dslreports.com/forum/Re-Cogeco-to-START-Changeover-Logistics-27117945 Sat, 14 Apr 2012 14:54:27 EDT Anticipation http://www.dslreports.com/forum/Anticipation-27117882 said by Last Parade:

said by Davesnothere:

 
Is Last Parade up and running on START yet, with the fancy D3 Cisco beast ?

No, I can't wait for my 9 hour install window on the 18th though.

 
Ironic that the only one of us GOUGEco lemmings with a proper Kosher D3 modem has to endure latency in his INSTALL DATE ! :o

4 more Sleeps, then.... :)

--

We have only 2 things about which to worry :
(1) That things may never get back to normal
(2) That they already HAVE !
]]> http://www.dslreports.com/forum/Anticipation-27117882 Sat, 14 Apr 2012 14:31:01 EDT Re: Cogeco to START - Changeover Logistics http://www.dslreports.com/forum/Re-Cogeco-to-START-Changeover-Logistics-27117791 http://www.dslreports.com/forum/Re-Cogeco-to-START-Changeover-Logistics-27117791 Sat, 14 Apr 2012 13:42:24 EDT Re: Cogeco to START - Changeover Logistics http://www.dslreports.com/forum/Re-Cogeco-to-START-Changeover-Logistics-27117783 [att=1]

Why would it be GRADE B?
]]> http://www.dslreports.com/forum/Re-Cogeco-to-START-Changeover-Logistics-27117783 Sat, 14 Apr 2012 13:38:47 EDT Cogeco to Fibrenoire in Montreal http://www.dslreports.com/forum/Cogeco-to-Fibrenoire-in-Montreal-27117763 Tracing route to fibrenoire.net [208.84.104.2]
over a maximum of 30 hops:

1 - 1 ms 1 ms 1 ms 192.168.67.1
2 - 14 ms 8 ms 7 ms 10.71.128.1
3 - 20 ms 22 ms 19 ms d226-5-81.home.cgocable.net [24.226.5.81]
4 - 25 ms 20 ms 19 ms d226-6-130.home.cgocable.net [24.226.6.130]
5 - 18 ms 19 ms 20 ms bvi1.asr01.tor151f.fibrenoire.ca [206.108.34.141]
6 - 25 ms 25 ms 28 ms te4-3.crt01.mtlcx03.fibrenoire.ca [68.67.63.197]
7 - 26 ms 25 ms 25 ms gi1-19.core02.mtl-1250.fibrenoire.ca [208.88.108.226]
8 - 26 ms 25 ms 27 ms srv01.mtl-1250.fibrenoire.ca [208.84.104.2]

Trace complete.

Very similar peering.

One network transfer and done.]]> http://www.dslreports.com/forum/Cogeco-to-Fibrenoire-in-Montreal-27117763 Sat, 14 Apr 2012 13:28:01 EDT Cogeco to Nexicom in Toronto http://www.dslreports.com/forum/Cogeco-to-Nexicom-in-Toronto-27117746 Tracing route to nexicom.com [216.168.96.37]
over a maximum of 30 hops:

1 - 1 ms 1 ms 1 ms 192.168.67.1
2 - 7 ms 7 ms 7 ms 10.71.128.1
3 - 22 ms 19 ms 19 ms d226-5-81.home.cgocable.net [24.226.5.81]
4 - 18 ms 27 ms 19 ms d226-6-130.home.cgocable.net [24.226.6.130]
5 - 24 ms 17 ms 21 ms xe4-3-0-56.core1.toronto1.nexicom.net [206.108.34.66]
6 - 19 ms 19 ms 19 ms xe3-3-0.core2.toronto1.nexicom.net [98.124.50.241]
7 - 33 ms 20 ms 22 ms ge1-2-9.dis2.millbrook1.nexicom.net [98.124.46.162]
8 - 24 ms 22 ms 23 ms ge6-0-20.dis3.millbrook1.nexicom.net [98.124.50.2]
9 * * * Request timed out.
10 * * * Request timed out.
11 ^C

It's a quick hand-off to Nexicom, et VOILA !

Deux Points !]]> http://www.dslreports.com/forum/Cogeco-to-Nexicom-in-Toronto-27117746 Sat, 14 Apr 2012 13:22:04 EDT Re: Speed Tests, April 13th, Near Peak http://www.dslreports.com/forum/Re-Speed-Tests-April-13th-Near-Peak-27117717 Lurking then, I see.

So it's not that Montreal was that much better in my tests, it was the Toronto test that was out of range, and the other user noticed that too, when comparing Toronto to Michigan.

A-HAH !

And there sure were a lot of hops on the way to Nexicom from START ! :o]]> http://www.dslreports.com/forum/Re-Speed-Tests-April-13th-Near-Peak-27117717 Sat, 14 Apr 2012 13:10:58 EDT Re: Speed Tests, April 13th, Near Peak http://www.dslreports.com/forum/Re-Speed-Tests-April-13th-Near-Peak-27117715 said by Davesnothere:

Nexicom has not yet turned on peering to Start thru TorIX, but plans to soon, apparently.

I know, I read that when rocca said that. :p

If that speed test server needs to be routed through Cogent, that explains why the speed tests are out of whack relative to the actual performance, at least based on my own past experiences. Once they're talking to each other directly at Torix you'll see it improve drastically.]]> http://www.dslreports.com/forum/Re-Speed-Tests-April-13th-Near-Peak-27117715 Sat, 14 Apr 2012 13:08:17 EDT Re: Speed Tests, April 13th, Near Peak http://www.dslreports.com/forum/Re-Speed-Tests-April-13th-Near-Peak-27117696 said by Gone:

said by Davesnothere:

The Toronto test server responds just fine when I'm on my Cogeco account and modem - in fact the lowest ping of them all.
Did I miss something obvious ?

Yes. Cogeco has drastically different peering arrangements than Start. Cogeco doesn't peer at Torix, for example. Who knows what kind of route you're getting to get to that server, or what or what port you're using if it's multihomed. You're posting decent speed tests from other servers, so who the hell cares if but one server has lower performance than the other ones you're posting?

Seriously, when it comes to stuff like this there are so many variables that were this conversation in person it would be nothing more than an exercise in oxygen/CO2 exchange.

 
But I THRIVE on learning stuff, even at my advanced age. :) :) :)

The tests I have performed since you posted that last post have illustrated very well the differences in peering among the 2 test sites with START, and so just for kicks, before Cogeco unprovisions me, I'm going to repeat those 2 cities thru Cogeco account to see what peering that THEY use.

BTW, Peter posted something which explained why the Toronto test reads poorly.

Even though they both peer at TorIX, Nexicom has not yet turned on peering to Start thru TorIX, but plans to soon.]]> http://www.dslreports.com/forum/Re-Speed-Tests-April-13th-Near-Peak-27117696 Sat, 14 Apr 2012 13:02:24 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117688 said by rocca:

In any case, the new 20ms latency that popped up last week is being investigated but as everyone seems to be reporting good speeds and no impact, 20ms (we are talking milliseconds here, ie 1/50th of a second) really shouldn't affect day-to-day in the meantime.

Browsing and downloading, no.

Ask me the same thing when I'm trying to play Team Fortress, though. :p]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117688 Sat, 14 Apr 2012 13:00:40 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117648 said by rocca:

said by Davesnothere:

I don't think I'll find the 'Phantom Ping'

It's at hop 3.

 
Yes, but I meant the reason for it. :)

WHAT ? - Not gone yet ?

EDIT : I didn't mean 'Gone', just gone ;)]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117648 Sat, 14 Apr 2012 12:50:15 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117638 said by rocca:

....Moral of the story: the shortest physical distance between A and B is often not the most optimal route.

Hope that helps....

...and now I'm done for the day, hockey tournament. :)

 
Yep, I get it. :)

Have fun there, and BTW, you should offer that analogy to the hockey players regarding the PUCK and scoring. :p]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117638 Sat, 14 Apr 2012 12:47:56 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117634 said by Davesnothere:

But Hop 11 seems to be a consistent slowdown ?

That's a question for tinet. ;-)]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117634 Sat, 14 Apr 2012 12:47:18 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117630 said by Davesnothere:

I don't think I'll find the 'Phantom Ping'

It's at hop 3.]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117630 Sat, 14 Apr 2012 12:46:21 EDT Nexicom Retested http://www.dslreports.com/forum/Nexicom-Retested-27117622 Tracing route to nexicom.com [216.168.96.37]
over a maximum of 30 hops:

1 - 1 ms 1 ms 1 ms 192.168.67.1
2 - 9 ms 12 ms 7 ms 10.205.36.1
3 - 42 ms 43 ms 43 ms asr-link1-burlington1.net.start.ca [64.140.112.154]
4 43 ms 43 ms 44 ms core1-toronto1-te3-3.net.start.ca [64.140.112.153]
5 - 43 ms 43 ms 44 ms gi2-27.ccr01.yyz03.atlas.cogentco.com [38.122.70.81]
6 - 42 ms 42 ms 54 ms te7-5.mpd02.yyz02.atlas.cogentco.com [154.54.45.117]
7 - 47 ms 43 ms 44 ms te0-3-0-0.ccr22.yyz02.atlas.cogentco.com [154.54.40.165]
8 - 56 ms 53 ms 55 ms te0-3-0-6.ccr22.jfk02.atlas.cogentco.com [154.54.47.129]
9 - 59 ms 56 ms 56 ms te0-5-0-0.ccr21.jfk07.atlas.cogentco.com [154.54.80.178]
10 - 54 ms 57 ms 55 ms tiscali.jfk07.atlas.cogentco.com [154.54.10.90]
11 - 71 ms 74 ms 71 ms xe-4-3-0.tor10.ip4.tinet.net [89.149.184.110]
12 - 89 ms 75 ms 79 ms xe-4-2-0-101.core1.toronto1.nexicom.net [77.67.71.82]
13 - 77 ms 75 ms 75 ms dis1-rtr-mb-ge8-15-vl3.nexicom.net [76.75.120.81]
14 - 83 ms 80 ms 80 ms dis2-rtr-mb-ge9-5.nexicom.net [216.168.98.137]
15 - 76 ms 79 ms 78 ms ge6-0-23.dis3.millbrook1.nexicom.net [98.124.59.130]
16 * * * Request timed out.
17 * * * Request timed out.
18 * ^C

Hop 5 looks better now.

I guess it's just the sheer number of hops in the Cogent and other peerings to there.

They cannot ALL be invisible.]]> http://www.dslreports.com/forum/Nexicom-Retested-27117622 Sat, 14 Apr 2012 12:44:10 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117620 said by Davesnothere:

That's been told to me occasionally before, but it can be hard to take to heart sometimes.

I wouldn't lie to you. ;)

Here's a recent story from our rural wireless side. We have a customer about a 1/2 km from one of our towers and wants to upgrade their speed, but the path is poor (tree in the fresnel) and that path can't support higher speeds. So we setup a dedicated link from another tower about 5km away but has a different path. The customer is initially very concerned "How can a link 5km away be faster than the one a tenth of that distance" - valid 'gut' feel, but that's not the way networks work, particularly when packets are travelling at roughly the speed of light. The extra hop on the router adds about 0.5ms latency and the customer gets full speed.

Moral of the story: the shortest physical distance between A and B is often not the most optimal route.

Hope that helps....

...and now I'm done for the day, hockey tournament. :) ]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117620 Sat, 14 Apr 2012 12:43:40 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117589 said by rocca:

You have to remember that latency to a particular path includes _all_ the hops to that point, not just the latency _of_ that point.

So when you show hop 5 and say "that's odd", there are two reasons for seeing 101ms there....

 
Right, so I ought to repeat the test to rule out that sort of stuff.

But Hop 11 seems to be a consistent slowdown ?

BTW, did you re-read my last post ? - I revised it.]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117589 Sat, 14 Apr 2012 12:36:15 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117576
So when you show hop 5 and say "that's odd", there are two reasons for seeing 101ms there, a) your computer did something at that moment, ie a background update, a web page ad refreshed, your instant messenger got or checked for a message, your mailbox downloaded, etc. or b) that router doesn't prioritize packets to its control plane (ie routers are designed to pass packets, not respond to requests directly against the router - packets destined _to_ a router are called control plane packets, whereas packets destined _through_ a router are traffic planes and have _very_ different handling). So we continue along and you see hop 6 and a dropped packet and probably think "dropped packet, must be a problem there" ...however again the control plane on that router probably limits how many responses that target that router are processed. Continuing you see hop 7 and say "oh good, everything is normal from here" but you have to remember that getting to hop 7 means that exact packet that replied went through all the other hops (and back again) that you were concerned about.

In the end, traceroute is good for seeing where there is a problem if the end node is responding poorly, ie if you saw 100+ for _all_ the hops after 5, then you could conclude hop 5 was a problem, but the fact that the end point is quite fine, then therefore the entire path must be quite fine also despite what a control plane on a specific router in the middle of the path said.]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117576 Sat, 14 Apr 2012 12:33:18 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117570 said by rocca:

Also FYI, I expect you'll see the 'Toronto' speed test better shortly. It's hosted by Nexicom who is in TorIX but not peered with us yet, however they sent us a request last week so both sides are working on that currently - I expect it will be done next week.

The short version though to your questions today is that just because two things are in the same city doesn't mean they are necessarily directly connected. Ie the internet doesn't route via geography, rather it routes via available paths.

 
(our posts just crossed)

That's been told to me occasionally before, but it can be hard to take to heart sometimes.

Even in dialup days, we observed that RipNET in Brockville peered out to Chicago (for example) to access another Brockville ISP's website.

And what you just said about Nexicom explains a lot of that last tracert I did to them.

ARRRRGH - Just ONE MORE POST ! (I see you typing) :p]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117570 Sat, 14 Apr 2012 12:31:29 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117535 This test is also while on my START account :

tracert to the root domain of one provider of a test site

Nexicom in Toronto :

Tracing route to nexicom.com [216.168.96.37]
over a maximum of 30 hops:

1 - 1 ms 1 ms 1 ms 192.168.67.1
2 - 8 ms 11 ms 7 ms 10.205.36.1
3 - 45 ms 43 ms 47 ms 64.140.112.154
4 - 55 ms 43 ms 42 ms 64.140.112.153
5 - 101 ms 206 ms 208 ms gi2-27.ccr01.yyz03.atlas.cogentco.com [38.122.70.81]
6 - * 43 ms 42 ms te7-5.mpd02.yyz02.atlas.cogentco.com [154.54.45.117]
7 - 47 ms 43 ms 46 ms te0-3-0-0.ccr22.yyz02.atlas.cogentco.com [154.54.40.165]
8 - 54 ms 59 ms 56 ms te0-3-0-6.ccr22.jfk02.atlas.cogentco.com [154.54.47.129]
9 - 54 ms 58 ms 55 ms te0-5-0-0.ccr21.jfk07.atlas.cogentco.com [154.54.80.178]
10 - 54 ms 63 ms 57 ms tiscali.jfk07.atlas.cogentco.com [154.54.10.90]
11 - 71 ms 76 ms 71 ms xe-4-3-0.tor10.ip4.tinet.net [89.149.184.110]
12 - 76 ms 76 ms 77 ms xe-4-2-0-101.core1.toronto1.nexicom.net [77.67.71.82]
13 - 74 ms 79 ms 75 ms dis1-rtr-mb-ge8-15-vl3.nexicom.net [76.75.120.81]
14 - 81 ms 79 ms 80 ms dis2-rtr-mb-ge9-5.nexicom.net [216.168.98.137]
15 - 75 ms 76 ms 81 ms ge6-0-23.dis3.millbrook1.nexicom.net [98.124.59.
130]
16 * * * Request timed out.
....
30 * * * Request timed out.

Trace complete.

= = = = = = = =

Looks like something odd at hop 5 with Cogent peering provider, and also notable latency at hop 11 when Cogent hands it to Tinet ?

I plan to swap back to my Cogeco account and repeat the above 2 tracert tests, if the account is still provisioned.

I don't think I'll find the 'Phantom Ping', but have a feeling I might see some very different hops for when Cogeco hands data to alternate peers.]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117535 Sat, 14 Apr 2012 12:20:01 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117534
The short version though to your questions today is that just because two things are in the same city doesn't mean they are necessarily directly connected. Ie the internet doesn't route via geography, rather it routes via available paths.]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117534 Sat, 14 Apr 2012 12:19:49 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117511 http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117511 Sat, 14 Apr 2012 12:10:44 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117508 said by rocca:

said by Davesnothere:

So this would be an 3rd party app, where instead 'tracert' is part of Windoze ?

Any suggestions as to which app, and are any freeware ?

Correct. And no suggestions, I don't typically do packet sniffing on Windows machines. ;)

 
I may not need to, if my next test bears any fruit.

Please stand by....]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117508 Sat, 14 Apr 2012 12:08:51 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117505 said by Davesnothere:

said by rocca:

You could install a packet sniffer on your computer and see where the packets are going.

 
So this would be an 3rd party app, where instead 'tracert' is part of Windoze ?

Any suggestions as to which app, and are any freeware ?

Correct. And no suggestions, I don't typically do packet sniffing on Windows machines. ;) ]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117505 Sat, 14 Apr 2012 12:07:42 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117500 said by Davesnothere:

So Cogeco hands it to START at hop 3, and START peers it immediately (next) to someone who peers to FibreNoire ?

1 - 3 ms 1 ms 1 ms 192.168.67.1 <- YOU
2 - 8 ms 8 ms 20 ms 10.205.36.1 <- YOUR CMTS
3 - 43 ms 43 ms 43 ms 64.140.112.154 <- COGECO POI ROUTER IN BURLINGTON
4 - 48 ms 44 ms 42 ms 64.140.112.153 <- START ROUTER IN TORONTO
5 - 44 ms 44 ms 42 ms bvi1.asr01.tor151f.fibrenoire.ca [206.108.34.141] <- FIBERNOIRE ROUTER IN TORONTO

...ie we peer directly with them through TorIX.]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117500 Sat, 14 Apr 2012 12:06:28 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117494 said by rocca:

You could install a packet sniffer on your computer and see where the packets are going.

 
So this would be an 3rd party app, where instead 'tracert' is part of Windoze ?

Any suggestions as to which app, and are any freeware ?]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117494 Sat, 14 Apr 2012 12:04:26 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117488 said by rocca:

...shows that we're about 0ms away from fibernoires edge. After we hand it off to them it's up to their network...

 
ie immediately after hop 3 (which includes the 'PP')

So Cogeco hands it to START at hop 3, and START peers it immediately (next) to someone who peers to FibreNoire ?]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117488 Sat, 14 Apr 2012 12:01:53 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117479 said by Davesnothere:

4 - 48 ms 44 ms 42 ms 64.140.112.153
5 - 44 ms 44 ms 42 ms bvi1.asr01.tor151f.fibrenoire.ca

...shows that we're about 0ms away from fibernoires edge. After we hand it off to them it's up to their network...]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117479 Sat, 14 Apr 2012 11:58:10 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117475 said by Davesnothere:

 
So how would I find out the name or IP of the various speedtest.net servers, so to do ping trace routes for each ?
I will repeat this post periodically until someone offers a way, or tells me that there IS none.

You could install a packet sniffer on your computer and see where the packets are going.]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117475 Sat, 14 Apr 2012 11:56:39 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117474 OK, I tried this while on my START account :

tracert to the root domain of one provider of a test site

FibreNoire in Montreal :

Tracing route to fibrenoire.net [208.84.104.2]
over a maximum of 30 hops:

1 - 3 ms 1 ms 1 ms 192.168.67.1
2 - 8 ms 8 ms 20 ms 10.205.36.1
3 - 43 ms 43 ms 43 ms 64.140.112.154
4 - 48 ms 44 ms 42 ms 64.140.112.153
5 - 44 ms 44 ms 42 ms bvi1.asr01.tor151f.fibrenoire.ca [206.108.34.141]
6 - 51 ms 56 ms 50 ms te4-3.crt01.mtlcx03.fibrenoire.ca [68.67.63.197]
7 - 78 ms 50 ms 52 ms gi6-9.core02.mtl-1250.fibrenoire.ca [68.67.63.254]
8 - 51 ms 48 ms 49 ms srv01.mtl-1250.fibrenoire.ca [208.84.104.2]

Trace complete.]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117474 Sat, 14 Apr 2012 11:56:30 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117469
As Gone mentioned, there are multiple paths, different arrangements, even paths between two directly connected routers can take varying physical paths through different physical switches and even different physical paths between cities. There are too many variables for me to be able to say with any authority why one server sitting somewhere on the internet is giving better performance than some other server sitting somewhere else on the internet. I know nothing about their connectivity, their load, their paths, etc.

Speedtests are a good baseline for 'is my connection giving me the speed I've ordered' and if one of them says yes, then you know you're local connection has the correct speed. They are also good for if you're seeing poor performance surfing the web then you can use it as a quick check to see if you're generally having problems. However, if you repeatedly speedtest over and over and over using different sites you will undoubtedly find that sometimes you get different results - especially on cable. ;)

In any case, the new 20ms latency that popped up last week is being investigated but as everyone seems to be reporting good speeds and no impact, 20ms (we are talking milliseconds here, ie 1/50th of a second) really shouldn't affect day-to-day in the meantime.]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117469 Sat, 14 Apr 2012 11:54:09 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117458 So how would I find out the name or IP of the various speedtest.net servers, so to do ping trace routes for each ?

I will repeat this post periodically until someone offers a way, or tells me that there IS none.

I want to LEARN something from this, even if it turns out to be less important in the big scheme of things than I perceive it to be.

Thanks. :)]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117458 Sat, 14 Apr 2012 11:48:46 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117446 said by rocca:

....Also FYI, Cogeco's aggregation network terminates in Burlington, not Toronto.

 
Understood - Though I regarded Burlington as 'across town' from Toronto when I said that. :) :) :)

BUT, when closer geography from test sites to my ISP and Cogeco's AGG POI seem to affects my ping AND speed negatively, even in off-peak periods, I feel that it matters and is worthy of investigation.

However, we'll know better on the SPEED part after the D3 modems are happening, so I'll try to be patient. ;)

I just want to make sure that as much info is 'Out There' as possible, and these tests are an important part of it, IMNSHO.]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117446 Sat, 14 Apr 2012 11:43:54 EDT Re: HOW to Do It http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117425 said by Davesnothere:

 
The main question which comes to MY mind is why my PING on START is lowest to Montreal if my data has to first go to Toronto on Cogeco's AGG network, and then back to Montreal, but a Toronto test shows poorly and it's just 'across town' from wherever Cogeco peers, I would think.

Latency rarely has much to do with distance when distance is less than a few hundred miles.

Also FYI, Cogeco's aggregation network terminates in Burlington, not Toronto.]]> http://www.dslreports.com/forum/Re-HOW-to-Do-It-27117425 Sat, 14 Apr 2012 11:35:42 EDT Re: Speed Tests, April 13th, Near Peak http://www.dslreports.com/forum/Re-Speed-Tests-April-13th-Near-Peak-27117423 said by Davesnothere:

The Toronto test server responds just fine when I'm on my Cogeco account and modem - in fact the lowest ping of them all.
Did I miss something obvious ?

Yes. Cogeco has drastically different peering arrangements than Start. Cogeco doesn't peer at Torix, for example. Who knows what kind of route you're getting to get to that server, or what or what port you're using if it's multihomed. You're posting decent speed tests from other servers, so who the hell cares if but one server has lower performance than the other ones you're posting?

Seriously, when it comes to stuff like this there are so many variables that were this conversation in person it would be nothing more than an exercise in oxygen/CO2 exchange.]]> http://www.dslreports.com/forum/Re-Speed-Tests-April-13th-Near-Peak-27117423 Sat, 14 Apr 2012 11:35:01 EDT Re: Cogeco to START - Changeover Logistics http://www.dslreports.com/forum/Re-Cogeco-to-START-Changeover-Logistics-27117419 said by spikernum1:

michigan server:

 
Just for Kicks, here is my test for Mount Pleasant, Michigan (Winn Telecom server) (same city that you tried) :

Lower ping than Toronto, but higher than Montreal. ]]> http://www.dslreports.com/forum/Re-Cogeco-to-START-Changeover-Logistics-27117419 Sat, 14 Apr 2012 11:31:08 EDT 11 AM Tests - START account http://www.dslreports.com/forum/11-AM-Tests-START-account-27117381 START 16/1 account with D2 Modem :
[Tested from Eastern Ontario]

(However, my Cogeco account and D3 modem continue to test at full speed (30/2) on both of these servers, with PINGs of around 18 for Toronto and 26 for Montreal (FibreNoire server), and that observation remains true no matter what time of day.)

Toronto :



Montreal (FibreNoire server) :

]]> http://www.dslreports.com/forum/11-AM-Tests-START-account-27117381 Sat, 14 Apr 2012 11:09:54 EDT HOW to Do It http://www.dslreports.com/forum/HOW-to-Do-It-27117357 The main question which comes to MY mind is why my PING on START is lowest to Montreal if my data has to first go to Toronto on Cogeco's AGG network, and then back to Montreal, but a Toronto test shows poorly and it's just 'across town' from wherever Cogeco peers, I would think.

It must be taking a short cut to Montreal somehow, or a wrong turn in and around Toronto....

So how would I find out the name or IP of the various speedtest.net servers, so to do ping trace routes for each ?

I will repeat this post periodically until someone offers a way, or tells me that there IS none.

Thanks. :)]]> http://www.dslreports.com/forum/HOW-to-Do-It-27117357 Sat, 14 Apr 2012 11:00:47 EDT