[GTER] RES: Peering entre Oi e Amazon?

Rafael Moreno rafael.moreno at worldweb.com.br
Mon Dec 26 13:54:49 -02 2011


A NET SPO pelo visto não fechou sessão com a Amazon ainda.

tracert 177.71.156.225

Tracing route to ec2-177-71-156-225.sa-east-1.compute.amazonaws.com [177.71.156.225]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  x.x.x.x [x.x.x.x]
  2    11 ms    11 ms    11 ms  x.x.x.x [x.x.x.x]
  3     9 ms     8 ms    23 ms  spovmnrtd01.virtua.com.br [201.6.0.94]
  4    10 ms    12 ms    11 ms  c90600a3.virtua.com.br [201.6.0.163]
  5    12 ms    10 ms    11 ms  embratel-t0-3-2-0-tacc01.spoph.embratel.net.br [200.178.127.21]
  6    12 ms     9 ms    23 ms  ebt-c1-gacc14.spo.embratel.net.br [200.230.242.58]
  7   109 ms   109 ms   109 ms  64.208.27.225
  8   111 ms   111 ms   112 ms  po3.asr1.gru1.gblx.net [67.16.139.166]
  9   107 ms   110 ms   128 ms  amazon-com.vlan409.asr1.gru1.gblx.net [159.63.22.122]
 10   112 ms   123 ms     *     177.72.240.208
 11   115 ms   113 ms   110 ms  177.72.240.155
 12   112 ms   111 ms   122 ms  ec2-177-71-128-139.sa-east-1.compute.amazonaws.com [177.71.128.139]
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17   113 ms   110 ms   112 ms  ec2-177-71-156-225.sa-east-1.compute.amazonaws.com [177.71.156.225]

Trace complete.

-----Mensagem original-----
De: gter-bounces at eng.registro.br [mailto:gter-bounces at eng.registro.br] Em nome de Felipe Da Cruz
Enviada em: Monday, December 26, 2011 12:11 PM
Para: Grupo de Trabalho de Engenharia e Operacao de Redes
Assunto: Re: [GTER] Peering entre Oi e Amazon?

Teste de POA usando um upstream que faz peering com a Amazon.

PING 177.71.156.225 (177.71.156.225) 56(84) bytes of data.
64 bytes from 177.71.156.225: icmp_seq=1 ttl=55 time=18.7 ms
64 bytes from 177.71.156.225: icmp_seq=2 ttl=55 time=18.6 ms
64 bytes from 177.71.156.225: icmp_seq=3 ttl=55 time=18.7 ms
64 bytes from 177.71.156.225: icmp_seq=4 ttl=55 time=18.4 ms
64 bytes from 177.71.156.225: icmp_seq=5 ttl=55 time=18.5 ms

traceroute to 177.71.156.225 (177.71.156.225), 30 hops max, 40 byte packets
 1   xxxx  ( xxxx )  0.122 ms  0.106 ms  0.101 ms
 2  xxxx ( xxxx )  0.280 ms  0.280 ms  0.283 ms
 3  as16509.sp.ptt.br (187.16.217.20)  15.775 ms  15.775 ms  15.769 ms
 4  177.72.240.177 (177.72.240.177)  18.244 ms  18.251 ms  18.175 ms
 5  177.72.240.195 (177.72.240.195)  18.107 ms  18.048 ms  18.017 ms
 6  ec2-177-71-128-141.sa-east-1.compute.amazonaws.com (177.71.128.141)
 17.975 ms  18.504 ms  18.909 ms
 7  ec2-177-71-156-225.sa-east-1.compute.amazonaws.com (177.71.156.225)
 18.850 ms  19.111 ms  18.737 ms

2011/12/24 Heini Thomas Geib <heini at unijui.edu.br>

> 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<http://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<http://BrT-G2-3-0-sance302.brasiltelecom.net.br>            25.6
>  4. BrT-GE-3-0-0-1000-paebv-**border.brasiltelecom.net.br<http://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<http://ge5-1-0.sanpaolo2.spa.seabone.net>                  263.6
>  7. amazon.sanpaolo2.spa.seabone.**net<http://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<http://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<http://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<http://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<http://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<http://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<http://ec2-177-71-1
> 28-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<http://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<https://eng.registro.br/mailman/listinfo/gter>
>
--
gter list    https://eng.registro.br/mailman/listinfo/gter



More information about the gter mailing list