On 2013-09-26 16:07 , Andreas Fink wrote:
> ...or modify your webservers to not deliver web content on such routes
> to avoid PRISM and inform the customer about the "shortcut" of his
> switzerland to switzerland data over NSA territory...
Don't worry about that, they don't need to pull that trick
ag von Stephan Wolf
> Gesendet: Donnerstag, 26. September 2013 15:47
> An: swinog
> Betreff: Re: [swinog] Scenic route of the day: L3 towards UPC
>
> I have seen things here similar to this very often / permanently:
>
> cablecom to UK/NL often via level3 and washington inste
eundliche GrĂ¼sse
Matias Meier
Online WebToolbox: www.webtoolbox.ch<http://www.webtoolbox.ch/>
Von: swinog-boun...@lists.swinog.ch [mailto:swinog-boun...@lists.swinog.ch] Im
Auftrag von Stephan Wolf
Gesendet: Donnerstag, 26. September 2013 15:47
An: swinog
Betreff: Re: [swinog] Scenic route
On 2013-09-26 15:01 , Fredy Kuenzler wrote:
> Am 26.09.2013 12:33, schrieb Jeroen Massar:
>>> Anyone else seeing this... do we have a new peering spat or is it
>>> just a random routing issue?
>>
>> Looks to be just that prefix, as for instance:
>
> Actually we've seen more than 300 prefixes with
I have seen things here similar to this very often / permanently:
cablecom to UK/NL often via level3 and washington instead going directly
may something to do with UPC and partnership with level3 - and the
"Nonpartners" of level3.
"we do not peer with you" politics ?!
imho cogent vs level3
Am 26.09.2013 12:33, schrieb Jeroen Massar:
>> Anyone else seeing this... do we have a new peering spat or is it
>> just a random routing issue?
>
> Looks to be just that prefix, as for instance:
Actually we've seen more than 300 prefixes with the same path. Meanwhile
the journey to california an
On 2013-09-26 11:55 , Fredy Kuenzler wrote:
> Anyone else seeing this... do we have a new peering spat or is it just a
> random routing issue?
Looks to be just that prefix, as for instance:
traceroute to chzrh02.sixxs.net (213.144.148.74), 64 hops max, 52 byte
packets
[..]
3 217-168-54-245.stat
Anyone else seeing this... do we have a new peering spat or is it just a
random routing issue?
Regards,
Fredy
traceroute to 84.116.204.234 (84.116.204.234), 30 hops max, 60 byte packets
1 r1zlz1.core.init7.net (77.109.136.233) [AS13030] 23.682 ms 23.741
ms 23.775 ms
2 r1zrh1.core.init7.n
8 matches
Mail list logo