Have burst/nocster stopped using Cogent?

root@server1 [~/public_html]# traceroute www.cogentco.com
traceroute to salt.cogentco.com (66.28.0.10), 30 hops max, 38 byte packets
1 ge-5-0-border.scr1.hostnoc.net (64.191.0.1) 0.432 ms 0.374 ms 0.615 ms
2 12.124.179.5 (12.124.179.5) 8.067 ms 7.858 ms 7.914 ms
3 gbr6-p80.n54ny.ip.att.net (12.123.1.206) 7.864 ms 7.997 ms 8.529 ms
4 tbr2-p012401.n54ny.ip.att.net (12.122.11.29) 8.493 ms 9.000 ms 8.750 ms
5 ggr1-p320.n54ny.ip.att.net (12.122.12.54) 8.044 ms 8.196 ms 8.070 ms
6 att-gw.ny.psi.net (192.205.32.42) 8.301 ms 8.962 ms 8.761 ms
7 p5-0.br01.jfk01.atlas.psi.net (154.54.1.197) 9.291 ms 8.906 ms 8.612 ms
8 p14-0.core01.jfk01.atlas.cogentco.com (154.54.1.21) 37.653 ms 37.524 ms 36.828 ms


traceroute to edgehost.com (66.250.145.194), 30 hops max, 38 byte packets
1 ge-5-0-border.scr1.hostnoc.net (64.191.0.1) 0.451 ms 0.319 ms 0.272 ms
2 12.124.179.5 (12.124.179.5) 7.830 ms 9.300 ms 8.064 ms
3 gbr6-p80.n54ny.ip.att.net (12.123.1.206) 8.443 ms 8.431 ms 7.860 ms
4 gbr3-p90.n54ny.ip.att.net (12.122.5.114) 7.922 ms 7.961 ms 7.891 ms
5 ggr1-p360.n54ny.ip.att.net (12.123.1.121) 7.950 ms 8.058 ms 8.170 ms
6 att-gw.ny.psi.net (192.205.32.42) 27.887 ms 29.215 ms 29.955 ms
7 p5-0.br01.jfk01.atlas.psi.net (154.54.1.197) 29.165 ms 28.637 ms 26.134 ms
8 p14-0.core01.jfk01.atlas.cogentco.com (154.54.1.21) 49.233 ms 45.672 ms 42.264 ms
9 p13-0.core02.jfk02.atlas.cogentco.com (66.28.4.121) 39.369 ms 37.783 ms 37.260 ms
10 p14-0.core02.ord01.atlas.cogentco.com (66.28.4.86) 60.887 ms 62.601 ms 62.110 ms
11 p15-0.core01.ord01.atlas.cogentco.com (66.28.4.61) 61.652 ms 62.164 ms 61.165 ms
12 p5-0.core01.sfo01.atlas.cogentco.com (66.28.4.42) 93.360 ms 93.702 ms 93.145 ms
13 g49.ba01.b003070-2.sfo01.atlas.cogentco.com (66.28.66.138) 93.551 ms 94.057 ms 93.966 ms
14 Atrivo.demarc.cogentco.com (66.250.6.2) 93.831 ms 93.710 ms 94.566 ms
15 66.250.145.194 (66.250.145.194) 91.373 ms 98.596 ms 111.803 ms


Is anybody getting cogent bandwidth in traceroutes to server1.mainarea.com ?

- Matt
9 p4-0.core01.jfk02.atlas.cogentco.com (66.28.4.10) 32.843 ms 33.028 ms 32.981 ms
10 p4-0.core02.dca01.atlas.cogentco.com (66.28.4.81) 38.490 ms 38.448 ms 38.733 ms
11 p15-0.core01.dca01.atlas.cogentco.com (66.28.4.21) 39.202 ms 38.334 ms 39.006 ms
12 salt.cogentco.com (66.28.0.10) 43.131 ms * 42.102 ms

I believe they have cut it back because of all the problems they were having with it.

Andrew

there using sprint now :D

Yep... if you search through some older threads you will see BurstNET comments on why they removed it...

They're currently using Sprint and allowing ATT to be used (from the BurstNET network) for the nocster line until they get another provider... I think they were aiming for Level3

Actually, they're using Sprint, AT&T, and Worldcom. I was getting traces straight through Cogent the other day though to other cogent sites, so they were probably having more problems...