Banda Ancha EU

Comunidad de usuarios
de fibra, móvil y ADSL

hosting en interdominios
41 lecturas y 3 respuestas
  • Cerrado

    [Editado 29/12/06 14:59]

    ¿Qué mierdas de trazas son estas, que no hay quien vea nada?

    Traza a la dirección www.youtube.com [208.65.153.241]
    sobre un máximo de 30 saltos:

    1 * * * Tiempo de espera agotado para esta solicitud.
    2 44 ms 44 ms 42 ms 172.18.0.30
    3 53 ms 44 ms 43 ms 172.18.0.30
    4 234 ms 208 ms 239 ms 84.76.4.152
    5 43 ms 42 ms 42 ms 217.6.24.105
    6 77 ms 78 ms 77 ms f-ea1.F.DE.net.DTAG.DE [62.154.17.182]
    7 86 ms 88 ms 92 ms p2-0.core01.fra01.atlas.cogentco.com [212.20.159.38]
    8 93 ms 87 ms 87 ms g1-1.core01.fra03.atlas.cogentco.com [130.117.0.29]
    9 258 ms 259 ms 255 ms p15-0.core01.par02.atlas.cogentco.com [130.117.0.18]
    10 258 ms 272 ms 247 ms p12-0.core01.par01.atlas.cogentco.com [130.117.0.117]
    11 248 ms 254 ms 258 ms p14-0.core02.dca01.atlas.cogentco.com [66.28.4.206]
    12 258 ms 258 ms 251 ms t4-3.mpd01.dca01.atlas.cogentco.com [154.54.5.57]
    13 256 ms * 314 ms v3491.mpd01.dca02.atlas.cogentco.com [154.54.2.182]
    14 258 ms 259 ms 258 ms v3494.mpd01.iad01.atlas.cogentco.com [154.54.5.42]
    15 258 ms 258 ms 242 ms youtube.demarc.cogentco.com [38.112.2.142]
    16 267 ms 250 ms 252 ms 10.254.254.226
    17 347 ms 270 ms 240 ms 64.15.116.5
    18 * * * Tiempo de espera agotado para esta solicitud.
    19 * * * Tiempo de espera agotado para esta solicitud.
    20 225 ms 226 ms 226 ms www.youtube.com [208.65.153.241]

    Y esta ya es patética del todo:

    Traza a la dirección conceptart.org [38.100.84.112]
    sobre un máximo de 30 saltos:

    1 * * * Tiempo de espera agotado para esta solicitud.
    2 46 ms 43 ms 43 ms 172.18.0.49
    3 43 ms 43 ms 44 ms 172.18.0.49
    4 42 ms 56 ms 42 ms 84.76.4.156
    5 43 ms 43 ms 43 ms 217.6.48.89
    6 78 ms 77 ms 78 ms f-ea1.F.DE.net.DTAG.DE [62.154.17.182]
    7 141 ms 145 ms 146 ms p2-0.core01.fra01.atlas.cogentco.com [212.20.159.38]
    8 150 ms 147 ms 148 ms g1-1.core01.fra03.atlas.cogentco.com [130.117.0.29]
    9 256 ms 262 ms 262 ms p3-0.core01.ams03.atlas.cogentco.com [130.117.0.145]
    10 262 ms 261 ms 252 ms p1-0.core01.lon01.atlas.cogentco.com [130.117.1.225]
    11 260 ms 250 ms 253 ms p3-0.core02.jfk02.atlas.cogentco.com [66.28.4.189]
    12 252 ms 262 ms 263 ms p15-0.core01.jfk02.atlas.cogentco.com [66.28.4.13]
    13 261 ms 262 ms 257 ms p4-0.core02.dca01.atlas.cogentco.com [66.28.4.81]
    14 266 ms 261 ms 273 ms p14-0.core01.atl01.atlas.cogentco.com [66.28.4.161]
    15 1079 ms 1049 ms 1016 ms p10-0.core01.iah01.atlas.cogentco.com [154.54.5.89]
    16 1081 ms 1074 ms 1051 ms g0-1.na01.b002576-1.iah01.atlas.cogentco.com [38.20.34.54]
    17 900 ms 932 ms 992 ms zogmo.demarc.cogentco.com [38.99.213.114]
    18 1086 ms 1085 ms 1142 ms server3.greyskymedia.com [38.100.84.112]

    ¿Os pasa lo mismo?

    Este tema es antiguo y puede contener información obsoleta. Abre un nuevo tema para publicar tu mensaje.
    1
    • Cerrado

      Con telefonica: Tracing route to www.youtube.com…

      Con telefonica:

      Tracing route to www.youtube.com [208.65.153.251]
      over a maximum of 30 hops:

      1 1 ms 1 ms 1 ms 192.168.1.1
      2 44 ms 43 ms 43 ms 192.168.153.1
      3 44 ms 44 ms 43 ms 98.Red-81-46-65.staticIP.rima-tde.net [81.46.65.
      98]
      4 * * 53 ms 137.Red-80-58-75.staticIP.rima-tde.net [80.58.75
      .137]
      5 53 ms 53 ms * So7-0-0-0-grtmadde2.red.telefonica.wholesale.net
      [84.16.8.113]
      6 82 ms 75 ms 76 ms So1-2-0-0-grtparix3.red.telefonica-wholesale.net
      [213.140.43.186]
      7 123 ms 122 ms 121 ms p10-0.core02.par02.atlas.cogentco.com [130.117.1
      .25]
      8 127 ms 126 ms 125 ms p12-0.core01.par01.atlas.cogentco.com [130.117.0
      .117]
      9 202 ms 201 ms 200 ms p14-0.core02.dca01.atlas.cogentco.com [66.28.4.2
      06]
      10 203 ms 203 ms 204 ms t4-3.mpd01.dca01.atlas.cogentco.com [154.54.5.57
      ]
      11 206 ms 205 ms 204 ms v3491.mpd01.dca02.atlas.cogentco.com [66.28.4.86
      ]
      12 * 202 ms * v3496.mpd01.iad01.atlas.cogentco.com [154.54.5.4
      6]
      13 265 ms 334 ms 402 ms 38.101.184.202
      14 * * * Request timed out.
      15 248 ms 248 ms 248 ms 64.15.116.9
      16 * * * Request timed out.
      17 * * * Request timed out.
      18 288 ms 284 ms 287 ms 208.65.153.251

      Trace complete.

    • Cerrado

      There was a funny conspiracy theory spun on the NANOG mailing…

      There was a funny conspiracy theory spun on the NANOG mailing list about this issue. The general theory put forth was that the entire story is about Deutsche Telecom (DTAG, AS3320). Unlikely, you say? This is the very nature (and appeal) of conspiracy theories. The story goes something like this: Cogent traffic to DTAG is congested. DTAG refuses to upgrade the peering because they think it hurts Cogent more than it hurts them. DTAG buys from Sprint and Cogent knows this. Cogent gets paid peering from Sprint so that they can force DTAG traffic down that link and make DTAG pay for it. It's a nice theory but it's not realistic.

      While it is true that DTAG buys from Sprint, it is not true that a network of Cogent's size would make a paid peering decision purely on the basis of one congested peering. Moreover, the rumors are flying fast and furious that lots of DTAG peering is congested right now, not just to Cogent. I have no personal knowledge about whether that's true, but it's becoming a persistent story. Although I don't doubt for a second that many European networks would like to reduce the quality of their peering with Cogent out of anger over the way Cogent has dropped prices in the European market, there's no evidence that DTAG's peering congestion with Cogent (if it exists at all) is caused by that anger. And there's even less evidence that a network like Cogent would pay Sprint for peering just to spite DTAG. It is a fun theory, though.

      ======================================

      Wolfen - 12/12/2006 11:51 AM

      This is for people in germany, which are customers of Deutsche Telekom AG - i have got a answer from Cogent Support Desk:

      Dear *********,

      The problem is not due to our network. There is currently a congestion on the peering conections between Cogent and Deutsche Telecom during peak hours. Cogent has approached DTAG to increase the current peeing capacity and for the time being, DTAG has declined to do so. As you are a DTAG customer we advise you to report this problem to your provider since they are the ones blocking the peering capacity increase.

      best regards

      NOC Cogent

      :-( :-( :-( :-( :-(

      • Cerrado

        esto ya lo postee yo hace tiempo que todo de yacom va por…

        esto ya lo postee yo hace tiempo que todo de yacom va por alemania en dtag y esta saturado, no las centralitas de aqui ni la red albura, por eso va tan lento yacom.