Resultados 1 a 6 de 6
  1. #1
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    15,000

    Akamai expande presença na América Latina

    A Akamai está abrindo um centro de serviços e suporte em San Jose, Costa Rica, parte de um plano de expansão para comercializar seus produtos na América Latina, aonde já possui presença local na Argentina, Brasil, Chile, Colombia, Mexico, e Peru. Ilustra o aumento da demanda na região citando um aumento de 40% de IPs servidos no Brasil pela empresa.

    http://www.telecomramblings.com/2012/10/akamai-expands-to-latin-america

  2. #2
    Louco pelo WHT Brasil
    Data de Ingresso
    Dec 2011
    Posts
    168
    Aqui no Brasil só recebo conteúdo da Akamai de servidores do Brasil se estou no Virtua ou na GVT. Das demais grandes redes como CTBC, Oi, Telefonica e TIM (Intelig) o conteúdo ou vem dos EUA ou do Chile, por IPs que num olhar rápido parecem por IPs brasileiros por começar com 200.*

    Já tinha ouvido falar que algumas operadoras/telcos brasileiras estavam convidando a Akamai e outros caches a saírem (incluindo Google) pois se deram conta que essas empresas ganham bilhões com sua base de assinantes banda larga e não molham a mão da operadora. Postura essa que a Embratel sempre teve, incluindo sendo avessa a peering no PTT.

  3. #3
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    15,000
    C:\>tracert www.estadao.com.br
    Tracing route to a1638.g.akamai.net [201.20.244.42]
    over a maximum of 30 hops:
    1 2 ms 2 ms 3 ms 192.168.1.1
    2 * * * Request timed out.
    3 33 ms 31 ms 32 ms 201-0-85-9.dsl.telesp.net.br [201.0.85.9]
    4 31 ms 31 ms 32 ms 200-100-3-221.dsl.telesp.net.br [200.100.3.221]
    5 31 ms 32 ms 48 ms 187-100-58-65.dsl.telesp.net.br [187.100.58.65]
    6 32 ms 32 ms 34 ms 201-0-5-190.dsl.telesp.net.br [201.0.5.190]
    7 31 ms * 31 ms 186.238.142.2
    8 31 ms 34 ms 32 ms 201.20.244.42.user.ajato.com.br [201.20.244.42]
    Trace complete.



    root@sp4:~# traceroute www.estadao.com.br
    traceroute to www.estadao.com.br (200.123.198.154), 30 hops max, 60 byte packets
    1 ip-10-2-3-129.sa-east-1.compute.internal (10.2.3.129) 7.636 ms 7.897 ms 8.156 ms
    2 ip-10-0-32-57.sa-east-1.compute.internal (10.0.32.57) 0.355 ms 0.431 ms ip-10-0-34-57.sa-east-
    1.compute.internal (10.0.34.57) 6.770 ms
    3 ip-10-1-6-1.sa-east-1.compute.internal (10.1.6.1) 0.481 ms ip-10-1-10-1.sa-east-1.compute.inter
    nal (10.1.10.1) 0.564 ms ip-10-1-4-1.sa-east-1.compute.internal (10.1.4.1) 0.452 ms
    4 ip-10-1-11-253.sa-east-1.compute.internal (10.1.11.253) 0.610 ms ip-10-1-5-253.sa-east-1.comput
    e.internal (10.1.5.253) 0.529 ms ip-10-1-7-253.sa-east-1.compute.internal (10.1.7.253) 0.540 ms
    5 ec2-177-71-128-10.sa-east-1.compute.amazonaws.com (177.71.128.10) 0.605 ms ec2-177-71-128-8.sa-
    east-1.compute.amazonaws.com (177.71.128.8) 0.384 ms ec2-177-71-128-10.sa-east-1.compute.amazonaws.
    com (177.71.128.10) 0.583 ms
    6 177.72.240.192 (177.72.240.192) 1.569 ms 1.234 ms 177.72.240.152 (177.72.240.152) 0.591 ms
    7 177.72.240.180 (177.72.240.180) 1.302 ms 1.241 ms 1.319 ms
    8 ge13-0-0-3301.sanpaolo1.spa.seabone.net (195.22.219.138) 2.875 ms xe-0-1-0-3000.sanpaolo8.spa.s
    eabone.net (195.22.219.136) 1.043 ms ge13-0-0-3301.sanpaolo1.spa.seabone.net (195.22.219.138) 3.06
    8 ms
    9 200.123.198.154 (200.123.198.154) 3.341 ms 3.323 ms ge5-1-0.sanpaolo1.spa.seabone.net (195.22.
    219.173) 2.038 ms
    root@sp4:~#

    root@sp4:~# traceroute a1638.g.akamai.net
    traceroute to a1638.g.akamai.net (200.123.198.154), 30 hops max, 60 byte packets
    1 ip-10-2-3-129.sa-east-1.compute.internal (10.2.3.129) 0.882 ms 3.758 ms 4.017 ms
    2 ip-10-0-34-57.sa-east-1.compute.internal (10.0.34.57) 0.507 ms 0.611 ms 0.698 ms
    3 ip-10-1-8-1.sa-east-1.compute.internal (10.1.8.1) 0.524 ms ip-10-1-10-1.sa-east-1.compute.inter
    nal (10.1.10.1) 0.632 ms ip-10-1-8-1.sa-east-1.compute.internal (10.1.8.1) 0.473 ms
    4 ip-10-1-9-253.sa-east-1.compute.internal (10.1.9.253) 0.712 ms 0.712 ms ip-10-1-7-253.sa-east-
    1.compute.internal (10.1.7.253) 0.547 ms
    5 ec2-177-71-128-12.sa-east-1.compute.amazonaws.com (177.71.128.12) 0.319 ms ec2-177-71-128-10.sa
    -east-1.compute.amazonaws.com (177.71.128.10) 0.384 ms ec2-177-71-128-6.sa-east-1.compute.amazonaws
    .com (177.71.128.6) 0.774 ms
    6 177.72.240.192 (177.72.240.192) 1.205 ms 1.572 ms 1.155 ms
    7 177.72.240.180 (177.72.240.180) 1.262 ms 1.473 ms 177.72.240.140 (177.72.240.140) 0.734 ms
    8 ge13-0-0-3301.sanpaolo1.spa.seabone.net (195.22.219.138) 2.763 ms 2.604 ms 2.805 ms
    9 200.123.198.154 (200.123.198.154) 3.343 ms 3.349 ms 3.328 ms
    root@sp4:~#



    http://just-ping.com/index.php?vh=ww...r&c=&s=ping%21

    Amsterdam2, Netherlands: Okay 0.9 1.1 1.2 89.149.151.187
    Florida, U.S.A.: Okay 9.0 9.1 9.2 64.56.95.232
    Amsterdam3, Netherlands: Okay 0.7 0.9 1.5 23.62.99.49
    Sydney, Australia: Okay 0.6 0.7 1.1 119.161.91.19
    New York, U.S.A.: Okay 0.6 0.7 0.7 66.152.103.75
    Stockholm, Sweden: Okay 5.5 5.6 5.6 93.158.110.216
    Santa Clara, U.S.A.: Okay 5.5 6.0 8.3 69.22.138.34
    Vancouver, Canada: Okay 0.9 1.0 1.5 216.113.197.198
    London, United Kingdom: Okay 1.4 1.8 2.3 84.53.134.137
    Madrid, Spain: Okay 14.5 14.6 14.7 213.248.113.16
    Padova, Italy: Okay 0.6 0.8 1.0 46.40.191.18
    Singapore, Singapore: Okay 1.8 3.6 5.8 124.155.223.16
    Austin, U.S.A.: Okay 6.4 6.7 7.5 174.76.226.25
    Cologne, Germany: Okay 3.4 3.6 3.9 92.122.50.161
    München, Germany: Okay 7.1 7.3 7.9 194.25.95.104
    Amsterdam, Netherlands: Okay 1.0 1.1 1.1 89.149.151.200
    Shanghai, China: Okay 29.5 30.0 30.6 219.76.10.145
    Hong Kong, China: Okay 1.6 1.8 2.6 219.76.10.152
    Melbourne, Australia: Okay 1.4 4.2 12.7 125.255.240.10
    Copenhagen, Denmark: Okay 0.2 0.3 0.3 87.72.143.72
    Lille, France: Okay 25.0 25.1 25.2 80.157.149.42
    San Francisco, U.S.A.: Checkpoint temporarily not available - - - -
    Zurich, Switzerland: Okay 2.1 2.3 2.4 95.100.255.18
    Mumbai, India: Okay 3.7 6.1 9.8 49.248.249.17
    Auckland, New Zealand: Okay 1.5 1.6 1.6 202.49.135.106
    Groningen, Netherlands: Okay 5.6 5.6 5.7 62.41.80.26
    Antwerp, Belgium: Okay 3.2 3.2 3.4 77.109.170.65
    Dublin, Ireland: Okay 0.7 0.8 0.9 193.1.253.145
    Moscow, Russia: Okay 17.5 17.8 20.1 193.184.164.175
    Kharkov, Ukraine: Okay 28.0 28.0 28.0 87.245.209.169
    Manchester, United Kingdom: Okay 3.2 3.4 3.9 213.249.233.209
    Vilnius, Lithuania: Okay 5.9 6.0 6.3 159.148.86.199
    Bucharest, Romania: Okay 0.2 0.4 0.5 89.114.195.33
    Bangkok, Thailand: Checkpoint temporarily not available - - - -
    Kuala Lumpur, Malaysia: Okay 2.1 2.7 3.7 203.92.134.137
    Jakarta, Indonesia: Okay 1.2 1.6 2.9 223.255.230.136
    Cape Town, South Africa: Okay 0.8 0.9 1.0 197.84.130.24
    Glasgow, United Kingdom: Okay 1.4 1.5 1.7 84.53.134.145
    Lisbon, Portugal: Okay 5.9 5.9 6.0 212.113.184.43
    Chicago, U.S.A.: Okay 1.8 2.3 3.0 208.59.255.145
    Dallas, U.S.A.: Okay 1.6 1.7 1.9 69.31.49.48
    Amsterdam1, Netherlands: Okay 0.9 0.9 0.9 89.149.151.187
    Istanbul, Turkey: Okay 1.6 1.7 1.9 195.175.70.18
    Gdansk, Poland: Okay 6.6 6.7 6.8 217.153.56.72
    Cairo, Egypt: Okay 27.7 28.1 29.0 79.140.95.153
    Beijing, China: checking...
    Buenos Aires, Argentina: Okay 22.3 22.5 22.8 200.123.201.147
    Belgrade, Serbia: Okay 0.8 0.9 0.9 213.240.44.138
    Toronto, Canada: Okay 1.7 2.1 2.5 216.154.11.42
    Athens, Greece: Okay 1.6 1.6 1.7 212.205.43.16
    Frankfurt, Germany: Okay 6.2 6.2 6.2 80.157.149.58
    Sofia, Bulgaria: Okay 0.7 1.0 1.2 85.14.5.169
    Budapest, Hungary: Okay 0.9 4.2 26.9 217.79.128.200
    Sao Paulo, Brazil: Okay 2.6 2.7 2.8 200.123.198.137
    Paris, France: Okay 0.8 0.9 1.1 88.221.15.80
    Mumbai, India: Okay 2.9 3.2 4.9 49.248.249.17
    New Delhi, India: Okay 2.3 2.6 3.2 96.17.182.11
    Chicago, U.S.A.: Okay 1.0 1.3 1.4 208.59.255.147
    Bangalore, India: Okay 1.6 3.4 7.7 184.26.162.49
    Montreal, Canada: Okay 1.3 1.3 1.5 24.200.239.48
    Tokyo, Japan: Okay 1.7 2.0 2.2 23.32.241.51



    http://just-ping.com/index.php?vh=+a...t&c=&s=ping%21


    Amsterdam2, Netherlands: Okay 1.0 1.1 1.2 89.149.151.187
    Florida, U.S.A.: Okay 9.1 9.1 9.2 64.56.95.233
    Amsterdam3, Netherlands: Okay 0.7 1.5 7.8 23.62.99.49
    Sydney, Australia: Okay 0.6 0.8 1.1 119.161.91.25
    New York, U.S.A.: Okay 0.6 0.7 0.7 66.152.103.80
    Stockholm, Sweden: Okay 5.6 5.6 5.7 93.158.111.9
    Santa Clara, U.S.A.: Okay 4.3 5.0 7.0 69.22.138.18
    Vancouver, Canada: Okay 0.9 1.1 1.4 216.113.197.199
    London, United Kingdom: Okay 1.4 1.8 2.1 84.53.134.145
    Madrid, Spain: Okay 14.5 14.6 14.8 213.248.113.11
    Padova, Italy: Packets lost (10%) 0.7 0.9 1.0 46.40.191.18
    Singapore, Singapore: Okay 1.5 2.5 8.5 124.155.223.17
    Austin, U.S.A.: Okay 6.4 6.7 7.3 174.76.226.25
    Cologne, Germany: Okay 3.4 3.6 3.8 92.122.50.161
    München, Germany: Okay 7.1 7.2 7.4 194.25.95.104
    Amsterdam, Netherlands: Okay 1.0 1.4 3.6 89.149.151.200
    Shanghai, China: Okay 23.8 24.3 24.8 61.111.58.153
    Hong Kong, China: Okay 1.9 2.3 2.9 60.254.131.72
    Melbourne, Australia: Okay 1.4 2.1 5.4 125.255.240.10
    Copenhagen, Denmark: Okay 0.2 0.3 0.3 87.72.143.74
    Lille, France: Okay 23.9 24.1 24.2 80.157.149.58
    San Francisco, U.S.A.: Checkpoint temporarily not available - - - -
    Zurich, Switzerland: Okay 2.1 2.2 2.3 95.100.255.18
    Mumbai, India: Okay 3.8 5.7 7.4 49.248.249.17
    Auckland, New Zealand: Okay 1.4 1.6 1.9 202.49.135.106
    Groningen, Netherlands: Okay 5.4 5.6 5.6 62.41.80.18
    Antwerp, Belgium: Okay 3.2 3.2 3.3 88.221.216.59
    Dublin, Ireland: Okay 0.7 0.8 0.9 193.1.253.145
    Moscow, Russia: Okay 17.5 17.5 17.6 193.184.164.175
    Kharkov, Ukraine: Okay 28.0 28.4 32.0 87.245.209.170
    Manchester, United Kingdom: Okay 3.0 3.1 3.4 213.249.233.208
    Vilnius, Lithuania: Okay 5.8 5.9 6.0 159.148.86.201
    Bucharest, Romania: Okay 0.3 0.4 0.6 89.114.195.33
    Bangkok, Thailand: checking...
    Kuala Lumpur, Malaysia: Okay 2.0 2.6 4.8 203.92.134.137
    Jakarta, Indonesia: Okay 1.2 1.5 2.2 223.255.230.144
    Cape Town, South Africa: Okay 0.7 0.8 0.9 197.84.130.24
    Glasgow, United Kingdom: Okay 1.4 1.4 1.5 84.53.134.145
    Lisbon, Portugal: Okay 6.8 7.1 9.8 212.113.184.35
    Chicago, U.S.A.: Okay 1.9 2.2 2.8 208.59.255.145
    Dallas, U.S.A.: Okay 1.7 1.7 1.8 69.31.49.42
    Amsterdam1, Netherlands: Okay 0.9 0.9 0.9 89.149.151.187
    Istanbul, Turkey: Okay 0.4 0.4 0.5 195.175.68.137
    Gdansk, Poland: Okay 6.7 6.7 6.8 217.153.56.72
    Cairo, Egypt: Okay 27.6 27.9 28.5 79.140.95.153
    Beijing, China: Unknown host: a1638.g.akamai.net
    Buenos Aires, Argentina: Okay 21.3 21.5 22.3 200.123.201.154
    Belgrade, Serbia: Okay 0.8 1.2 4.1 213.240.44.138
    Toronto, Canada: Okay 1.9 2.3 2.6 216.154.11.40
    Athens, Greece: Okay 1.6 1.7 1.7 212.205.43.6
    Frankfurt, Germany: Okay 5.9 6.0 6.0 80.157.149.42
    Sofia, Bulgaria: Okay 0.7 0.9 1.2 85.14.5.169
    Budapest, Hungary: Okay 0.9 1.0 1.2 217.79.128.202
    Sao Paulo, Brazil: Okay 2.7 2.7 2.9 200.123.198.137
    Paris, France: Okay 0.8 0.9 1.0 88.221.15.80
    Mumbai, India: Okay 2.3 2.8 4.8 49.248.249.11
    New Delhi, India: Okay 2.1 2.6 2.9 96.17.182.16
    Chicago, U.S.A.: Okay 1.0 1.3 1.9 208.59.255.145
    Bangalore, India: Okay 1.6 2.1 5.7 184.26.162.49
    Montreal, Canada: Okay 1.3 1.3 1.4 24.200.239.48
    Tokyo, Japan: Okay 1.4 1.6 1.8 23.32.241.19
    Última edição por 5ms; 04-10-2012 às 02:52.

  4. #4
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    15,000
    Amazon SP

    root@sp4:~# nslookup www.estadao.com.br
    Server: 172.16.0.23
    Address: 172.16.0.23#53
    Non-authoritative answer:
    www.estadao.com.br canonical name = estadao.edgesuite.net.
    estadao.edgesuite.net canonical name = a1638.g.akamai.net.
    Name: a1638.g.akamai.net
    Address: 200.123.198.137
    Name: a1638.g.akamai.net
    Address: 200.123.198.154

    Speedy SP


    C:\>nslookup www.estadao.com.br
    Server: resolver1.telesp.net.br
    Address: 200.204.0.10
    Non-authoritative answer:
    Name: a1638.g.akamai.net
    Addresses: 201.95.254.216
    201.95.254.210
    Aliases: www.estadao.com.br
    estadao.edgesuite.net

    C:\>

  5. #5
    Louco pelo WHT Brasil
    Data de Ingresso
    Dec 2011
    Posts
    168
    Excelentes resultados 5ms. Totalmente diferente do que eu obtive nos últimos meses. Quando tiver acesso a outras conexões repetirei as checagens.

  6. #6
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    15,000
    Talvez a situação que você reportou seja devido ao uso de um servidor DNS no exterior, o que ocorre, por exemplo, quando os clientes da Vivo (Telefonica) usam o Google Public DNS (8.8.8.8,8.8.4.4):

    C:\>nslookup www.estadao.com.br
    Server: google-public-dns-a.google.com
    Address: 8.8.8.8
    Non-authoritative answer:
    Name: a1638.g.akamai.net
    Addresses: 208.44.23.144
    208.44.23.122
    Aliases: www.estadao.com.br
    estadao.edgesuite.net

    C:\>tracert www.estadao.com.br
    Tracing route to a1638.g.akamai.net [208.44.23.122]
    over a maximum of 30 hops:
    1 8 ms 2 ms 3 ms 192.168.1.1
    2 * * * Request timed out.
    3 32 ms 65 ms 34 ms 201-0-85-9.dsl.telesp.net.br [201.0.85.9]
    4 81 ms 36 ms 32 ms 200-148-89-53.dsl.telesp.net.br [200.148.89.53]
    5 33 ms 32 ms 32 ms 187-100-57-77.dsl.telesp.net.br [187.100.57.77]
    6 33 ms 36 ms 32 ms GRTSANEM1-et-13-0-0-0-101-TELESP.50.140.213.in-addr.arpa [213.140.50
    .9]
    7 141 ms 141 ms 146 ms Xe-7-2-0-0-grtmiabr4.red.telefonica-wholesale.net [94.142.126.38]
    8 168 ms 178 ms 177 ms Xe7-1-0-0-grtwaseq4.red.telefonica-wholesale.net [94.142.122.157]
    9 169 ms 170 ms 204 ms Xe7-1-0-0-grtwaseq4.red.telefonica-wholesale.net [94.142.122.157]
    10 194 ms 199 ms 195 ms atl-pcor-05.inet.qwest.net [67.14.14.174]
    11 193 ms 195 ms 197 ms 208-44-23-122.dia.static.qwest.net [208.44.23.122]
    Trace complete.
    C:\>


    C:\>tracert 8.8.8.8
    Tracing route to google-public-dns-a.google.com [8.8.8.8]
    over a maximum of 30 hops:
    1 3 ms 2 ms 2 ms 192.168.1.1
    2 * * * Request timed out.
    3 61 ms 30 ms 32 ms 187-100-60-97.dsl.telesp.net.br [187.100.60.97]
    4 33 ms 128 ms 35 ms 200-148-89-49.dsl.telesp.net.br [200.148.89.49]
    5 33 ms 75 ms 31 ms 187-100-52-217.dsl.telesp.net.br [187.100.52.217]
    6 44 ms 48 ms 42 ms et1-0-0-100-GRTRIOTW1.51.140.213.in-addr.arpa [213.140.51.137]
    7 143 ms 144 ms 264 ms 176.52.248.66
    8 143 ms 144 ms 144 ms Xe6-1-2-0-grtmiana3.red.telefonica-wholesale.net [213.140.43.121]
    9 155 ms 167 ms 154 ms GOOGLE-xe-6-1-0-0-grtmiana3.red.telefonica-wholesale.net [84.16.6.11
    8]
    10 160 ms 157 ms 160 ms 209.85.253.118
    11 * 172 ms 175 ms 209.85.254.252
    12 170 ms 192 ms 193 ms 72.14.239.65
    13 172 ms 176 ms 174 ms 209.85.252.25
    14 * * 182 ms 64.233.174.182
    15 172 ms 184 ms 178 ms google-public-dns-a.google.com [8.8.8.8]
    Trace complete.
    C:\>


    Uma outra hipótese, não sei se possivel, seria determinado site contratar os serviços da Akamai de forma limitada, sem utilizar edge cache servers em cada network/país. Como eu uso sempre o site do Estadão para checar a Akamai e a cobertura sempre foi global, não sei se existem opções mais economicas.
    Última edição por 5ms; 04-10-2012 às 10:25.

Permissões de Postagem

  • Você não pode iniciar novos tópicos
  • Você não pode enviar respostas
  • Você não pode enviar anexos
  • Você não pode editar suas mensagens
  •