UAE-IX #3 · 2018-01-23 · UAE-IX #18 Jeddah to Jeddah Router: gin-jsd-core1 Site: SA, Jeddah, JSD...

February, 2014 Marco Brandstaetter Business Development, DE-CIX Management GmbH [email protected]

Peering “mentality” – an example from GCC

#3 UAE-IX www.uae-ix.net


Terestrial Links in GCC region


IXPs in GCC region


Some examples of Carriers in the region: Interoute

IP POP in Dubai

DubaiIP 84.233.221.50

Dubai Looking Glass:

http://hub.interoute.com

(84.233.221.50 = Gi0-3.dxb-003-access-3.interoute.net)


Some examples of Carriers in the region: PCCW

IP POP in Dubai

IP 63.218.176.65

Looking Glass:

http://lookingglass. pccglobal.com



Some examples of Carriers in the region: Level3

IP POP in Jeddah (SA)

IP 4.69.148.222

Looking Glass:

http://lg.level3.net



Some examples of Carriers in the region: Tata

IP POP in Jeddah and

Riyadh

IP Jeddah 80.231.165.78

Looking Glass:

http://lg.teleglobe.net/lg/



Traffic between Dubai and Dubai should be exchanged in Dubai

Traffic inside GCC region should be exchanged inside GCC

Runtimes:

Vienna – Frankfurt = ~ 700 km = 13 ms

Riad – Dubai = ~ 1000 km should be ~ 19 ms

Jeddah – Dubai = ~ 2500 km should be ~ 50 / 120 ms

Some thoughts for the following examples


First: How connections should look like in the ideal world….

server

router

UAE-‐IXExchange

router

server

ISP#1 somewhere in dubai ISP#2 somewhere in dubai

#traceroute server.isp2.aerouter.isp1.ae ~1 msec

router.isp2.ae ~1 msec (= uae-‐ix ip address)server.isp2.ae ~1 msec


Lets try the first easy example:

Try: Tracing from Dubai to Dubai

Side A: pccw lookingglass

Side B: ip of interoute in dubai

Expected Runtime: 1-2 msec

What do you think we will see?

A first example


Dubai to Dubai

Abort / Removecr01.dub01.pccwbtn.net84.233.221.50 traceroute ip 84.233.221.50 Tracing the route to Gi0-3.dxb-003-access-3.interoute.net (84.233.221.50) 1 ge5-0-1.var01.dub01.pccwbtn.net (63.218.176.66) 0 msec 0 msec 0 msec 2 pos4-6.cr03.ldn01.pccwbtn.net (63.218.176.38) 136 msec 136 msec 136 msec 3 TenGE11-2.br02.ldn01.pccwbtn.net (63.218.12.146) 136 msec 136 msec 136 msec 4 xe-11-1-1.lon21.ip4.tinet.net (77.67.94.153) 136 msec 136 msec 136 msec 5 xe-11-3-0.par72.ip4.tinet.net (141.136.111.246) 144 msec xe-2-2-2.par72.ip4.tinet.net (141.136.111.250) 148 msec 144 msec 6 interoute-gw.ip4.tinet.net (77.67.75.238) 148 msec 144 msec 144 msec 7 ae1-0.mrs-001-score-1-re0.interoute.net (217.118.118.74) 156 msec 156 msec 160 msec 8 Gi0-1.mrs-boi-access-2.interoute.net (217.118.118.86) 160 msec 160 msec Gi0-3.mrs-boi-access-2.interoute.net (217.118.118.82) 160 msec 9 so-1-0-0-0.dxb-003-access-1-re1.interoute.net (84.233.221.41) [MPLS: Label 299776 Exp 0] 260 msec 260 msec 264 msec 10 ge-0-0-0-0.dxb-003-access-2-re1.interoute.net (84.233.221.30) 260 msec 260 msec 260 msec 11 Gi0-3.dxb-003-access-3.interoute.net (84.233.221.50) 264 msec * 260 msec Query Complete

25.000 km instead of 20260 msec instead of 1


Lets try the second example:

Try: Tracing from Jeddah to Dubai (~ 2500 km)

Side A: Level3 lookingglass

Side B: datamena 94.207.32.1 (bg1.dx1.datamena.ae)

Expected Runtime: 50 msec or 120 via seacable

What do you think we will see?

Bad example? Try another one….


Jeddah to Dubai

1 ae-5-6.bar1.Marseille1.Level3.net (4.69.143.158) 47.743 ms 47.648 ms 47.535 ms 2 ae-7-7.ebr1.Paris1.Level3.net (4.69.143.238) 64.999 ms 65.000 ms 65.057 ms 3 ae-63-63.csw1.Paris1.Level3.net (4.69.161.110) 69.492 ms 65.502 ms ae-73-73.csw2.Paris1.Level3.net (4.69.161.114) 65.609 ms 4 ae-61-61.ebr1.Paris1.Level3.net (4.69.161.77) 64.923 ms ae-71-71.ebr1.Paris1.Level3.net (4.69.161.81) 65.071 ms ae-81-81.ebr1.Paris1.Level3.net (4.69.161.85) 65.831 ms 5 ae-45-45.ebr1.London1.Level3.net (4.69.143.101) 64.996 ms ae-47-47.ebr1.London1.Level3.net (4.69.143.109) 66.120 ms 73.129 ms 6 ae-56-111.csw1.London1.Level3.net (4.69.153.114) 65.217 ms ae-58-113.csw1.London1.Level3.net (4.69.153.122) 76.913 ms ae-59-114.csw1.London1.Level3.net (4.69.153.126) 64.958 ms 7 ae-116-3502.edge3.London1.Level3.net (4.69.166.134) 104.733 ms ae-118-3504.edge3.London1.Level3.net (4.69.166.142) 64.897 ms ae-117-3503.edge3.London1.Level3.net (4.69.166.138) 72.163 ms 8 EMIRATES-IN.edge3.London1.Level3.net (212.113.15.66) 64.924 ms 65.871 ms 64.919 ms 9 * * * 10 94.201.0.50 (94.201.0.50) 212.263 ms 211.648 ms 211.709 ms 11 * * * 12 94.205.255.33 (94.205.255.33) 210.974 ms 210.779 ms 210.772 ms

2x.000 km instead of 2500210 msec instead of 50


Lets try the second example:

Try: Tracing from Jeddah to Jeddah (~ 0 km)

Side A: Tatacommunications lookingglass

Side B: Level3 – Router IP in Jeddah 4.69.143.157

Expected Runtime: 1 msec

Another bad example? Let´s try a short one….


Jeddah to Jeddah Router: gin-jsd-core1

Site: SA, Jeddah, JSD

Command: traceroute ip 4.69.143.157

Tracing the route to ae-5-6.bar1.Jeddah1.Level3.net (4.69.143.157)

1 195.219.167.42 [MPLS: Label 2414 Exp 0] 52 msec

if-2-0-0.core1.WYN-Marseille.as6453.net (80.231.165.77) [MPLS: Label 2414 Exp 0] 48 msec

195.219.167.42 [MPLS: Label 2414 Exp 0] 48 msec

2 if-1-2-1-29.tcore2.WYN-Marseille.as6453.net (80.231.200.21) [MPLS: Label 785440 Exp 0] 76 msec 80 msec 76 msec

3 if-9-2.tcore2.L78-London.as6453.net (80.231.200.14) [MPLS: Label 682656 Exp 0] 72 msec 72 msec 72 msec

4 if-2-2.tcore1.L78-London.as6453.net (80.231.131.2) [MPLS: Label 616320 Exp 0] 72 msec

if-1-2.tcore1.L78-London.as6453.net (80.231.130.121) [MPLS: Label 616320 Exp 0] 76 msec

if-2-2.tcore1.L78-London.as6453.net (80.231.131.2) [MPLS: Label 616320 Exp 0] 76 msec

5 if-17-2.tcore1.LDN-London.as6453.net (80.231.130.130) 72 msec 72 msec 72 msec

6 195.219.83.102 72 msec 72 msec 72 msec

7 vl-3503-ve-117.csw1.London1.Level3.net (4.69.166.137) [AS 3356] 80 msec

vl-3502-ve-116.csw1.London1.Level3.net (4.69.166.133) [AS 3356] 80 msec

vl-3504-ve-118.csw1.London1.Level3.net (4.69.166.141) [AS 3356] 72 msec

8 ae-56-111.ebr1.London1.Level3.net (4.69.153.113) [AS 3356] 72 msec

ae-58-113.ebr1.London1.Level3.net (4.69.153.121) [AS 3356] 76 msec

ae-57-112.ebr1.London1.Level3.net (4.69.153.117) [AS 3356] 80 msec

9 ae-46-46.ebr1.Paris1.Level3.net (4.69.143.106) [AS 3356] 68 msec 68 msec

ae-47-47.ebr1.Paris1.Level3.net (4.69.143.110) [AS 3356] 72 msec

10 ae-81-81.csw3.Paris1.Level3.net (4.69.161.86) [AS 3356] 68 msec

ae-61-61.csw1.Paris1.Level3.net (4.69.161.78) [AS 3356] 68 msec

ae-91-91.csw4.Paris1.Level3.net (4.69.161.90) [AS 3356] 72 msec

11 ae-93-93.ebr3.Paris1.Level3.net (4.69.161.121) [AS 3356] 68 msec 68 msec

ae-73-73.ebr3.Paris1.Level3.net (4.69.161.113) [AS 3356] 68 msec

12 *

ae-1-7.bar1.Marseille1.Level3.net (4.69.143.237) [AS 3356] 80 msec 84 msec

13 ae-5-6.bar1.Jeddah1.Level3.net (4.69.143.157) [AS 3356] 128 msec 128 msec 128 msec

20.000 km instead of 0128 msec instead of 1

btw: marseille is doinga great job instead ofpassing gibraltar!


And a last one …

Lets try another example:

Try: Tracing from Dubai to Dubai (~ 0 km)

Side A: ANEXIA Dubai

Side B: PCCW Dubai IP 63.218.176.66 (ge5-0-1.var01.dub01.pccwbtn.net)

Expected Runtime: 1 msec


Dubai to Dubai

Traceroute: 63.218.176.66 finished

Hop IP RDNS Location RTT

1 37.252.245.18 cr-01.00-v0-18.anx23.du.ae.anexia-it.com Dubai, United Arab Emirates 0.505 ms 0.569 ms 0.617 ms

2 94.207.34.33 gi12-15.bg1.dx1.datamena.ae United Arab Emirates 0.315 ms 0.312 ms 0.407 ms

3 94.205.255.34 Unknown United Arab Emirates 4.403 ms 4.396 ms 4.385 ms

4 10.44.152.70 Unknown 6.765 ms 6.759 ms 6.783 ms

5 94.201.0.77 Unknown United Arab Emirates 9.547 ms 9.542 ms 9.535 ms

6 10.44.24.102 Unknown 111.248 ms 111.057 ms 111.050 ms

7 116.51.26.81 Unknown Singapore, Singapore 127.901 ms 127.901 ms 127.644 ms

8 129.250.3.88 as-3.r20.snjsca04.us.bb.gin.ntt.net Englewood, United States 297.966 ms 308.808 ms 302.003 ms

9 129.250.5.53 ae-1.r07.snjsca04.us.bb.gin.ntt.net Englewood, United States 315.772 ms 316.022 ms 308.968 ms

10 ? ? ? Timeout

11 63.218.176.37 pos1-1-1.var01.dub01.pccwbtn.net Herndon, United States 429.183 ms


•  All mentioned carriers and hosters are great companies with excellent market positions!

• We did 15 tries and found 10 examples like these

•  It´s not a matter of bad networks – it´s all just a matter of missing peerings (or missing peering possibilities!)

Some notes to the Tests


•  Established in 2012

•  Actually 27 Members

•  Represents 55% of GCC´s Access Users

•  A bit more than 10GBits of Traffic Peak

•  First 100% neutral Internet Exchange

• …. And also open for Tier1´s ;-)

Some facts about UAE-IX


Q & A


JOIN US NOW

www.uae-ix.net

[email protected]

Phone: +971 44524777

Alternative phone: +49 69 1730 902 92

UAE-IX #3 · 2018-01-23 · UAE-IX #18 Jeddah to Jeddah Router: gin-jsd-core1 Site: SA, Jeddah, JSD...

Documents

Transcript of UAE-IX #3 · 2018-01-23 · UAE-IX #18 Jeddah to Jeddah Router: gin-jsd-core1 Site: SA, Jeddah, JSD...