Thanks guys -- I will look into it.

-- 
http://localrobot.com/

On Nov 7, 2010, at 13:24, "Martin v. Löwis" <[email protected]> wrote:

>> traceroute to ntppool-varnish.develooper.com (2607:f238:2::51), 30 hops max, 
>> 12 byte packets
>> 1  Stone  2.197 ms  2.149 ms *
>> 2  2610:98:8001:1::2  20.206 ms  20.056 ms  21.12 ms
>> 3  2610:98:1::1  19.715 ms  23.343 ms  20.268 ms
>> 4  2001:470:0:41::1  105.317 ms !N  107.428 ms !N  104.822 ms !N
>> 
>> It's not at all clear to me what's wrong here; superficially, looks
>> like a routing snafu, but after three days I would ahve expected a
>> routing hiccup to have fixed itself.  Is there anything I can do to
>> help get it, whatever it is, fixed?
> 
> It appears that the address prefix is not announced anymore; I get
> the same problem from different networks also. The route belongs to
> 
> NetRange:       2607:F238:: - 2607:F238:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF
> CIDR:           2607:F238::/32
> OriginAS:       AS7012
> NetName:        PHYBER-IPV6
> NetHandle:      NET6-2607-F238-1
> Parent:         NET6-2600-1
> NetType:        Direct Allocation
> NameServer:     RDNS02.PHYBER.COM
> NameServer:     RDNS01.PHYBER.COM
> RegDate:        2007-11-09
> Updated:        2007-11-09
> Ref:            http://whois.arin.net/rest/net/NET6-2607-F238-1
> 
> OrgName:        Phyber Communications, LLC.
> OrgId:          PCL-90
> Address:        214 Main Street #374
> City:           El Segundo
> StateProv:      CA
> PostalCode:     90245
> Country:        US
> RegDate:        2007-05-22
> Updated:        2008-11-04
> Comment:        http://www.phyber.com
> Comment:        +1-877-7-PHYBER (749237)
> Ref:            http://whois.arin.net/rest/org/PCL-90
> 
> OrgTechHandle: NOC2563-ARIN
> OrgTechName:   Network Operations Center
> OrgTechPhone:  +1-877-774-9237
> OrgTechEmail:  [email protected]
> OrgTechRef:    http://whois.arin.net/rest/poc/NOC2563-ARIN
> 
> According to
> 
> http://www.ris.ripe.net/dashboard/2607:f238::/32
> 
> this is not reachable from anywhere, since Nov 4.
> So I recommend to contact some operator there.
> 
> Regards,
> Martin
> _______________________________________________
> pool mailing list
> [email protected]
> http://lists.ntp.org/listinfo/pool
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool

Reply via email to