Hi,

I'm also leaving in South of France, experimenting the same problems exposed here. But the "proxy" solutions does not fit my needs as I already needs proxy to get my internet connection (to go out of my office local network).

Any idea?

Sorry if I missed a reply about this in the thread.

David.

> > Just so you know and don't claim all the glory (as usual of the American
> > culture) the WWW was developed at CERN, in France/Switzerland, (only the
> > Internet was developed by the US Military) - ironically the guy that
> invented
> > the WWW hates it lol :P
>
> ... and only the badly uninformed use the terms "web" and "internet"
> interchangably.
>
> I didn't say that the government involvement was good. I didn't say that
> involvement by the U.S. government was good. I didn't say that the U.S.
> deserved a pat on the back for accidentally developing something useful.
>
> I just said that the government was and still is involved.
>
> I'd be happier if they weren't. I don't even care which one.
>
> But more than anything else, I'd be happy if we could have a good technical
> discussion without bashing each other over politics, governments, and
> nationality.
>
Agreed.... Truce...whatever makes our world a happy one! I was not aware I had introduced nationality into the argument....and would NEVER wittingly do so sir. If I have then please accept my humble apologies. As for governments....ha..... they are there to be bashed so they are fair game!

---

> Hi,
>
> I'm also leaving in South of France, experimenting the same problems exposed
> here. But the "proxy" solutions does not fit my needs as I already needs
> proxy to get my internet connection (to go out of my office local network).
>
> Any idea?
>
> Sorry if I missed a reply about this in the thread.
>
> David.
>
David Salut!
I'm not sure how you resolve that if you need a proxy to get to the internet anyway. Hmmmm....but I will think about it and see if there is anything can be done as will everyone lese here I guess.

---

> Well you can add another area to the misfortune. I am in French Guyana, South
> America. We come in to the US on the Americas II line. I get the trace
> routes and ping ok for SETI, but the server systems do not respond and have
> not since Thursday the 14th. It is the same thing for Pirate and LHC, but
> Einstein and climat are working.
>
Hi GOC. Sounds like a different problem. Post your tracert info here so we can see. Thanks

---

> If you need to use a proxy that's safe and at the same time protect your
> privacy you could also try <a> href="http://anon.inf.tu-dresden.de/index_en.html">this free service[/url]
> I was able to connect to S@H using this service and I think I don't have to
> worry about what the proxy server is doing with my private data that passes
> through it.
>
> Regards
>

Hi,
This free service of anonymity works fine and solve my problem. It is called JAP.

Thanks!

David.

---

sorry

---

Mit freundlichen Grüssen, Arnold
BZH Café

hi all

PING www.climateprediction.net (137.108.64.33): 56 data bytes

--- www.climateprediction.net ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss

any idee for this ?
thx

---

Mit freundlichen Grüssen, Arnold
BZH Café

> hi all
>
> PING www.climateprediction.net (137.108.64.33): 56 data bytes
>
> --- www.climateprediction.net ping statistics ---
> 5 packets transmitted, 0 packets received, 100% packet loss
>
> any idee for this ?
> thx
>
Hi
You are in France?
You may be affected by the problem. Do a tracert setiboic.ssl.berkeley.edu and post the results and we can see then.

---

[b]$[/b] traceroute www.climateprediction.net
[b]traceroute to www.climateprediction.net (137.108.64.33), 30 hops max, 40 byte packets
 1  10.32.19.1 (10.32.19.1)  18.34 ms  8.712 ms  8.792 ms
 2  130.81.11.157 (130.81.11.157)  8.908 ms  8.611 ms  9.753 ms
 3  so-6-0-0-0.bb-rtr1.ny325.verizon-gni.net (130.81.18.88)  9.338 ms  19.73 ms  8.645 ms
 4  so-6-0-0-0.peer-rtr1.ny111.verizon-gni.net (130.81.17.129)  11.347 ms  112.649 ms  45.665 ms
 5  so-6-2-0-0.gar2.newyork1.level3.net (65.59.196.17)  9.421 ms  8.783 ms  48.898 ms
 6  ae-1-53.bbr1.newyork1.level3.net (4.68.97.65)  8.943 ms  8.906 ms
    ae-1-51.bbr1.newyork1.level3.net (4.68.97.1)  9.064 ms
 7  as-0-0.bbr2.london1.level3.net (4.68.128.105)  74.782 ms  90.502 ms  95.669 ms
 8  ae-1-0.bbr1.london2.level3.net (212.187.128.46)  100.341 ms  101.708 ms  100.294 ms
 9  ge-3-0-0.gar1.london2.level3.net (4.68.124.62)  97.509 ms  100.724 ms  98.46 ms
10  195.50.116.202 (195.50.116.202)  110.08 ms  79.108 ms  89.679 ms
11  po2-0.lond-scr4.ja.net (146.97.35.221)  99.881 ms  101.604 ms  99.07 ms
12  gi0-1.lond-bar4.ja.net (146.97.35.210)  102.766 ms  98.04 ms  94.317 ms
13  146.97.41.146 (146.97.41.146)  99.65 ms  80.181 ms  88.426 ms
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

[b]$[/b] nslookup 146.97.41.146
[b]Note:  nslookup is deprecated and may be removed from future releases.
Consider using the `dig' or `host' programs instead.  Run nslookup with
the `-sil[ent]' option to prevent this message from appearing.
Server:         151.202.0.84
Address:        151.202.0.84#53

** server can't find 146.41.97.146.in-addr.arpa: NXDOMAIN

$[/b] nslookup 146.97.35.210
[b]Note:  nslookup is deprecated and may be removed from future releases.
Consider using the `dig' or `host' programs instead.  Run nslookup with
the `-sil[ent]' option to prevent this message from appearing.
Server:         151.202.0.84
Address:        151.202.0.84#53

Non-authoritative answer:
210.35.97.146.in-addr.arpa      name = gi0-1.lond-bar4.ja.net.

Authoritative answers can be found from:
97.146.in-addr.arpa     nameserver = ns4.ja.net.
97.146.in-addr.arpa     nameserver = ns0.ja.net.
97.146.in-addr.arpa     nameserver = ns1.cs.ucl.ac.uk.
97.146.in-addr.arpa     nameserver = ns1.surfnet.nl.
ns4.ja.net      internet address = 193.62.157.66
ns4.ja.net      has AAAA address 2001:630:0:47::42[/b]

---

[DELETED] Incorrect information posted - See 101149

---

> $ traceroute setiweb.ssl.berkeley.edu
> traceroute to klaatu.ssl.berkeley.edu (128.32.18.152), 30 hops max, 40 byte
> packets
> 1 10.32.19.1 (10.32.19.1) 35.654 ms 15.506 ms 8.716 ms
> 2 130.81.11.161 (130.81.11.161) 13.652 ms 9.178 ms 8.425 ms
> 3 so-0-0-0-0.core-rtr1.ny325.verizon-gni.net (130.81.7.181) 15.75 ms
> 10.107 ms 10.619 ms
> 4 so-6-0-0-0.bb-rtr1.ny325.verizon-gni.net (130.81.18.88) 9.949 ms 14.941
> ms 9.978 ms
> 5 so-6-2-0-0.bb-rtr1.res.verizon-gni.net (130.81.8.253) 15.93 ms 17.708 ms
> 17.101 ms
> 6 130.81.10.90 (130.81.10.90) 69.897 ms 17.761 ms 16.198 ms
> 7 130.81.15.18 (130.81.15.18) 15.309 ms 16.104 ms 16.386 ms
> 8 pos5-0.gsr12012.dal.he.net (66.160.184.13) 47.544 ms 47.515 ms 46.718
> ms
> 9 pos5-0.gsr12012.lax.he.net (66.160.184.5) 86.044 ms 85.241 ms 85.242
> ms
> 10 198.32.251.85 (198.32.251.85) 76.901 ms 76.373 ms 76.36 ms
> 11 dc-sac-dc1--lax-dc1-pos.cenic.net (137.164.22.127) 85.427 ms 86.351 ms
> 84.99 ms
> 12 dc-oak-dc2--csac-dc1-ge.cenic.net (137.164.22.110) 87.091 ms 87.641 ms
> 86.964 ms
> 13 ucb--oak-dc2-ge.cenic.net (137.164.23.30) 87.604 ms 87.222 ms 95.581
> ms
> 14 vlan189.inr-201-eva.berkeley.edu (128.32.0.37) 87.218 ms 86.391 ms
> 86.205 ms
> 15 g1-1.inr-230-spr.berkeley.edu (128.32.255.110) 87.071 ms 87.352 ms
> 87.682 ms
> 16 * * *
> 17 * * *
> 18 * * *
> 19 * * *
> 20 * * *
> 21 * * *
> 22 * * *
> 23 * * *
> 24 * * *
> 25 * * *
> 26 * * *
> 27 * * *
> 28 * * *
> 29 * * *
> 30 * * *
>
> I'm out of ideas...
>

Hi. Dont trace to setiweb....tracert setiboinc.ssl.berkeley.edu. Thats the data server. Post the results.

---

[b]$[/b]traceroute setiboinc.ssl.berkeley.edu
[b]traceroute to setiboincdata.ssl.berkeley.edu (66.28.250.125), 30 hops max, 40 byte packets
 1  10.32.19.1 (10.32.19.1)  18.161 ms  8.237 ms  7.596 ms
 2  130.81.11.161 (130.81.11.161)  8.089 ms  8.02 ms  61.854 ms
 3  so-6-0-0-0.bb-rtr2.ny325.verizon-gni.net (130.81.18.90)  10.18 ms  8.904 ms  9.502 ms
 4  so-7-0-0-0.peer-rtr1.ny111.verizon-gni.net (130.81.17.131)  46.444 ms  9.083 ms  10.596 ms
 5  so-2-0-0-0.peer-rtr2.ny111.verizon-gni.net (130.81.4.2)  8.552 ms  7.968 ms  9.533 ms
 6  130.81.15.14 (130.81.15.14)  8.631 ms  9.704 ms  41.409 ms
 7  p9-0.core02.jfk02.atlas.cogentco.com (154.54.1.129)  11.125 ms  8.994 ms  9.297 ms
 8  p10-0.core02.sfo01.atlas.cogentco.com (66.28.4.209)  88.946 ms  88.541 ms  105.795 ms
 9  g0-2.na01.b003123-1.sfo01.atlas.cogentco.com (66.28.6.6)  99.097 ms  89.339 ms  99.096 ms
10  uc-berkeley.demarc.cogentco.com (66.250.4.74)  94.902 ms  95.095 ms  96.133 ms
11  66.28.250.125 (66.28.250.125)  97.897 ms  95.67 ms  96.543 ms

$[/b]nslookup 66.28.250.125[b]
Server:        151.202.0.84
Address:       151.202.0.84#53

** server can't find 125.250.28.66.in-addr.arpa: NXDOMAIN

$[/b]nslookup 66.250.4.74[b]
Server:        151.202.0.84
Address:       151.202.0.84#53

Non-authoritative answer:
74.4.250.66.in-addr.arpa name = UC-Berkeley.demarc.cogentco.com.

Authoritative answers can be found from:
4.250.66.in-addr.arpa    nameserver = auth2.dns.cogentco.com.
4.250.66.in-addr.arpa    nameserver = auth4.dns.cogentco.com.
4.250.66.in-addr.arpa    nameserver = auth5.dns.cogentco.com.
4.250.66.in-addr.arpa    nameserver = auth1.dns.cogentco.com.
auth1.dns.cogentco.com   internet address = 66.28.0.14
auth4.dns.cogentco.com   internet address = 80.245.32.74
auth5.dns.cogentco.com   internet address = 80.91.64.50[/b]

---

This is coming from the NYC/LI Verizon pools, so it's probably useless for the most part, but I can't get www.climateprediction.net either - Even the website times out on me.

---

>

[b]$[/b]traceroute setiboinc.ssl.berkeley.edu
[b]traceroute to
> setiboincdata.ssl.berkeley.edu (66.28.250.125), 30 hops max, 40 byte
> packets
 1  10.32.19.1 (10.32.19.1)  18.161 ms  8.237 ms  7.596 ms
 2 
> 130.81.11.161 (130.81.11.161)  8.089 ms  8.02 ms  61.854 ms
 3 
> so-6-0-0-0.bb-rtr2.ny325.verizon-gni.net (130.81.18.90)  10.18 ms  8.904 ms 
> 9.502 ms
 4  so-7-0-0-0.peer-rtr1.ny111.verizon-gni.net (130.81.17.131) 
> 46.444 ms  9.083 ms  10.596 ms
 5 
> so-2-0-0-0.peer-rtr2.ny111.verizon-gni.net (130.81.4.2)  8.552 ms  7.968 ms 
> 9.533 ms
 6  130.81.15.14 (130.81.15.14)  8.631 ms  9.704 ms  41.409 ms

> 7  p9-0.core02.jfk02.atlas.cogentco.com (154.54.1.129)  11.125 ms  8.994 ms 
> 9.297 ms
 8  p10-0.core02.sfo01.atlas.cogentco.com (66.28.4.209)  88.946 ms
>  88.541 ms  105.795 ms
 9  g0-2.na01.b003123-1.sfo01.atlas.cogentco.com
> (66.28.6.6)  99.097 ms  89.339 ms  99.096 ms
10 
> uc-berkeley.demarc.cogentco.com (66.250.4.74)  94.902 ms  95.095 ms  96.133
> ms
11  66.28.250.125 (66.28.250.125)  97.897 ms  95.67 ms  96.543
> ms

$[/b]nslookup 66.28.250.125[b]
Server:       
> 151.202.0.84
Address:       151.202.0.84#53

** server can't find
> 125.250.28.66.in-addr.arpa: NXDOMAIN

$[/b]nslookup
> 66.250.4.74[b]
Server:        151.202.0.84
Address:      
> 151.202.0.84#53

Non-authoritative answer:
74.4.250.66.in-addr.arpa
> name = UC-Berkeley.demarc.cogentco.com.

Authoritative answers can be
> found from:
4.250.66.in-addr.arpa    nameserver =
> auth2.dns.cogentco.com.
4.250.66.in-addr.arpa    nameserver =
> auth4.dns.cogentco.com.
4.250.66.in-addr.arpa    nameserver =
> auth5.dns.cogentco.com.
4.250.66.in-addr.arpa    nameserver =
> auth1.dns.cogentco.com.
auth1.dns.cogentco.com   internet address =
> 66.28.0.14
auth4.dns.cogentco.com   internet address =
> 80.245.32.74
auth5.dns.cogentco.com   internet address =
> 80.91.64.50[/b]

>
Well that says you are reaching the seti data sever OK. So....what is the problem that you have?

---

Never mind - just got climate prediction back...

Sorry for the confusion...

---

> > Well you can add another area to the misfortune. I am in French Guyana,
> South
> > America. We come in to the US on the Americas II line. I get the trace
> > routes and ping ok for SETI, but the server systems do not respond and
> have
> > not since Thursday the 14th. It is the same thing for Pirate and LHC,
> but
> > Einstein and climat are working.
> >
> Hi GOC. Sounds like a different problem. Post your tracert info here so we can
> see. Thanks
>

I'm seem to have the same problem but in the land down under -

Tracing route to setiboincdata.ssl.berkeley.edu [66.28.250.125]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.254
2 2232 ms 966 ms 2713 ms nexthop.qld.iinet.net.au [203.55.228.88]
3 1931 ms 1989 ms 2617 ms Gi1-0-0-17.bne-pipe-bdr1.chime.net.au [203.55.228.188]
4 1490 ms 1061 ms 358 ms GigabitEthernet2-1.cha23.Brisbane.telstra.net [139.130.130.37]
5 953 ms 2148 ms 1891 ms GigabitEthernet5-0.cha-core4.Brisbane.telstra.net [203.50.44.9]
6 2161 ms 3286 ms * Pos4-0.chw-core2.Sydney.telstra.net [203.50.6.225]
7 * 1681 ms 2264 ms InterfaceA.oxf-core1.Sydney.telstra.net [203.50.6.2]
8 1493 ms 3172 ms 1182 ms GigabitEthernet6-0.syd-core04.Sydney.net.reach.com [203.50.13.34]
9 1927 ms 1886 ms 1351 ms i-5-0.syd-core02.net.reach.com [202.84.144.249]
10 2244 ms 2732 ms 2150 ms i-4-0.syd-core01.net.reach.com [202.84.221.89]
11 3274 ms 1396 ms 3430 ms i-12-2.wil-core01.net.reach.com [202.84.144.25]
12 1431 ms * * i-3-2.wil03.net.reach.com [202.84.251.170]
13 1879 ms 2331 ms 3034 ms unassign.net.reach.com [134.159.63.66]
14 1662 ms 3095 ms 1557 ms p15-0.core01.lax01.atlas.cogentco.com [154.54.2.213]
15 1412 ms 3148 ms * p14-0.core01.sjc01.atlas.cogentco.com [66.28.4.74]
16 1759 ms 3610 ms 3115 ms p4-0.core01.sfo01.atlas.cogentco.com [66.28.4.93]
17 1518 ms 3460 ms 2057 ms g0-1.na01.b003123-1.sfo01.atlas.cogentco.com [66.28.6.2]
18 3909 ms * * UC-Berkeley.demarc.cogentco.com [66.250.4.74]
19 3114 ms 3658 ms 2452 ms 66.28.250.125

Trace complete.

Is this the same? I'm still trying to understand Traceroute and the unassign.net.reach.com is a trigger for me ??

Any help ??

Thanx's

James

---

> > > Well you can add another area to the misfortune. I am in French
> Guyana,
> > South
> > > America. We come in to the US on the Americas II line. I get the
> trace
> > > routes and ping ok for SETI, but the server systems do not respond
> and
> > have
> > > not since Thursday the 14th. It is the same thing for Pirate and
> LHC,
> > but
> > > Einstein and climat are working.
> > >
> > Hi GOC. Sounds like a different problem. Post your tracert info here so
> we can
> > see. Thanks
> >
>
> I'm seem to have the same problem but in the land down under -
>
> Tracing route to setiboincdata.ssl.berkeley.edu [66.28.250.125]
> over a maximum of 30 hops:
>
> 1 1 ms 1 ms 1 ms 192.168.1.254
> 2 2232 ms 966 ms 2713 ms nexthop.qld.iinet.net.au [203.55.228.88]
> 3 1931 ms 1989 ms 2617 ms Gi1-0-0-17.bne-pipe-bdr1.chime.net.au
> [203.55.228.188]
> 4 1490 ms 1061 ms 358 ms GigabitEthernet2-1.cha23.Brisbane.telstra.net
> [139.130.130.37]
> 5 953 ms 2148 ms 1891 ms
> GigabitEthernet5-0.cha-core4.Brisbane.telstra.net [203.50.44.9]
> 6 2161 ms 3286 ms * Pos4-0.chw-core2.Sydney.telstra.net
> [203.50.6.225]
> 7 * 1681 ms 2264 ms InterfaceA.oxf-core1.Sydney.telstra.net
> [203.50.6.2]
> 8 1493 ms 3172 ms 1182 ms
> GigabitEthernet6-0.syd-core04.Sydney.net.reach.com [203.50.13.34]
> 9 1927 ms 1886 ms 1351 ms i-5-0.syd-core02.net.reach.com [202.84.144.249]
> 10 2244 ms 2732 ms 2150 ms i-4-0.syd-core01.net.reach.com [202.84.221.89]
> 11 3274 ms 1396 ms 3430 ms i-12-2.wil-core01.net.reach.com
> [202.84.144.25]
> 12 1431 ms * * i-3-2.wil03.net.reach.com [202.84.251.170]
> 13 1879 ms 2331 ms 3034 ms unassign.net.reach.com [134.159.63.66]
> 14 1662 ms 3095 ms 1557 ms p15-0.core01.lax01.atlas.cogentco.com
> [154.54.2.213]
> 15 1412 ms 3148 ms * p14-0.core01.sjc01.atlas.cogentco.com
> [66.28.4.74]
> 16 1759 ms 3610 ms 3115 ms p4-0.core01.sfo01.atlas.cogentco.com
> [66.28.4.93]
> 17 1518 ms 3460 ms 2057 ms g0-1.na01.b003123-1.sfo01.atlas.cogentco.com
> [66.28.6.2]
> 18 3909 ms * * UC-Berkeley.demarc.cogentco.com [66.250.4.74]
> 19 3114 ms 3658 ms 2452 ms 66.28.250.125
>
> Trace complete.
>
> Is this the same? I'm still trying to understand Traceroute and the
> unassign.net.reach.com is a trigger for me ??
>
> Any help ??
>
> Thanx's
>
> James
>
>
>
>
>
James Hi.
I see you are reaching the Boinc data server from that trace route. But you have very long times between hops. This may be network congestion rather than any problem being routed to UC. So I think your problem is different but nevertheless a problem. It may just go away when things get quieter. Where you see a ** that can mean a router is dropping packets and thats where the problem may lie. It may be badly configured or just overworked or faulty. But you do eventually get through albeit slowly. Just hang and see if it resolves itself. Cheers and G'day!

---

> > hi all
> > PING www.climateprediction.net (137.108.64.33): 56 data bytes
> > --- www.climateprediction.net ping statistics ---
> > 5 packets transmitted‰'k¹>õ¥•Ëòv1›È6؆ved, 100% packet loss
> > any idee for this ?
> > thx
> Hi
> You are in France?
> You may be affected by the problem. Do a tracert setiboic.ssl.berkeley.edu and
> post the results and we can see then.

hi tiger: yep i m her in france !

Target Name: www.climateprediction.net
IP: 137.108.64.33
Date/Time: 19/04/2005 13:39:30

1 * * * * * * * * [-]
2 * * * * * * * * [-]
3 57 ms 57 ms 54 ms 57 ms 53 ms 57 ms 56 ms 58 ms [193.253.171.66]
4 54 ms 51 ms 50 ms 54 ms 54 ms 53 ms 51 ms 52 ms [10.224.28.18]
5 59 ms 59 ms 59 ms 60 ms 60 ms 59 ms 57 ms 61 ms pos12-3.nrsta304.Paris.francetelecom.net [193.252.103.158]
6 66 ms 60 ms 57 ms 61 ms 60 ms 57 ms 61 ms 59 ms [193.251.126.50]
7 60 ms 58 ms 59 ms 59 ms 58 ms 60 ms 56 ms 60 ms P9-0.PASCR1.Pastourelle.opentransit.net [193.251.129.61]
8 60 ms 60 ms 60 ms 58 ms 159 ms 59 ms 58 ms 59 ms Level3.GW.opentransit.net [193.251.240.214]
9 60 ms 62 ms 59 ms 66 ms 138 ms 59 ms 63 ms 77 ms ae-0-17.mp1.Paris1.Level3.net [212.73.240.97]
10 69 ms 69 ms 66 ms 77 ms 123 ms 68 ms 69 ms 68 ms ae-1-0.bbr1.London2.Level3.net [212.187.128.46]
11 132 ms 67 ms 69 ms 69 ms 101 ms 66 ms 68 ms 69 ms ge-3-0-0.gar1.London2.Level3.net [4.68.124.62]
12 66 ms 66 ms 65 ms 68 ms 78 ms 65 ms 63 ms 67 ms [195.50.116.202]
13 69 ms 66 ms 66 ms 69 ms 66 ms 68 ms 67 ms 68 ms po2-0.lond-scr4.ja.net [146.97.35.221]
14 76 ms 64 ms 66 ms 67 ms 67 ms 66 ms 66 ms 67 ms gi0-1.lond-bar4.ja.net [146.97.35.210]


????? IP: 137.108.64.33

wath u can see ?

---

Mit freundlichen Grüssen, Arnold
BZH Café

> > > hi all
> > > PING www.climateprediction.net (137.108.64.33): 56 data bytes
> > > --- www.climateprediction.net ping statistics ---
> > > 5 packets transmitted‰'k¹>õ¥•Ëòv1›È6؆ved, 100% packet loss
> > > any idee for this ?
> > > thx
> > Hi
> > You are in France?
> > You may be affected by the problem. Do a tracert
> setiboic.ssl.berkeley.edu and
> > post the results and we can see then.
>
> hi tiger: yep i m her in france !
>
> Target Name: www.climateprediction.net
> IP: 137.108.64.33
> Date/Time: 19/04/2005 13:39:30
>
> 1 * * * * * * * * [-]
> 2 * * * * * * * * [-]
> 3 57 ms 57 ms 54 ms 57 ms 53 ms 57 ms 56 ms 58 ms
> [193.253.171.66]
> 4 54 ms 51 ms 50 ms 54 ms 54 ms 53 ms 51 ms 52 ms
> [10.224.28.18]
> 5 59 ms 59 ms 59 ms 60 ms 60 ms 59 ms 57 ms 61 ms
> pos12-3.nrsta304.Paris.francetelecom.net [193.252.103.158]
> 6 66 ms 60 ms 57 ms 61 ms 60 ms 57 ms 61 ms 59 ms
> [193.251.126.50]
> 7 60 ms 58 ms 59 ms 59 ms 58 ms 60 ms 56 ms 60 ms
> P9-0.PASCR1.Pastourelle.opentransit.net [193.251.129.61]
> 8 60 ms 60 ms 60 ms 58 ms 159 ms 59 ms 58 ms 59 ms
> Level3.GW.opentransit.net [193.251.240.214]
> 9 60 ms 62 ms 59 ms 66 ms 138 ms 59 ms 63 ms 77 ms
> ae-0-17.mp1.Paris1.Level3.net [212.73.240.97]
> 10 69 ms 69 ms 66 ms 77 ms 123 ms 68 ms 69 ms 68 ms
> ae-1-0.bbr1.London2.Level3.net [212.187.128.46]
> 11 132 ms 67 ms 69 ms 69 ms 101 ms 66 ms 68 ms 69 ms
> ge-3-0-0.gar1.London2.Level3.net [4.68.124.62]
> 12 66 ms 66 ms 65 ms 68 ms 78 ms 65 ms 63 ms 67 ms
> [195.50.116.202]
> 13 69 ms 66 ms 66 ms 69 ms 66 ms 68 ms 67 ms 68 ms
> po2-0.lond-scr4.ja.net [146.97.35.221]
> 14 76 ms 64 ms 66 ms 67 ms 67 ms 66 ms 66 ms 67 ms
> gi0-1.lond-bar4.ja.net [146.97.35.210]
>
>
> ????? IP: 137.108.64.33
>
> wath u can see ?
>
Hi. My guess would be that the router for that university is down or their link to Internet is down. I cant tracert it either....get as far London only. Wait while and see what happens.

---

just tried JAP here from France
no luck but the proxies work


over on NANOG they are quite hard on Cogent saying they have a few bottomless pits
1 for our traffic
2 of money