[GTER] Peering entre Oi e Amazon?
Rubens Kuhl
rubensk at gmail.com
Sun Dec 25 21:13:02 -02 2011
Eu gosto da CTBC como trânsito nacional... tem v6, tem boa
conectividade com as teles que não fazem peering, faz peering com os
demais. Para um cliente fortemente outbound como a Amazon seria uma
boa pedida.
Rubens
2011/12/25 Alexandre J. Correa - Onda Internet <alexandre at onda.net.br>:
> sensata decisão !!
>
>
> Em 25/12/2011 17:53, CTBC Telecom escreveu:
>
>> A Amazon decidiu não comprar "trânsito IP" Algar Telecom, mesmo tendo
>> contratado diversos outros produtos.
>>
>>
>> 2011/12/24 Rubens Kuhl<rubensk at gmail.com>
>>
>>> Eu acho muito estranho tráfego CTBC<-> Brasil Telecom não estar pela
>>> interconexão classe V deles:
>>>
>>> Este é um trace no LG da CTBC (origem São Paulo) para o IP de
>>> www.brasiltelecom.com.br:
>>>
>>> 1 ge-5-0-3-1.core-a.spo511.ctbc.com.br (201.48.235.9) 0.547 ms 1.038 ms
>>> 0.541 ms
>>> 2 ge-2-0-0-0.border-a.spo511.ctbc.com.br (201.48.44.89) 0.665 ms 0.652
>>> ms 0.656 ms
>>> 3 200.169.193.89 (200.169.193.89) [AS 8167] 1.132 ms 1.110 ms 0.968 ms
>>> 4 BrT-G6-1-0-spopn309.brasiltelecom.net.br (201.10.241.149) 30.426 ms
>>> 30.596 ms 30.164 ms
>>> 5 BrT-G9-1-1-spopa-core01.brasiltelecom.net.br (201.10.242.81) 32.070
>>> ms BrT-G9-1-1-spopn-core01.brasiltelecom.net.br (201.10.242.57) 30.542
>>> ms BrT-G6-0-1-spopn-core01.brasiltelecom.net.br (201.10.242.49) 30.107
>>> ms
>>> 6 BrT-G11-2-0-bsacocore01.brasiltelecom.net.br (201.10.192.77) 30.172
>>> ms 30.209 ms BrT-G2-1-2-bsacecore01.brasiltelecom.net.br
>>> (201.10.192.153) 36.542 ms
>>> 7 BrT-10GE2-0-0-bsace-border.brasiltelecom.net.br (201.10.211.122)
>>> 30.138 ms Oi-10G9-1-0-etce-df-rotd-01.brasiltelecom.net.br
>>> (201.10.209.46) 32.365 ms
>>> BrT-10GE2-0-0-bsace-border.brasiltelecom.net.br (201.10.211.122)
>>> 30.034 ms
>>> 8 BrTC-G5-2-bsace-core01.brasiltelecom.net.br (200.199.193.106) [AS
>>> 8167] 36.762 ms 30.234 ms 32.147 ms
>>>
>>>
>>> Rubens
>>>
>>> 2011/12/24 Antonio Carlos Pina<antoniocarlospina at gmail.com>:
>>>>
>>>> Nao é questão de uplink. Eles estão no Brasil em parceria com a Algar e
>>>
>>> usando facilities da Terremark e Tivit.
>>>>
>>>> Eles não são carrier-neutral. Sendo assim, a banda será dependente dos
>>>
>>> acordos da Algar.
>>>>
>>>> Nada complicado, mas de fato terá que haver um fine-tunning.
>>>>
>>>> Abs
>>>>
>>>> Em 24/12/2011, às 12:30, Rafael Cresci<cresci at gmail.com> escreveu:
>>>>
>>>>> Pina,
>>>>>
>>>>> Acho que eles não são doidos de ter um unico uplink. Pra quem está em 3
>>>
>>> POPs (TIVIT, CTBC/Campinas e Terremark) justamente por causa da
>>> redundância/availability zones...
>>>>>
>>>>> Rafael-Crescis-MacBook-Pro:~ rafael$ traceroute
>>>
>>> ec2-177-71-156-225.sa-east-1.compute.amazonaws.com
>>>>>
>>>>> traceroute to
>>>>> ec2-177-71-156-225.sa-east-1.compute.amazonaws.com(177.71.156.225), 64 hops
>>>>> max, 52 byte packets
>>>>> 1 192.168.43.1 (192.168.43.1) 1.633 ms 1.271 ms 1.071 ms
>>>>> 2 10.125.81.66 (10.125.81.66) 528.251 ms 129.329 ms 89.616 ms
>>>>> 3 10.125.81.83 (10.125.81.83) 110.221 ms 169.775 ms 407.168 ms
>>>>> 4 10.222.153.219 (10.222.153.219) 253.101 ms 505.447 ms 124.833 ms
>>>>> 5 187.12.161.205 (187.12.161.205) 89.659 ms 135.973 ms 139.474 ms
>>>>> 6 ge-9-0-0-1000-vlm-sp-rotn-01.telemar.net.br (200.164.183.108)
>>>
>>> 91.511 ms 129.697 ms 100.164 ms
>>>>>
>>>>> 7 so-0-1-0-0-arc-rj-rotn-01.telemar.net.br (200.164.197.209) 169.733
>>>
>>> ms 216.855 ms 135.075 ms
>>>>>
>>>>> 8 gigabitethernet8-0-0-arc-rj-rotb-03.telemar.net.br (200.223.45.78)
>>>
>>> 98.533 ms 138.884 ms 183.537 ms
>>>>>
>>>>> 9 gigabitethernet8-0-0-arc-rj-rotb-03.telemar.net.br (200.223.45.78)
>>>
>>> 139.034 ms * *
>>>>>
>>>>> 10 * amazon-com.vlan409.asr1.gru1.gblx.net (159.63.22.122) 115.092
>>>
>>> ms 130.606 ms
>>>>>
>>>>> 11 amazon-com.vlan409.asr1.gru1.gblx.net (159.63.22.122) 139.709 ms
>>>>> 177.72.240.206 (177.72.240.206) 185.947 ms 91.982 ms
>>>>> 12 177.72.240.153 (177.72.240.153) 77.210 ms 139.300 ms 101.521 ms
>>>>> 13 ec2-177-71-128-7.sa-east-1.compute.amazonaws.com (177.71.128.7)
>>>
>>> 117.902 ms 137.164 ms
>>>>>
>>>>> 177.72.240.153 (177.72.240.153) 169.872 ms
>>>>>
>>>>> (o step 1 é meu tablet, que estou compartilhando o 3G via portable wifi
>>>
>>> hotspot, já que destruí meu modem 3G USB ontem de noite num acidente em
>>> plena viagem :-)
>>>>>
>>>>> []s
>>>>> Rafael Cresci
>>>>>
>>>>> On 24/12/2011, at 11:41, Antonio Carlos Pina wrote:
>>>>>
>>>>>> Pode postar o tracert ?
>>>>>>
>>>>>> A principal fornecedora de link da Amazon é a ALGAR.
>>>>>>
>>>>>> Abs
>>>>>>
>>>>>> Em 24 de dezembro de 2011 11:25, Rafael Cresci<cresci at gmail.com>
>>>
>>> escreveu:
>>>>>>>
>>>>>>> Heini,
>>>>>>>
>>>>>>> Estou passando o natal em S. Paulo usando meu 3G da Oi 7738. Ele está
>>>>>>> saindo pela Oi até o Rio e voltando para S. Paulo, via Global
>>>
>>> Crossing, sem
>>>>>>>
>>>>>>> ter de ir a Miami. Latência normal para um 3G.
>>>>>>> Já não tenho como testar o mesmo via BrT...
>>>>>>>
>>>>>>> On 24/12/2011, at 10:53, Heini Thomas Geib wrote:
>>>>>>>
>>>>>>>> Prezados,
>>>>>>>>
>>>>>>>> Alguém sabe se há uma previsão de peering da Oi com a Amazon, ou
>>>
>>> outra
>>>>>>>
>>>>>>> iniciativa que reduza a latência no acesso de clientes Oi à AWS
>>>>>>> (infraestrutura São Paulo)?
>>>>>>>>
>>>>>>>> Vejam o seguinte trace, ruim, a partir de conexão Oi (interior do
>>>
>>> RS):
>>>>>>>>
>>>>>>>> ------------------------------
>>>>>>>> $ mtr -rwo 'A ' -c 100
>>>>>>>
>>>>>>> ec2-177-71-156-225.sa-east-1.compute.amazonaws.com
>>>>>>>>
>>>>>>>> HOST: fw1 Avg
>>>>>>>> 1. rtborda2.unijui.edu.br 0.5
>>>>>>>> 2. 187.4.46.137 2.8
>>>>>>>> 3. BrT-G2-3-0-sance302.brasiltelecom.net.br 25.6
>>>>>>>> 4. BrT-GE-3-0-0-1000-paebv-border.brasiltelecom.net.br 9.9
>>>>>>>> 5. pos13-0.miami2.mia.seabone.net 148.9
>>>>>>>> 6. ge5-1-0.sanpaolo2.spa.seabone.net 263.6
>>>>>>>> 7. amazon.sanpaolo2.spa.seabone.net 152.1
>>>>>>>> 8. 177.72.240.141 152.6
>>>>>>>> 9. 177.72.240.153 152.2
>>>>>>>> 10. ec2-177-71-128-7.sa-east-1.compute.amazonaws.com 152.4
>>>>>>>> 11. ??? 0.0
>>>>>>>> 12. ??? 0.0
>>>>>>>> 13. ??? 0.0
>>>>>>>> 14. ec2-177-71-156-225.sa-east-1.compute.amazonaws.com 152.1
>>>>>>>> ------------------------------
>>>>>>>>
>>>>>>>> Já o trace a partir do Registro.br, excelente:
>>>>>>>> ------------------------------
>>>>>>>> 1 xe-1-0-1.50.ar1.nu.registro.br (200.160.2.1) 0.322
>>>
>>> ms
>>>>>>>>
>>>>>>>> 2 ae0-0.core2.nu.registro.br (200.160.0.252) 0.585
>>>
>>> ms
>>>>>>>>
>>>>>>>> 3 xe-0-0-1-0.gw1.nu.registro.br (200.160.0.169) 0.608
>>>
>>> ms
>>>>>>>>
>>>>>>>> 4 xe-0-2-0-537.edge-c.spo511.ctbc.com.br (187.32.53.70) 0.731
>>>
>>> ms
>>>>>>>>
>>>>>>>> 5 xe-3-0-0-0.core-b.spo511.ctbc.com.br (201.48.44.94) 0.764
>>>
>>> ms
>>>>>>>>
>>>>>>>> 6 ge-3-0-0-0.border-a.spo511.ctbc.com.br (201.48.44.210) 0.967
>>>
>>> ms
>>>>>>>>
>>>>>>>> 7 as16509.sp.ptt.br (187.16.217.20) 1.124
>>>
>>> ms
>>>>>>>>
>>>>>>>> 8 177.72.240.177 (177.72.240.177) 3.824
>>>
>>> ms
>>>>>>>>
>>>>>>>> 9 177.72.240.193 (177.72.240.193) 2.351
>>>
>>> ms
>>>>>>>>
>>>>>>>> 10 ec2-177-71-128-9.sa-east-1.compute.amazonaws.com (177.71.128.9)
>>>>>>>
>>>>>>> 3.120 ms
>>>>>>>>
>>>>>>>> 15
>>>>>>>> ec2-177-71-156-225.sa-east-1.compute.amazonaws.com(177.71.156.225)
>>>>>>>
>>>>>>> 2.432 ms
>>>>>>>>
>>>>>>>> ------------------------------
>>>>>>>>
>>>>>>>> Obrigado,
>>>>>>>> Heini.
>>>>>>>> --
>>>>>>>> gter list https://eng.registro.br/mailman/listinfo/gter
>>>>>>>
>>>>>>> --
>>>>>>> gter list https://eng.registro.br/mailman/listinfo/gter
>>>>>>>
>>>>>> --
>>>>>> gter list https://eng.registro.br/mailman/listinfo/gter
>>>>>
>>>>> --
>>>>> gter list https://eng.registro.br/mailman/listinfo/gter
>>>>
>>>> --
>>>> gter list https://eng.registro.br/mailman/listinfo/gter
>>>
>>> --
>>> gter list https://eng.registro.br/mailman/listinfo/gter
>>>
>> --
>> gter list https://eng.registro.br/mailman/listinfo/gter
>>
>
>
> --
> Sds.
>
> Alexandre Jeronimo Correa
> Socio-Administrador
>
> Onda Internet
> www.onda.net.br
>
> IPV6 Ready !
>
>
> --
> gter list https://eng.registro.br/mailman/listinfo/gter
More information about the gter
mailing list