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

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

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

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.