Site Speed - tracert

[jimnyc]

Who knows how to do a tracert from their computer to this site, and also knows how to copy/past the results? I'm seeing slowness, and poor numbers at the last hop for the last hours.

1 - Go to START and then RUN and type in "CMD" without the quotes
2 - This will open the command prompt, black screen
3 - At this prompt, type in "tracert www.debatepolicy.com
4 - This will ping every hop on your route to the website and give back results similar to what I am posting below

How to copy and paste here

5 - Right click anywhere on the top bar, choose EDIT and then MARK
6 - Now you can right-click and highlight all the text on the screen - and leave it highlighted
7 - Now go to the top bar again, right click - EDIT and then this time choose COPY

Now you can past here as such: (The asterisks on the last 3 being where I think the issue is...)

5 16 ms 11 ms 16 ms 65.19.121.41
6 10 ms 11 ms 10 ms 64.15.2.198
7 * * * Request timed out.
8 13 ms 21 ms 11 ms te0-6-0-0.mpd21.jfk02.atlas.cogentco.com [154.54
.0.153]
9 19 ms 16 ms 18 ms te0-1-0-3.mpd21.dca01.atlas.cogentco.com [154.54
.3.45]
10 28 ms 29 ms 29 ms te0-0-0-3.mpd22.atl01.atlas.cogentco.com [154.54
.28.210]
11 45 ms 44 ms 43 ms te0-3-0-2.ccr22.iah01.atlas.cogentco.com [66.28.
4.90]
12 47 ms 46 ms 48 ms te0-3-0-2.ccr22.dfw01.atlas.cogentco.com [154.54
.0.202]
13 47 ms 48 ms 46 ms te4-8.ccr02.dfw06.atlas.cogentco.com [66.28.4.16
6]
14 46 ms 47 ms 47 ms 38.122.58.34
15 53 ms * 57 ms dal1-core1.unisonplatform.com [207.210.229.150]

16 53 ms * * green.unisonplatform.com [69.194.234.59]
17 54 ms * 53 ms green.unisonplatform.com [69.194.234.59]

Trace complete.

C:\Users\Jim>

[jafar00]

I'm in France at the moment so....

C:\Users\Jafar>tracert www.debatepolicy.com


Tracing route to debatepolicy.com [69.194.234.59]
over a maximum of 30 hops:


1 1 ms <1 ms <1 ms bbox.lan [192.168.1.254]
2 45 ms 43 ms 37 ms bty91-h01-31-33-140-254.dsl.sta.abo.bbox.fr [31
33.140.254]
3 36 ms 36 ms 36 ms v136.cor1.club-internet.fr [212.194.42.225]
4 89 ms 37 ms 37 ms ae24.tcore01-m.net.bbox.fr [62.35.255.174]
5 39 ms 38 ms 39 ms po101.core04-t2.net.bbox.fr [89.89.102.38]
6 38 ms 37 ms 142 ms v210.tengec1-20g.core03-t2.club-internet.fr [62
34.0.165]
7 81 ms 107 ms 108 ms ae8.tcore02-t2.net.bbox.fr [89.89.101.77]
8 * * * Request timed out.
9 37 ms 37 ms 37 ms root.franceix.net [193.105.232.66]
10 47 ms 49 ms 46 ms xe-1-1-0.r1.lon.iptransit.com [199.59.206.109]
11 120 ms 121 ms 122 ms xe-0-1-1.r1.ny.us.iptransit.com [204.26.60.210]


12 159 ms 157 ms 156 ms te8-8.r3.dal.us.iptransit.com [204.26.60.62]
13 158 ms 157 ms 156 ms te3-3.r1.dal.us.iptransit.com [204.26.61.1]
14 153 ms 151 ms 152 ms 204.26.63.166
15 155 ms 193 ms 164 ms dal1-core1.unisonplatform.com [207.210.229.150]


16 152 ms 151 ms 152 ms green.unisonplatform.com [69.194.234.59]


Trace complete.

[tailfins]

Connecticut

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

H:\>tracert www.debatepolicy.com (http://www.debatepolicy.com)

Tracing route to debatepolicy.com [69.194.***.59]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms brs-383-d-as-mdn-vl2021.corp.****.pvt
2 <1 ms 1 ms 25 ms brs-383-a-ds-mdn-vl2015.corp.****.pvt
3 <1 ms <1 ms 2 ms brs-ba-dc-cs-mdn-vl2140.corp.****.pvt
4 <1 ms 2 ms <1 ms brs-383-dc-cs-mdn-vl2024.corp.****.pvt
5 1 ms 1 ms <1 ms brs-383-dc-cs-vl1072.corp.****.pvt
6 2 ms <1 ms <1 ms brs-b5-dc-cs-vl756.corp.****.pvt
7 2 ms 1 ms 1 ms 172.22.0.1
8 1 ms 1 ms 1 ms 172.22.0.22
9 1 ms 1 ms 1 ms 172.17.0.241
10 1 ms 1 ms 1 ms 172.22.215.35
11 1 ms 1 ms 1 ms 192.234.2.3
12 4 ms 4 ms 4 ms te-4-4.car2.stamford1.level3.net [4.26.50.217]
13 47 ms 47 ms 47 ms ae-5-5.ebr2.newyork2.level3.net [4.69.142.82]
14 52 ms 53 ms 52 ms ae-1-100.ebr1.newyork2.level3.net [4.69.135.253]

15 45 ms 45 ms 45 ms ae-3-3.ebr2.washington1.level3.net [4.69.132.89]

16 45 ms 45 ms 45 ms ae-62-62.csw1.washington1.level3.net [4.69.134.1
46]
17 47 ms 47 ms 72 ms ae-61-61.ebr1.washington1.level3.net [4.69.134.1
29]
18 45 ms 45 ms 45 ms ae-2-2.ebr3.atlanta2.level3.net [4.69.132.85]
19 45 ms 45 ms 45 ms ae-7-7.ebr3.dallas1.level3.net [4.69.134.21]
20 45 ms 45 ms 45 ms ae-83-83.csw3.dallas1.level3.net [4.69.151.157]

21 52 ms 52 ms 52 ms ae-32-80.car2.dallas1.level3.net [4.69.145.132]

22 47 ms 47 ms 47 ms colo4-dalla.car2.dallas1.level3.net [4.79.182.23
8]
23 47 ms 47 ms 46 ms dal1-core1.unisonplatform.com [207.210.229.150]

24 46 ms 46 ms 46 ms green.unisonplatform.com [69.194.234.59]

Trace complete.

H:\>

[Robert A Whit]

California

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.


D:\Documents and Settings\Bob>tracert www.debatepolicy.com


Tracing route to debatepolicy.com [69.194.234.59]
over a maximum of 30 hops:


1 * * * Request timed out.
2 8 ms 9 ms 9 ms ge-1-4-ur01.fremontcev1.ca.sfba.comcast.net [68.
85.216.217]
3 8 ms 14 ms 9 ms te-9-3-ur01.fremont.ca.sfba.comcast.net [68.87.1
92.65]
4 14 ms 15 ms 11 ms te-1-8-0-4-ar01.sfsutro.ca.sfba.comcast.net [68.
86.143.86]
5 21 ms 23 ms 23 ms he-1-7-0-0-cr01.sanjose.ca.ibone.comcast.net [68
.86.90.153]
6 15 ms 14 ms 13 ms 4.71.118.37
7 54 ms 53 ms 53 ms vlan60.csw1.SanJose1.Level3.net [4.69.152.62]
8 53 ms 52 ms 53 ms ae-62-62.ebr2.SanJose1.Level3.net [4.69.153.17]


9 54 ms 52 ms 52 ms ae-2-2.ebr2.SanJose5.Level3.net [4.69.148.141]
10 54 ms 54 ms 52 ms ae-6-6.ebr2.LosAngeles1.Level3.net [4.69.148.201
]
11 52 ms 52 ms 52 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
12 52 ms 52 ms 52 ms ae-63-63.csw1.Dallas1.Level3.net [4.69.151.133]


13 94 ms 147 ms 56 ms ae-12-60.car2.Dallas1.Level3.net [4.69.145.4]
14 54 ms 167 ms 54 ms COLO4-DALLA.car2.Dallas1.Level3.net [4.79.182.23
8]
15 54 ms 59 ms 53 ms dal1-core1.unisonplatform.com [207.210.229.150]


16 53 ms 54 ms 52 ms green.unisonplatform.com [69.194.234.59]


Trace complete.

[jimnyc]

Those traces aren't showing packet loss. Mine is, but not right now either, it comes and goes.

Is anyone experiencing severe slowness like I am? In other words, much different than normal?

[jimnyc]

Took me about 1 minute to submit the above post, once I hit the submit button to where it refreshed and my post was live. I then wrote a PM to someone, and when hitting submit it also took a minute or so to finish.

[jimnyc]

Took me about 1 minute to submit the above post, once I hit the submit button to where it refreshed and my post was live. I then wrote a PM to someone, and when hitting submit it also took a minute or so to finish.

^^ And this one took about 1 second.

[jimnyc]

Just after my above post, the site speeds seem to have returned to normal for me, a dramatic improvement. It's back to normal, where pretty much anything I click on takes 1-2 seconds to load at best.

[Robert A Whit]

After the trace, it seemed to me to suddenly be slower. At times it seems to refresh fairly fast but other times slower. i also notice at times that my letters show up slower than i am typing.

In this piece, part of it typed slower and now it seems to be matching typing speeds to what shows up.

Now I will hit submit and see if it posts fast or slower than normal.

I counted 1000 &1, 1000 &2 and suddenly it showed up.

The edit showed up instantly.

[Trinity]

Ohio

Tracing route to debatepolicy.com [69.194.234.59]
over a maximum of 30 hops:

1 3 ms 2 ms 2 ms 192.168.1.1
2 18 ms 10 ms 12 ms cpe-65-27-180-1.cinci.res.rr.com [65.27.180.1]
3 15 ms 15 ms 22 ms ae0-1110.cr02.dytnoh55.swo.rr.com [65.25.147.137
]
4 28 ms 23 ms 31 ms network-065-029-001-046.midwest.rr.com [65.29.1.
46]
5 * 320 ms 30 ms ae-3-0.cr0.dca20.tbone.rr.com [66.109.6.70]
6 33 ms 26 ms 31 ms ae-1-0.pr0.dca10.tbone.rr.com [66.109.6.165]
7 31 ms 28 ms 30 ms te0-7-0-11.mpd22.iad02.atlas.cogentco.com [154.5
4.10.209]
8 37 ms * 148 ms te0-1-0-5.mpd22.dca01.atlas.cogentco.com [154.54
.26.121]
9 114 ms 45 ms 49 ms te0-2-0-3.mpd22.atl01.atlas.cogentco.com [154.54
.2.101]
10 336 ms 92 ms 98 ms te0-3-0-2.mpd22.iah01.atlas.cogentco.com [154.54
.2.246]
11 96 ms * 96 ms te0-0-0-1.ccr22.dfw01.atlas.cogentco.com [154.54
.25.221]
12 * * 128 ms te7-4.ccr02.dfw06.atlas.cogentco.com [154.54.0.1
22]
13 150 ms * 209 ms 38.122.58.34
14 * * 132 ms dal1-core1.unisonplatform.com [207.210.229.150]

15 * 121 ms * green.unisonplatform.com [69.194.234.59]
16 * * 127 ms green.unisonplatform.com [69.194.234.59]

Trace complete.

[gabosaurus]

Huntington Beach, California



C:\Users\Gabriella>tracert www.debatepolicy.com

Tracing route to debatepolicy.com [69.194.234.59]
over a maximum of 30 hops:

1 35 ms 34 ms 31 ms
2 34 ms 37 ms 29 ms
3 48 ms 38 ms 38 ms
4 44 ms 38 ms 39 ms
5 40 ms 30 ms 40 ms
6 52 ms 36 ms 47 ms
7 45 ms 46 ms 39 ms
8 49 ms 39 ms 38 ms
9 54 ms 57 ms 50 ms
10 59 ms 40 ms *

11 36 ms 39 ms 39 ms
12 45 ms 44 ms 52 ms
13 48 ms 40 ms 37 ms
Trace complete.

[Anton Chigurh]

Here's 30+ checks from 30+ places around the world, simultaneously.

http://host-tracker.com/check_res_ajx/12417458-0/

You can run this test any time, gives you a really good picture of how you're loading all over.

[jafar00]

I haven't had any problems here Jim. Maybe because I am not on the sub par internet we have in Australia ;)

[jimnyc]

This was about a 2 hour issue yesterday and was resolved. The webhost provider stated they were experiencing "huge packet loss on the datacenter side". But at least a lot of you know how to do a tracert now! :)

[NightTrain]

I noticed it was very slow this morning... here's mine from Alaska.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.


C:\Users\NT>tracert www.debatepolicy.com


Tracing route to debatepolicy.com [69.194.234.59]
over a maximum of 30 hops:


1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 8 ms 9 ms 9 ms 173-182-165-209.static.gci.net [209.165.182.173


4 10 ms 39 ms 9 ms 238-63-74-65.static.gci.net [65.74.63.238]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 42 ms 42 ms 58 ms 145-129-165-209.gci.net [209.165.129.145]
10 42 ms 42 ms 43 ms InetSeaSDCsw-2.gci.net [209.165.129.94]
11 42 ms 42 ms 43 ms xe-8-1-3.edge1.Seattle3.Level3.net [4.71.152.17
]
12 81 ms 83 ms 81 ms ae-32-52.ebr2.Seattle1.Level3.net [4.69.147.182


13 83 ms 88 ms 82 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]
14 84 ms 83 ms 83 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]


15 83 ms 83 ms 84 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]
16 * * * Request timed out.
17 105 ms 120 ms 87 ms ae-22-70.car2.Dallas1.Level3.net [4.69.145.68]
18 276 ms 212 ms 207 ms COLO4-DALLA.car2.Dallas1.Level3.net [4.79.182.2
8]
19 84 ms 83 ms 88 ms dal1-core1.unisonplatform.com [207.210.229.150]


20 82 ms 83 ms 83 ms green.unisonplatform.com [69.194.234.59]


Trace complete.


C:\Users\NT>

[jimnyc]

I noticed it was very slow this morning... here's mine from Alaska.


13 83 ms 88 ms 82 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]
14 84 ms 83 ms 83 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]


15 83 ms 83 ms 84 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]
16 * * * Request timed out.
17 105 ms 120 ms 87 ms ae-22-70.car2.Dallas1.Level3.net [4.69.145.68]
18 276 ms 212 ms 207 ms COLO4-DALLA.car2.Dallas1.Level3.net [4.79.182.2
8]
19 84 ms 83 ms 88 ms dal1-core1.unisonplatform.com [207.210.229.150]


20 82 ms 83 ms 83 ms green.unisonplatform.com [69.194.234.59]


Trace complete.


C:\Users\NT>

I would say that the bold portion is about where your bottleneck is today, which appears to be the last router before you hit the datacenter. Notice how the ping times even reduce dramatically after you reach the datacenter.

Good to seeya, Rick! :salute:

[Robert A Whit]

D:\Documents and Settings\Bob>tracert debatepolicy.com

Tracing route to debatepolicy.com [69.194.234.59]
over a maximum of 30 hops:

1 * * * Request timed out.
2 8 ms 9 ms 9 ms ge-1-4-ur01.fremontcev1.ca.sfba.comcast.net [68.
85.216.217]
3 9 ms 9 ms 9 ms te-9-3-ur01.fremont.ca.sfba.comcast.net [68.87.1
92.65]
4 16 ms 13 ms 11 ms te-1-8-0-4-ar01.sfsutro.ca.sfba.comcast.net [68.
86.143.86]
5 15 ms 23 ms 23 ms he-1-7-0-0-cr01.sanjose.ca.ibone.comcast.net [68
.86.90.153]
6 13 ms 14 ms 40 ms 4.71.118.37
7 52 ms 52 ms 52 ms vlan60.csw1.SanJose1.Level3.net [4.69.152.62]
8 54 ms 56 ms 53 ms ae-62-62.ebr2.SanJose1.Level3.net [4.69.153.17]

9 52 ms 56 ms 54 ms ae-2-2.ebr2.SanJose5.Level3.net [4.69.148.141]
10 53 ms 52 ms 53 ms ae-6-6.ebr2.LosAngeles1.Level3.net [4.69.148.201
]
11 53 ms 54 ms 52 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
12 54 ms 52 ms 52 ms ae-63-63.csw1.Dallas1.Level3.net [4.69.151.133]

13 187 ms 83 ms 93 ms ae-12-60.car2.Dallas1.Level3.net [4.69.145.4]
14 53 ms 54 ms 55 ms COLO4-DALLA.car2.Dallas1.Level3.net [4.79.182.23
8]
15 54 ms 54 ms 60 ms dal1-core1.unisonplatform.com [207.210.229.150]

16 54 ms 54 ms 55 ms green.unisonplatform.com [69.194.234.59]

Trace complete.

D:\Documents and Settings\Bob>^A

[aboutime]

This was about a 2 hour issue yesterday and was resolved. The webhost provider stated they were experiencing "huge packet loss on the datacenter side". But at least a lot of you know how to do a tracert now! :)


Jim. Not having any problems here. But you should be aware of sunspot activity increasing.

Though not many people take it seriously. I can assure everyone who uses a cell phone, the Internet, or high tech accessories these days. That sunspot activity Really Does play a huge part in the visual, and invisible spectrum of electronics, magnetism, and even satellite communications worldwide.
Next time you experience a long delay, or blackout. Remember. The SUN..not George W. Bush is responsible, and to blame.

[NightTrain]

Jim. Not having any problems here. But you should be aware of sunspot activity increasing.

Though not many people take it seriously. I can assure everyone who uses a cell phone, the Internet, or high tech accessories these days. That sunspot activity Really Does play a huge part in the visual, and invisible spectrum of electronics, magnetism, and even satellite communications worldwide.
Next time you experience a long delay, or blackout. Remember. The SUN..not George W. Bush is responsible, and to blame.

That's a myth - unless you're using a satellite connection, and then it would be minimal and rather rare.

I will admit to perpetuating this for a chuckle with an unsuspecting person, and I even had a smartass tech tell me it was solar activity when I called in to my ISP to complain about my internet speed. I told him I just installed & integrated his company's new cell phone network to shut him up, then told him, "I want you to look at my port and tell me what I'm set at." I heard some fast keyboard activity in the background, my modem reset, and BAM! Right back to 22 meg.

Turns out that my 'Solar Activity' was actually the usual ISP choking to save a buck... I think they all do it, and I keep mine on their toes with SpeedTest.net checkups. I want what I pay for.

The vast majority of internet traffic is carried through Fiber and Copper... it's cheaper, faster and more reliable than bouncing off satellites. Fiber is immune, of course, and the copper legs are very short.

Whenever you hear someone at your ISP explain slow internet speed with 'Solar Activity', it's a safe bet to tell them to shut the hell up, get off their ass and fix the problem.

[NightTrain]

I would say that the bold portion is about where your bottleneck is today, which appears to be the last router before you hit the datacenter. Notice how the ping times even reduce dramatically after you reach the datacenter.

Good to seeya, Rick! :salute:

Yep, it was definitely in the Dallas area... probably some maintenance going on down there at the CO.

I had some timeouts before reaching that hop, so there was something else going on in Anchorage and in Seattle, too.

Thanks, glad to be back!

[aboutime]

That's a myth - unless you're using a satellite connection, and then it would be minimal and rather rare.

I will admit to perpetuating this for a chuckle with an unsuspecting person, and I even had a smartass tech tell me it was solar activity when I called in to my ISP to complain about my internet speed. I told him I just installed & integrated his company's new cell phone network to shut him up, then told him, "I want you to look at my port and tell me what I'm set at." I heard some fast keyboard activity in the background, my modem reset, and BAM! Right back to 22 meg.

Turns out that my 'Solar Activity' was actually the usual ISP choking to save a buck... I think they all do it, and I keep mine on their toes with SpeedTest.net checkups. I want what I pay for.

The vast majority of internet traffic is carried through Fiber and Copper... it's cheaper, faster and more reliable than bouncing off satellites. Fiber is immune, of course, and the copper legs are very short.

Whenever you hear someone at your ISP explain slow internet speed with 'Solar Activity', it's a safe bet to tell them to shut the hell up, get off their ass and fix the problem.


Whatever you say. Guess all my time working satellite communications in the navy was invalid.

[NightTrain]

Whatever you say. Guess all my time working satellite communications in the navy was invalid.


I did say it can affect Satellite communications to an extent.

But it's not going to affect any internet traffic on the grid and it's a running joke in the trade.

[jimnyc]

I did say it can affect Satellite communications to an extent.

But it's not going to affect any internet traffic on the grid and it's a running joke in the trade.

Of course not, the man who invented the internet, put in a back door to slow things down if he wanted to, it's called "global warming". :coffee:

[NightTrain]

Of course not, the man who invented the internet, put in a back door to slow things down if he wanted to, it's called "global warming". :coffee:


I still chuckle about Al Gore "taking the initiative to create the internet".

Good times, Algore, good times.

I hope he doesn't sell the Interwebs to Al Jazeera. Then we'll be stuck with porn like this :

4687