I'm behind the Sunrise Backborn the Trace to init7 is going over alter.net

Routenverfolgung zu init7.ch [213.144.129.91] über maximal 30 Abschnitte:

1 <1 ms <1 ms <1 ms r2d2.pop.ch [195.141.232.1] 2 21 ms 21 ms 49 ms 212.161.209.113 3 23 ms 23 ms 24 ms 212.161.164.50 4 41 ms 23 ms 23 ms 212.161.164.50 5 24 ms 25 ms 24 ms p9-0.zur01b03.sunrise.ch [193.192.225.61] 6 25 ms 26 ms 26 ms gi0-1.zur14s01.sunrise.ch [195.141.93.203] 7 26 ms 26 ms 26 ms 194.42.48.73 8 29 ms 33 ms 25 ms so-2-1-0.XR2.ZUR4.ALTER.NET [146.188.5.69] 9 36 ms 41 ms 31 ms 462.ATM1-0.GW7.ZUR4.ALTER.NET [146.188.6.82] 10 2351 ms 2293 ms 2180 ms uch200090.customer.alter.net [212.249.10.246] 11 1846 ms 1694 ms 1526 ms r4.core.init7.net [213.144.128.4] 12 1361 ms 1140 ms 1022 ms prayer.init7.net [213.144.129.91]

Ablaufverfolgung beendet.

Swisscom is over IP Plus... Else Firewall 1 <1 ms <1 ms <1 ms r2d2.pop.ch [195.141.232.1] 2 21 ms 22 ms 23 ms 212.161.209.113 3 24 ms 23 ms 24 ms 212.161.164.50 4 23 ms 24 ms 24 ms 212.161.164.50 5 98 ms 115 ms 83 ms p9-0.zur01b03.sunrise.ch [193.192.225.61] 6 26 ms 27 ms 27 ms gi0-1.zur14s01.sunrise.ch [195.141.93.203] 7 26 ms 25 ms 26 ms 193.192.255.202 8 25 ms 26 ms 25 ms i79zhh-015-xxx1-4.bb.ip-plus.net [138.187.129.73 ] 9 30 ms 29 ms 28 ms i64beb-000-gig0-3.bb.ip-plus.net [138.187.130.16 1] 10 32 ms 32 ms 31 ms i64beb-010-gig0-2.bb.ip-plus.net [138.187.157.10 ] 11 33 ms 34 ms 33 ms i64beb-061-gig0-2.bb.ip-plus.net [138.187.156.17 2] 12 31 ms 31 ms 30 ms cit-00-lb-ser1-0.ce.ip-plus.net [164.128.156.242 ] 13 * * * Zeitüberschreitung der Anforderung. 14 ^C

Cablecom is direct 1 <1 ms <1 ms <1 ms r2d2.pop.ch [195.141.232.1] 2 22 ms 23 ms 22 ms 212.161.209.113 3 27 ms 45 ms 24 ms 212.161.164.50 4 402 ms 96 ms 23 ms 212.161.164.50 5 25 ms 68 ms 45 ms p9-0.zur01b03.sunrise.ch [193.192.225.61] 6 25 ms 25 ms 25 ms gi12-0-0.zur14s03.sunrise.ch [193.192.234.208] 7 26 ms 26 ms 26 ms 194.230.36.202 8 27 ms 25 ms 26 ms tengig-2-4.mlrOTF008.gw.cablecom.net [62.2.33.6]

9 27 ms 31 ms 26 ms vlan701.mesOTF009.cablecom.net [62.2.25.162] 10 * * * Zeitüberschreitung der Anforderung. (Last i think Firewall)

Urgent Service Googel is direct Routenverfolgung zu www.l.google.com [66.249.85.104] über maximal 30 Abschnitte :

1 <1 ms <1 ms <1 ms r2d2.pop.ch [195.141.232.1] 2 25 ms 51 ms 231 ms 212.161.209.113 3 22 ms 22 ms 24 ms 212.161.164.50 4 23 ms 23 ms 23 ms 212.161.164.50 5 23 ms 22 ms 23 ms g5-2.lau01b04.sunrise.ch [193.192.234.229] 6 49 ms 49 ms 49 ms 194.230.36.218 7 49 ms 49 ms 48 ms core2.ams.google.com [195.69.145.100] 8 49 ms 48 ms 49 ms 216.239.43.89 9 43 ms 46 ms 43 ms 72.14.232.209 10 45 ms 43 ms 43 ms 66.249.85.104

To Germany T-Online

Routenverfolgung zu www.t-online.de [62.153.159.92] über maximal 30 Abschnitte:

1 <1 ms <1 ms <1 ms r2d2.pop.ch [195.141.232.1] 2 23 ms 24 ms 22 ms 212.161.209.113 3 27 ms 24 ms 22 ms 212.161.164.50 4 24 ms 23 ms 24 ms 212.161.164.50 5 25 ms 25 ms 25 ms p9-0.zur01b03.sunrise.ch [193.192.225.61] 6 27 ms 28 ms 26 ms gi12-0-0.zur14s03.sunrise.ch [193.192.234.208] 7 25 ms 25 ms 27 ms 217.6.24.185 8 39 ms 38 ms 38 ms 194.25.10.94 9 39 ms 38 ms 38 ms 217.6.25.154 10 39 ms 38 ms 85 ms www.t-online.de [62.153.159.92]

Ablaufverfolgung beendet.

I havn't any Problem....

Greetings Xaver -----Ursprüngliche Nachricht----- Von: swinog-bounces@lists.swinog.ch [mailto:swinog-bounces@lists.swinog.ch] Im Auftrag von Fredy Kuenzler Gesendet: Donnerstag, 21. September 2006 20:49 An: swinog@swinog.ch Betreff: [swinog] Sunrise network issues?

Anyone else with problems to reach the Sunrise backbone?

We saw an high latency between Verizon Business (702) and Sunrise and after rerouting via Telia (1299) the latency remained between in the Level3 (3356) Backbone.

TTL LFT trace to business.sunrise.ch (195.141.106.101):80/tcp 1 [AS13030] r4.core.init7.net (213.144.129.65) 3.1ms 2 [AS13030] r7.core.init7.net (213.144.128.7) 6.3ms 3 [AS1299] zch-b1-link.telia.net (213.248.96.45) 6.5ms 4 [AS1299] ffm-bb1-link.telia.net (213.248.65.41) 12.1ms 5 [AS1299] ffm-b2-link.telia.net (80.91.249.194) 14.5ms 6 [AS3356] ge-6-13.car2.Frankfurt1.Level3.net (4.68.111.101) 14.6ms 7 [AS3356] ae-0-53.bbr1.Frankfurt1.Level3.net (4.68.118.65) 3398.5/3402.7ms 8 [AS3356] so-1-0-0.mpls2.Geneva1.Level3.net (212.187.128.245) 3406.1/3414.9ms 9 [AS3356] so-10-0.hsa2.Geneva1.Level3.net (4.68.125.182) 3410.9/3408.9ms 10 [AS3356] 213.242.73.150 3385.8/3408.4ms 11 [AS6730] 195.141.35.3 3395.9/3403.3ms 12 [AS6730] gi0-1.ber08d01.sunrise.ch (195.141.225.222) 3391.5/3389.5ms 13 * [AS6730] 195.141.3.14 3387.2ms 14 [AS6730] [target] business.sunrise.ch (195.141.106.101):80 3381.2ms

Any explanation?

F. _______________________________________________ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog

Steven Glogger schrieb:

no, from cybernet seems to be fine:

Thanks, issue is resolved. We had a DDos attack to a customer server, which filled up the STM-1 from 702. Sunrise (and Cablecom too) did route towards Init7 over 702 (since we are outbound heavy, I didn't gave this much attention yet). BTW DDOS still going on.

I changed now our routing policy. They won't see us anymore over 702, which forces them to route over their upstreams towards us (towards 13030 is now flowing over 1299), unless they agree to peer.

http://debby.sunrise.ch/lg/ Tracing the route to www.init7.net (82.197.165.66)

1 g5-0.zur01b04.sunrise.ch (193.192.234.198) 4 msec 0 msec 0 msec 2 t2a2-ge0-1.ch-zur.eu.bt.net (166.49.219.1) [AS 5400] 0 msec 0 msec 0 msec 3 t2c2-ge7-0.ch-zur.eu.bt.net (166.49.186.44) [AS 5400] 0 msec 0 msec 4 msec 4 t2c1-p8-0.de-fra.eu.bt.net (166.49.164.161) [AS 5400] 4 msec 4 msec 8 msec 5 t2a4-ge6-0.de-fra.eu.bt.net (166.49.172.20) [AS 5400] 8 msec 8 msec 8 msec 6 de-cix-1.telia.net (80.81.192.35) [AS 6695] 4 msec 8 msec 8 msec 7 ffm-bb2-link.telia.net (80.91.249.142) [AS 1299] 12 msec 8 msec 12 msec 8 zch-b1-pos2-0.telia.net (213.248.65.170) [AS 1299] 20 msec 20 msec 20 msec 9 init-113677-zch-b1.c.telia.net (213.248.96.46) [AS 1299] 16 msec 20 msec 20 msec 10 r4.core.init7.net (213.144.128.4) [AS 13030] 24 msec 20 msec 24 msec 11 www.init7.net (82.197.165.66) [AS 13030] 24 msec 24 msec 24 msec

BTW is anyone aware of a working Cablecom LG or at least Traceroute?

F.

Nik Hug schrieb:

cablecom nervt:

zu init7 komme ich momentan gar nicht durch ...

marzili:~# traceroute www.init7.net

traceroute to www.init7.net (82.197.165.66), 30 hops max, 38 byte packets 1 192.168.1.1 (192.168.1.1) 2.699 ms 1.571 ms 1.565 ms 2 10.163.128.1 (10.163.128.1) 9.572 ms 11.617 ms 10.895 ms 3 * * * 4 * * * 5 nl-ams01a-rd1-ge-4-1.aorta.net (213.46.160.25) 40.022 ms 41.455 ms 41.158 ms 6 fr-par03a-rd1-ge-4-0.aorta.net (213.46.163.82) 40.285 ms 41.913 ms 46.195 ms 7 fr-par03a-ra1-ge-0-0-0_0.aorta.net (213.46.163.90) 40.701 ms * *

super-sach mit aorta.net!

The current routing policy of 8404 is questionable. The seem to prefer any route over 6830, even though they learn them directly over peering.

F.

Folks,

when you study the traceroutes you see some ISPs have 8ms from Zürich to Frankfurt, some Nordic operator has 12ms for example. Still you (Fredy) and others seem to buy from them. Why? What would be the route from that operator to Interbusiness or Milan in general - I would be seriously interested how many ms that would be. Maybe do a ping to 217.29.67.18, and post the ping in ms, no traceroute, let us keep the names out of it please.

It is a general thing. I would have thought swiss ISPs buying a bit more selective based on rtt and peering being local or close by. Disclaimers apply left and right, for you know who I am etc. But I am really surprised, believe it or not.

Think about it this way - before there were 2 ISPs you had with 'interesting' domestic peering policies. Now you have three... I could bet with you these three do not react so much about traffic over their upstream unless it is some 500m sustained...? I speak of experience, in a way.

No pun intended anywhere. Also I am happy with not naming names too much, raising only a general thought that was too obvious for me to not ask...

Alexander

On Fri, 22 September 2006 07:56:12 +0200, Alexander Koch wrote:

many ms that would be. Maybe do a ping to 217.29.67.18, and

217.29.66.75 might be better to test from some Nordic operator, that is their MIX IP. I would be curious how many ms that are, if more than 5 ms it would prove my point unfortunately. That network might not be routed though.

Alexander

On Fri, 22 September 2006 15:07:16 +0200, Gunther Stammwitz wrote:

We're not receiveing a route for that network although we're buying transit from AS1299:

It is an exchange, likely that is why. Anyway, what you write shows DECIX -> Init7 Zurich is 8ms or so, and Aorta is 12ms, while it was clear from the traceroutes that 1299 is also around 12ms. Not sure I want to know the routing of the underlying path for that wave.

Alexander

Daniel Kamm wrote:

On Fri, 2006-09-22 at 15:07 +0200, Gunther Stammwitz wrote:

...

Some performance measurements from Frankfurt:

Back to our studies, we tried to implement a system, that periodically stores traceroutes from looking glass servers to some other endpoints. The main goal was to display a map which shows which provider uses wich route and detect routing changes (well, this had never been reached).

You might want to take a look at RIPE TTM ;) http://www.ripe.net/ttm/

As it does that and a lot of other things.

Greets, Jeroen