Página 1 de 2 12 ÚltimoÚltimo
Resultados 1 a 10 de 15
  1. #1
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    14,999

    Linode Datacenter Expansion

    Happy New Year! 2014 was a great year at Linode and we’re very excited about all the projects we have planned for 2015. Here’s a sneak peek at our datacenter expansion plans.

    Singapore, SG

    First, we’ll be expanding our presence in the Asia-Pacific region with a datacenter in Singapore. This new deployment will support all of the existing Linode services, including NodeBalancers, Backups, native IPv6, and features our latest generation SSD-based servers and 40 Gbit connectivity to each host machine. The facility will be a fantastic alternative/complement to our Tokyo location, with great connectivity to Australia, China, Hong Kong, India and the rest of Asia.
    All of the networking and server hardware has been installed, and our team should have Singapore ready for customer Linodes in the next few weeks!

    Frankfurt, Germany

    We’re also expanding our European footprint with a deployment into Frankfurt, Germany. This will complement our UK-based facility. Interestingly, more than 35% of all European cloud traffic flows through Frankfurt and this location will enable customers to comply with Germany’s Federal Data Protection Act (a.k.a., Bundesdatenschutzgesetz (BDSG)) by hosting their data on German soil. Frankfurt is also centrally located in continental Europe, and we believe this will be a great location for all of Europe.
    The Linode Frankfurt deployment will be coming in the next few months.

    Tokyo, Japan

    Our Tokyo facility has been a great success. So much so that we’ve actually exhausted all of the resources available there. Linodes in Tokyo are in limited supply and the datacenter is frequently sold out. While Singapore will be an excellent alternative for a presence in this region, we are also exploring a second Tokyo datacenter.
    Stay tuned for the official announcements of these new locations and several other exciting developments coming soon!
    https://blog.linode.com/2015/01/16/l...ter-expansion/

  2. #2
    Web Hosting Master
    Data de Ingresso
    Apr 2012
    Posts
    667
    por falar em linode, a minha rota até dallas está indo por lax e o ping beirando os 230ms.. mais alguém com esse problema?

  3. #3
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    14,999
    1 1 ms 1 ms 1 ms 192.168.1.1
    2 * * * Request timed out.
    3 55 ms 81 ms 31 ms 201-0-92-173.dsl.telesp.net.br [201.0.92.173]
    4 32 ms 42 ms 33 ms 200-148-89-49.dsl.telesp.net.br [200.148.89.49]
    5 31 ms 32 ms 79 ms 187-100-34-157.dsl.telesp.net.br [187.100.34.157]
    6 44 ms 80 ms 56 ms GRTSANEM1-et-14-0-0-0-100-TELESP.red.telefonica-wholesale.net [84.16.9.109]
    7 180 ms 156 ms 151 ms Te0-7-0-5-grtmiabr6.red.telefonica-wholesale.net [94.142.123.254]
    8 151 ms * * Hu-1-5-0-0-4-grtmiabr6.red.telefonica-wholesale.net [84.16.15.128]
    9 151 ms 165 ms 162 ms et2-0-0-0-grtmiana2.red.telefonica-wholesale.net [84.16.14.189]
    10 153 ms 152 ms 158 ms ae7.bbr01.tm01.mia01.networklayer.com [173.192.18.174]
    11 179 ms 147 ms 149 ms ae7.bbr01.tm01.mia01.networklayer.com [173.192.18.174]
    12 178 ms 177 ms 180 ms ae1.bbr01.sr02.hou02.networklayer.com [173.192.18.162]
    13 185 ms 178 ms 179 ms po31.dsr02.dllstx3.networklayer.com [173.192.18.227]
    14 180 ms 181 ms 174 ms po31.dsr02.dllstx3.networklayer.com [173.192.18.227]
    15 176 ms 179 ms 175 ms po32.dsr02.dllstx2.networklayer.com [70.87.255.70]
    16 175 ms 176 ms 178 ms po2.car01.dllstx2.networklayer.com [70.87.254.78]
    17 176 ms 183 ms 176 ms router1-dal.linode.com [67.18.7.90]

  4. #4
    Web Hosting Master
    Data de Ingresso
    Apr 2012
    Posts
    667
    mistério... isso acontece a alguns dias..

    4 9 ms 7 ms 8 ms 187.115.223.205.static.host.gvt.net.br [187.115.223.205]
    5 7 ms 7 ms 6 ms gvt-te-0-3-0-11.rc03.cta.gvt.net.br [179.185.103.114]
    6 15 ms 15 ms 15 ms gvt-te-0-5-0-11.rc02.spo.gvt.net.br [187.115.219.78]
    7 14 ms 14 ms 15 ms gvt-te-0-1-1-0.rt01.spo.gvt.net.br [187.115.214.186]
    8 21 ms 13 ms 12 ms xe-3-1-1.ar4.gru1.gblx.net [64.210.21.109]
    9 120 ms 120 ms 119 ms po3-20G.ar3.MIA2.gblx.net [67.17.75.66]
    10 132 ms 131 ms 132 ms ae5.edge2.miami2.level3.net [4.68.111.121]
    11 182 ms 181 ms * ae-4-90.edge1.LosAngeles6.Level3.net [4.69.144.208]
    12 180 ms 181 ms 181 ms ae-4-90.edge1.LosAngeles6.Level3.net [4.69.144.208]
    13 184 ms 182 ms 180 ms te2-5.bbr01.cs01.lax01.networklayer.com [4.26.0.70]
    14 183 ms 183 ms 181 ms ae7.bbr01.cs01.lax01.networklayer.com [173.192.18.166]
    15 181 ms 180 ms 181 ms ae19.bbr01.eq01.dal03.networklayer.com [173.192.18.140]
    16 184 ms 183 ms 181 ms po31.dsr02.dllstx3.networklayer.com [173.192.18.227]
    17 182 ms 182 ms 183 ms po31.dsr01.dllstx2.networklayer.com [70.87.255.66]
    18 181 ms 181 ms 181 ms po1.car02.dllstx2.networklayer.com [70.87.254.82]
    19 182 ms 182 ms 182 ms router2-dal.linode.com [67.18.7.94]

  5. #5
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    14,999
    O traceroute é RTT de n rotas (nos dois sentidos) para pacotes ICMP. Note que não é possivel você ter 180ms até LA e os mesmos 180ms para Dallas se o pacote tivesse passado por LA nos 2 sentidos.

    Um possibilidade seria:

    BR -> LA 90 ms
    LA -> TX 15 ms
    TX -> BR 75 ms

    Como fica o traceroute a partir de Dallas?

    Experimente com TCP.
    Última edição por 5ms; 25-01-2015 às 10:57.

  6. #6
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    14,999
    Curiosamente, o traceroute da Telefonica para o roteador da Level 3 em LA passa por Dallas

    E o seu traceroute não mostra interconexão em Miami com a SoftLayer.


    Tracing route to ae-4-90.edge1.LosAngeles6.Level3.net [4.69.144.208]
    over a maximum of 30 hops:

    1 1 ms 1 ms 10 ms 192.168.1.1
    2 * * * Request timed out.
    3 32 ms 31 ms 32 ms 201-0-85-9.dsl.telesp.net.br [201.0.85.9]
    4 31 ms 32 ms 43 ms 200-100-3-221.dsl.telesp.net.br [200.100.3.221]
    5 31 ms 34 ms 31 ms 187-100-34-149.dsl.telesp.net.br [187.100.34.149]
    6 48 ms 48 ms 61 ms et-6-0-0-100-GRTRIOTW2.red.telefonica-wholesale.net [84.16.9.61]
    7 152 ms 151 ms 155 ms Hu1-1-0-0-0-grtmiabr6.red.telefonica-wholesale.net [5.53.3.149]
    8 164 ms 165 ms 152 ms et2-0-0-0-grtmiana2.red.telefonica-wholesale.net [84.16.14.189]
    9 157 ms 153 ms 156 ms Hu-0-11-0-0-grtmiana4.red.telefonica-wholesale.net [84.16.12.238]
    10 * 152 ms 163 ms xe-4-3-1.edge1.Miami2.Level3.net [4.71.208.21]
    11 155 ms 153 ms 155 ms ae-31-51.ebr1.Miami1.Level3.net [4.69.138.91]
    12 181 ms 187 ms 183 ms ae-2-2.ebr1.Dallas1.Level3.net [4.69.140.133]
    13 233 ms 180 ms 191 ms ae-61-61.csw1.Dallas1.Level3.net [4.69.151.125]
    14 188 ms 220 ms 192 ms ae-63-63.ebr3.Dallas1.Level3.net [4.69.151.134]
    15 216 ms 216 ms 214 ms ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]
    16 215 ms 238 ms 214 ms ae-92-92.csw4.LosAngeles1.Level3.net [4.69.137.30]
    17 213 ms 216 ms 216 ms ae-4-90.edge1.LosAngeles6.Level3.net [4.69.144.208]

    Trace complete.
    Última edição por 5ms; 25-01-2015 às 11:12.

  7. #7
    Web Hosting Master
    Data de Ingresso
    Apr 2012
    Posts
    667
    Citação Postado originalmente por 5ms Ver Post
    Como fica o traceroute a partir de Dallas?
    não vai até a outra costa.. mas o ping tá bem alto

    traceroute to 187.115.211.225 (187.115.211.225), 30 hops max, 60 byte packets
    1 router2-dal.linode.com (67.18.7.162) 0.400 ms 0.555 ms 0.706 ms
    2 ae2.car02.dllstx2.networklayer.com (67.18.7.93) 0.248 ms 0.235 ms 0.209 ms
    3 po102.dsr02.dllstx2.networklayer.com (70.87.254.85) 0.929 ms 0.909 ms 0.992 ms
    4 po22.dsr02.dllstx3.networklayer.com (70.87.255.69) 0.830 ms 0.816 ms 0.839 ms
    5 ae17.bbr02.eq01.dal03.networklayer.com (173.192.18.230) 0.505 ms 0.464 ms ae17.bbr01.eq01.dal03.networklayer.com (173.192.18.226) 0.407 ms
    6 ae-11.r01.dllstx04.us.bb.gin.ntt.net (157.238.224.229) 2.246 ms 1.035 ms 1.062 ms
    7 ae-5.r08.dllstx09.us.bb.gin.ntt.net (129.250.3.232) 1.082 ms ae-1.r08.dllstx09.us.bb.gin.ntt.net (129.250.3.27) 1.154 ms 0.967 ms
    8 ae-0.globalcrossing.dllstx09.us.bb.gin.ntt.net (129.250.8.14) 34.289 ms 34.268 ms 34.199 ms
    9 ae1-100G.ar4.GRU1.gblx.net (67.16.148.10) 256.990 ms * *
    10 159.63.22.102 (159.63.22.102) 261.421 ms global-village-telecom-ltda.xe-1-0-2.ar4.gru1.gblx.net (64.214.145.50) 243.259 ms 194.6.125.189.static.impsat.net.br (189.125.6.194) 230.239 ms
    11 gvt-te-0-4-0-6.rc02.spo.gvt.net.br (187.115.218.166) 241.194 ms * gvt-te-0-6-0-0.rc01.spo.gvt.net.br (189.59.242.182) 238.176 ms
    12 gvt-te-0-10-0-11.rc03.cta.gvt.net.br (189.59.247.74) 254.256 ms gvt-te-0-8-0-6.rc03.cta.gvt.net.br (187.115.219.73) 273.668 ms 265.759 ms
    13 gvt-te-0-6-0-0.rc01.cta.gvt.net.br (189.59.247.38) 264.729 ms 268.591 ms 268.547 ms
    14 gvt-te-2-2.rd02.cta.gvt.net.br (187.115.213.42) 246.111 ms 230.088 ms 237.441 ms
    15 gvt-b-se03.cta.gvt.net.br (187.115.211.225) 266.394 ms 257.638 ms 272.614 ms

  8. #8
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    14,999
    Citação Postado originalmente por inter Ver Post
    não vai até a outra costa.. mas o ping tá bem alto
    Está indo sim. Ou melhor, no caso vindo

  9. #9
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    14,999
    10 159.63.22.102 (159.63.22.102) 261 ms
    global-village-telecom-ltda.xe-1-0-2.ar4.gru1.gblx.net (64.214.145.50) 243 ms
    194.6.125.189.static.impsat.net.br (189.125.6.194) 230 ms

    http://ipstats.globalcrossing.net/cg...lgCall=r2rping

    gru1 - sea1
    round-trip min/avg/max = 220/220/220 ms

    gru1 - lax1
    round-trip min/avg/max = 172/174/176 ms

    sea1 - dal1
    round-trip min/avg/max = 40/42/44 ms

    lax1 - dal1
    round-trip min/avg/max = 36/37/40 ms

    dal1 - gru1
    round-trip min/avg/max = 144/146/148 ms
    Última edição por 5ms; 25-01-2015 às 15:43.

  10. #10
    Web Hosting Master
    Data de Ingresso
    Apr 2012
    Posts
    667
    hoje está ainda pior... packet loss adoidado.

    3 7 ms 9 ms 6 ms gvt-b-se03.cta.gvt.net.br [187.115.211.225]
    4 10 ms 7 ms 11 ms 187.115.223.205.static.host.gvt.net.br [187.115.223.205]
    5 10 ms 10 ms 11 ms gvt-te-0-5-0-7.rc03.cta.gvt.net.br [187.115.218.200]
    6 15 ms 14 ms 15 ms gvt-te-0-6-0-13.rc03.spo.gvt.net.br [179.184.74.137]
    7 13 ms 14 ms 14 ms gvt-te-0-0-0-12.rt01.spo.gvt.net.br [177.99.251.206]
    8 13 ms 12 ms 12 ms xe-3-3-0.ar4.gru1.gblx.net [208.51.41.53]
    9 241 ms 249 ms 240 ms po3-20G.ar3.MIA2.gblx.net [67.17.75.66]
    10 331 ms * * ae5.edge2.miami2.level3.net [4.68.111.121]
    11 329 ms 332 ms * ae-2-70.edge1.LosAngeles6.Level3.net [4.69.144.80]
    12 313 ms 318 ms * ae-2-70.edge1.LosAngeles6.Level3.net [4.69.144.80]
    13 * 322 ms 326 ms te2-5.bbr01.cs01.lax01.networklayer.com [4.26.0.70]
    14 315 ms 324 ms 331 ms ae7.bbr01.cs01.lax01.networklayer.com [173.192.18.166]
    15 343 ms 348 ms 345 ms ae19.bbr01.eq01.dal03.networklayer.com [173.192.18.140]
    16 295 ms 291 ms 295 ms po31.dsr02.dllstx3.networklayer.com [173.192.18.227]
    17 431 ms 425 ms 428 ms po32.dsr02.dllstx2.networklayer.com [70.87.255.70]
    18 350 ms 346 ms 349 ms po2.car01.dllstx2.networklayer.com [70.87.254.78]
    19 426 ms 425 ms 426 ms router1-dal.linode.com [67.18.7.90]

    Disparando 67.18.7.90 com 32 bytes de dados:
    Resposta de 67.18.7.90: bytes=32 tempo=362ms TTL=240
    Esgotado o tempo limite do pedido.
    Resposta de 67.18.7.90: bytes=32 tempo=370ms TTL=240
    Esgotado o tempo limite do pedido.
    Esgotado o tempo limite do pedido.
    Resposta de 67.18.7.90: bytes=32 tempo=369ms TTL=240
    Resposta de 67.18.7.90: bytes=32 tempo=365ms TTL=240
    Resposta de 67.18.7.90: bytes=32 tempo=367ms TTL=240
    Esgotado o tempo limite do pedido.
    Resposta de 67.18.7.90: bytes=32 tempo=337ms TTL=240
    Resposta de 67.18.7.90: bytes=32 tempo=330ms TTL=240
    Resposta de 67.18.7.90: bytes=32 tempo=328ms TTL=240
    Esgotado o tempo limite do pedido.
    Resposta de 67.18.7.90: bytes=32 tempo=336ms TTL=240
    Resposta de 67.18.7.90: bytes=32 tempo=336ms TTL=240
    será que vale a pena manter os nodes em dallas por causa da softlayer?

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
  •