P
PapaJohn \(MVP\)
Jim,
Let me know what you find. Maybe it'll help others.
PapaJohn
Let me know what you find. Maybe it'll help others.
PapaJohn
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
?
=?iso-8859-1?Q?G=FCnter_Mangold?=
John, i receive www.papajohn.org again in full glory ;-)
included a functioning navigation window.
Regards, Günter
included a functioning navigation window.
Regards, Günter
P
PapaJohn \(MVP\)
Thanks Gunter,
So some things just heal themselves. I like that!!
PapaJohn
So some things just heal themselves. I like that!!
PapaJohn
J
John Kelly
Hi there,
Yes, well a tracert is the de-facto standard for ISP's to determine if
further investigation is necessary.
BT, TeleWest and NTL which includes several other names Chello, ATT and Cox
will not process a user's complaint of poor connectivity if the user does
not include a Tracert to the site involved. It is their way of saying yes
the problem is within our domain or someone else's, and as is often the case
if you are outside the domain where there is a problem, it can often take
more effort than its worth getting the domain owners to do anything about
it...but thats life...or at least thats Internet
Yes, well a tracert is the de-facto standard for ISP's to determine if
further investigation is necessary.
BT, TeleWest and NTL which includes several other names Chello, ATT and Cox
will not process a user's complaint of poor connectivity if the user does
not include a Tracert to the site involved. It is their way of saying yes
the problem is within our domain or someone else's, and as is often the case
if you are outside the domain where there is a problem, it can often take
more effort than its worth getting the domain owners to do anything about
it...but thats life...or at least thats Internet
S
Steve Holt
B
Big Jim
Hello All:
I'm still dead when trying to get the www.papajohn.org
website. I can however load it fine from work. Stange
huh?
Here are my trace route results which I have reported to
my ISP:
Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.
C:\DOCUME~1\BIGJIM~1>tracert www.papajohn.org
Tracing route to www.papajohn.org [216.40.33.117]
over a maximum of 30 hops:
1 33 ms 32 ms 38 ms dsl-049.catisle.net
[192.216.113.49]
2 44 ms 54 ms 45 ms s3-1-2-0.lsanca1-
cr1.bbnplanet.net [4.24.24.45]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
C:\DOCUME~1\BIGJIM~1>
I'm still dead when trying to get the www.papajohn.org
website. I can however load it fine from work. Stange
huh?
Here are my trace route results which I have reported to
my ISP:
Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.
C:\DOCUME~1\BIGJIM~1>tracert www.papajohn.org
Tracing route to www.papajohn.org [216.40.33.117]
over a maximum of 30 hops:
1 33 ms 32 ms 38 ms dsl-049.catisle.net
[192.216.113.49]
2 44 ms 54 ms 45 ms s3-1-2-0.lsanca1-
cr1.bbnplanet.net [4.24.24.45]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
C:\DOCUME~1\BIGJIM~1>
www.papajohn.org when finished-----Original Message-----
Hi PapaJohn,
At this time 7am EST I can see your website. If others at this time cannot
It indicates a failure in the infra structure between your site and them
and will almost certainly be under repair. It would be a good idea all the
same, for those people who cannot see your page to do the following
1) open a DOS box (Command) and type TRACERT
sm.blueyonder.co.uk [62.30.193.129]copy all of the text
2) Contact their own ISP stating can not reach etc and include the text from
step one above
Below is the result of a trace to your site from me...
Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.
tracert www.papajohn.org
Tracing route to www.papajohn.org [216.40.33.117]
over a maximum of 30 hops:
1 9 ms 8 ms 8 ms 10.63.0.1
2 8 ms 7 ms 8 ms gsr01-
pos.telewest.net [194.117.136.22]3 15 ms 17 ms 14 ms 172.18.14.58
4 16 ms 15 ms 14 ms brad-wit-
0.sprintlink.net [160.81.109.194]5 16 ms 16 ms 16 ms 194.117.136.162
6 21 ms 19 ms 19 ms 195.50.91.5
7 19 ms 19 ms 22 ms gige1- 1.core2.London1.Level3.net
[212.187.131.13
4]
8 15 ms 15 ms 16 ms sl-bb21-lon-6- 0.sprintlink.net
[213.206.131.21]
9 20 ms 19 ms 21 ms sl-bb20-lon-15- 0.sprintlink.net
[213.206.128.37]
10 20 ms 21 ms 21 ms sl-bb22-lon-14- 0.sprintlink.net
[213.206.128.53]
11 87 ms 87 ms 90 ms sl-bb20-nyc-2- 0.sprintlink.net
[144.232.9.163]
12 89 ms 88 ms 86 ms sl-bb22-nyc-8- 0.sprintlink.net
[144.232.7.106]
13 108 ms 110 ms 109 ms sl-bb21-chi-9- 0.sprintlink.net
[144.232.9.149]
14 114 ms 114 ms 117 ms sl-bb20-chi-14- 0.sprintlink.net
[144.232.26.1]
15 112 ms 109 ms 110 ms sl-gw36-chi-14- 0.sprintlink.net
[144.232.26.70]
16 113 ms 114 ms 115 ms sl-teleg-3-
17 110 ms 108 ms 110 ms 206.108.103.137
18 119 ms 121 ms 120 ms 206.108.103.133
19 120 ms 120 ms 120 ms 64.230.242.198
20 120 ms 122 ms 119 ms 206.108.97.70
21 126 ms 126 ms 126 ms 206.108.111.106
22 * * * Request timed out.
23 * * * Request timed out.
24 124 ms 124 ms 127 ms 129.33.183.72
25 * * * Request timed out.
26 * * * Request timed out.
27 130 ms 127 ms 128 ms radware-osrs1.tucows.com [216.40.33.70]
28 126 ms 125 ms 127 ms ddwww.tucows.com [216.40.33.117]
Trace complete.
You will see that hops 22, 23, 25 and 26 have no values...thats because that
server has refused the info...that is not a fault...but if you got Request
Timed out all the way to the end...that is a fault. As I am on broadband I
would have expected quite a few of the above values to be higher than they
are, but even so...its not to bad
J
John Kelly
Hi there,
There is nothing all that strange about being able to get any website from
one location and not another...simply from the one where you cannot get
it...If you image you are at some point on a spiders web that has not been
completed you are at a location where there is no route to the target web
site. Your ISP will advise on what you need to do.
You may want to try disableing your firewall (for the shortest period
possible) and try again. If it works then one of the critical mid route
address's has been blocked. Comparing two tracerts will then give you the
all important clue as to which one it is. I expect your ISP has already
told you that.
There is nothing all that strange about being able to get any website from
one location and not another...simply from the one where you cannot get
it...If you image you are at some point on a spiders web that has not been
completed you are at a location where there is no route to the target web
site. Your ISP will advise on what you need to do.
You may want to try disableing your firewall (for the shortest period
possible) and try again. If it works then one of the critical mid route
address's has been blocked. Comparing two tracerts will then give you the
all important clue as to which one it is. I expect your ISP has already
told you that.
J
Jake
Hi
It looks like the peering between your ISPs transit provider and Papa John's
Web site host's transit provider is dead.
Looking at my own route trace it looks like Papa John's transit provider is
Allstream, which was formerly AT&T Canada. Your ISPs transit provider is
Genuity. Both of these companies are very large with very complex networks
and peering arrangements so it's surprising that there's a dead route there
(I would have thought that two providers of that size would peer in several
different places so there'd be at least *two* routes, if not more).
The problem would appear to be between Allstream and Genuity. Hope your ISP
is able to kick some butt and get the problem sorted out!
Incidentally, a timeout with ping or tracert doesn't necessarily mean that
you won't be able to access a Web page on a particular host as it's not
uncommon for an ISP to firewall ICMP traffic (includes ping and traceroute)
but allow Web traffic - you'd normally see this at the end of the route
though, rarely at the start.
As a matter of interest, can you access www.tucows.com? This would appear
to be on the same network as www.papajohn.org, so if you can't reach Tucows
either then this gives you further evidence of a problem between Allstream
and Genuity.
Jake
It looks like the peering between your ISPs transit provider and Papa John's
Web site host's transit provider is dead.
Looking at my own route trace it looks like Papa John's transit provider is
Allstream, which was formerly AT&T Canada. Your ISPs transit provider is
Genuity. Both of these companies are very large with very complex networks
and peering arrangements so it's surprising that there's a dead route there
(I would have thought that two providers of that size would peer in several
different places so there'd be at least *two* routes, if not more).
The problem would appear to be between Allstream and Genuity. Hope your ISP
is able to kick some butt and get the problem sorted out!
Incidentally, a timeout with ping or tracert doesn't necessarily mean that
you won't be able to access a Web page on a particular host as it's not
uncommon for an ISP to firewall ICMP traffic (includes ping and traceroute)
but allow Web traffic - you'd normally see this at the end of the route
though, rarely at the start.
As a matter of interest, can you access www.tucows.com? This would appear
to be on the same network as www.papajohn.org, so if you can't reach Tucows
either then this gives you further evidence of a problem between Allstream
and Genuity.
Jake
Big Jim said:Hello All:
I'm still dead when trying to get the www.papajohn.org
website. I can however load it fine from work. Stange
huh?
Here are my trace route results which I have reported to
my ISP:
Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.
C:\DOCUME~1\BIGJIM~1>tracert www.papajohn.org
Tracing route to www.papajohn.org [216.40.33.117]
over a maximum of 30 hops:
1 33 ms 32 ms 38 ms dsl-049.catisle.net
[192.216.113.49]
2 44 ms 54 ms 45 ms s3-1-2-0.lsanca1-
cr1.bbnplanet.net [4.24.24.45]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
C:\DOCUME~1\BIGJIM~1>
www.papajohn.org when finished-----Original Message-----
Hi PapaJohn,
At this time 7am EST I can see your website. If others at this time cannot
It indicates a failure in the infra structure between your site and them
and will almost certainly be under repair. It would be a good idea all the
same, for those people who cannot see your page to do the following
1) open a DOS box (Command) and type TRACERTsm.blueyonder.co.uk [62.30.193.129]copy all of the text
2) Contact their own ISP stating can not reach etc and include the text from
step one above
Below is the result of a trace to your site from me...
Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.
tracert www.papajohn.org
Tracing route to www.papajohn.org [216.40.33.117]
over a maximum of 30 hops:
1 9 ms 8 ms 8 ms 10.63.0.1
2 8 ms 7 ms 8 ms gsr01-pos.telewest.net [194.117.136.22]3 15 ms 17 ms 14 ms 172.18.14.58
4 16 ms 15 ms 14 ms brad-wit-0.sprintlink.net [160.81.109.194]5 16 ms 16 ms 16 ms 194.117.136.162
6 21 ms 19 ms 19 ms 195.50.91.5
7 19 ms 19 ms 22 ms gige1- 1.core2.London1.Level3.net
[212.187.131.13
4]
8 15 ms 15 ms 16 ms sl-bb21-lon-6- 0.sprintlink.net
[213.206.131.21]
9 20 ms 19 ms 21 ms sl-bb20-lon-15- 0.sprintlink.net
[213.206.128.37]
10 20 ms 21 ms 21 ms sl-bb22-lon-14- 0.sprintlink.net
[213.206.128.53]
11 87 ms 87 ms 90 ms sl-bb20-nyc-2- 0.sprintlink.net
[144.232.9.163]
12 89 ms 88 ms 86 ms sl-bb22-nyc-8- 0.sprintlink.net
[144.232.7.106]
13 108 ms 110 ms 109 ms sl-bb21-chi-9- 0.sprintlink.net
[144.232.9.149]
14 114 ms 114 ms 117 ms sl-bb20-chi-14- 0.sprintlink.net
[144.232.26.1]
15 112 ms 109 ms 110 ms sl-gw36-chi-14- 0.sprintlink.net
[144.232.26.70]
16 113 ms 114 ms 115 ms sl-teleg-3-17 110 ms 108 ms 110 ms 206.108.103.137
18 119 ms 121 ms 120 ms 206.108.103.133
19 120 ms 120 ms 120 ms 64.230.242.198
20 120 ms 122 ms 119 ms 206.108.97.70
21 126 ms 126 ms 126 ms 206.108.111.106
22 * * * Request timed out.
23 * * * Request timed out.
24 124 ms 124 ms 127 ms 129.33.183.72
25 * * * Request timed out.
26 * * * Request timed out.
27 130 ms 127 ms 128 ms radware-osrs1.tucows.com [216.40.33.70]
28 126 ms 125 ms 127 ms ddwww.tucows.com [216.40.33.117]
Trace complete.
You will see that hops 22, 23, 25 and 26 have no values...thats because that
server has refused the info...that is not a fault...but if you got Request
Timed out all the way to the end...that is a fault. As I am on broadband I
would have expected quite a few of the above values to be higher than they
are, but even so...its not to bad