Which company has better quality bandwidth?

They're both great. NAC (great BW - DedicatedNow) vs. Sprint, ATT, and Level3 (all top providers, great BW - Nocster).

be specfic Nocster isn't offering all those providers. While dednow/NAC is offering over 100 diverse providers including AOL Verio, and many others.


Originally posted by dsj
Which company has better quality bandwidth?

Originally posted by jayglate
be specfic Nocster isn't offering all those providers. While dednow/NAC is offering over 100 diverse providers including AOL Verio, and many others.




Nocster does offer all those providers I believe.

Originally posted by jayglate
be specfic Nocster isn't offering all those providers. While dednow/NAC is offering over 100 diverse providers including AOL Verio, and many others.




Shows how much I know. I didn't think there were over 100 different bandwidth providers out there. Hmmm...

http://www.fixedorbit.com/AS/21/AS21788.htm

Their AS has all of them listed, but that doesn't mean they are turned up...

jayglate - stop posting false info about your competitors. Here are traces from my Nocster server:

ATT:
root@server1 [~]# traceroute www.att.net
traceroute: Warning: www.att.net has multiple addresses; using 204.127.135.135
traceroute to www.att.net (204.127.135.135), 30 hops max, 38 byte packets
1 ge-5-0-border.scr1.hostnoc.net (64.191.0.1) 0.971 ms 1.110 ms 0.713 ms
2 12.124.179.5 (12.124.179.5) 7.493 ms 7.683 ms 9.026 ms
3 gbr6-p80.n54ny.ip.att.net (12.123.1.206) 7.291 ms 7.091 ms 7.665 ms


Sprint:

root@server1 [~]# traceroute www.sprint.net
traceroute to www.sprint.net (199.0.233.22), 30 hops max, 38 byte packets
1 ge-5-0-border.scr1.hostnoc.net (64.191.0.1) 0.411 ms 0.331 ms 0.269 ms
2 sl-gw1-pen-11-0.sprintlink.net (144.228.171.177) 17.959 ms 18.378 ms 17.557 ms
3 sl-bb25-pen-5-0.sprintlink.net (144.232.5.5) 31.973 ms 19.683 ms 27.077 ms
4 sl-bb21-pen-8-0.sprintlink.net (144.232.5.237) 22.551 ms 30.131 ms 18.165 ms

Level3:

root@server1 [~]# traceroute www.level3.net
traceroute to www.level3.net (209.245.19.41), 30 hops max, 38 byte packets
1 ge-5-0-border.scr1.hostnoc.net (64.191.0.1) 1.542 ms 0.694 ms 0.775 ms
2 gigabitethernet8-0-104.hsipaccess1.Philadelphia1.Level3.net (64.157.236.1) 9.694 ms 10.000 ms 12.131 ms


Cogent is only used for Cogent to Cogent transfers (hosts that only have Cogent lines), otherwise the other providers are used.

Nocster also has backup providers that can be switched on for Nocster (providers that are offered to BurstNET but not Nocster customers).


For NAC, I guarantee that 90% of NAC traffic goes across seven or so providers, the rest you'll never see. I get Williams going into NAC... yuck. Most of the time, WCG, ATT, Worldcom, and Verio show up. Usually, my pings are better to Nocster than they are to NAC (and I'm in NJ).

NAC's bandwidth (DN uses DCJN NAC bandwidth) is far superior to BurstNet's bandwidth.

Yeah whats up with that, which bandwidth set does DN use? NAC or DJCN? It seems nobody can get it straight, i've never figured it out :eek:, granted im not that concerned so i've never made a concentrated effort :D

It uses DCJN although I also believe its available with NAC for a smaller amount of bandwidth.

You will only get verio or aol if you are on aol or verio, which is the great thing. Your users across 100 or so backbones depending on which one they are connected to will have direct routes to their servers.

Jay,

Please edit your first post in this thread to take out the false info.

- Matt

How is what i said false?
This is a traceroute froma user on the verio network
FROM www.wvi.com TO dedicatednow.com.traceroute to dedicatednow.com (216.118.112.211), 30 hops max, 40 byte packets
1 wvi-gw.wvi.com (204.119.27.254) 1 ms 1 ms 1 ms
2 d1-8-1-5.a01.ptldor01.us.ra.verio.net (206.163.42.213) 24 ms 4 ms 4 ms
3 ge-1-0-0.r02.ptldor01.us.bb.verio.net (129.250.31.222) 4 ms 5 ms 6 ms
4 p4-1-2-0.r00.snjsca04.us.bb.verio.net (129.250.4.31) 30 ms 24 ms 19 ms
5 p16-0-1-0.r20.snjsca04.us.bb.verio.net (129.250.3.86) 23 ms 21 ms 58 ms
6 p16-1-1-2.r20.plalca01.us.bb.verio.net (129.250.2.196) 20 ms 23 ms 20 ms
7 p16-5-0-0.r02.mclnva02.us.bb.verio.net (129.250.2.193) 85 ms 82 ms 81 ms
8 p4-3-0.r00.mclnva02.us.bb.verio.net (129.250.5.249) 94 ms 84 ms 81 ms
9 mae-east-atm.peer.nac.net (198.32.187.103) 83 ms 87 ms 92 ms
10 209.123.11.138 (209.123.11.138) 91 ms 120 ms 98 ms
11 64.21.102.2 (64.21.102.2) 91 ms 91 ms 90 ms
12 fa0-0.core1.pwebtech.com (207.99.8.198) 91 ms 91 ms 92 ms
13 dedicatednow.com (216.118.112.211) 91 ms 91 ms 128 ms


Straight from Verio to us.

Originally posted by mainarea
Jay,

Please edit your first post in this thread to take out the false info.

- Matt

Jay,

I was referring to this piece of info:


be specfic Nocster isn't offering all those providers

I did prove that they do offer all of those providers.

- Matt

There is only one way to solve this dispute.
Look for your selves.

Who ever disegrees with each other go to: http://www.fixedorbit.com/search.htm

In the IP/Domain field enter burst.net, then click on HOSTNOC to see a list of BURSTNET bandwidth providers.

Now, do you same EXCEPT enter nac.net, then click on NET-ACCESS-CORP.

This will solve hopefully ALL disputes. If you still do not beleive the results, contact each NOC/Bandwidth provider and ask for your self.

These are the threads the Mod's close because they get too large ;)

Originally posted by jayglate
How is what i said false?
This is a traceroute froma user on the verio network
FROM www.wvi.com TO dedicatednow.com.traceroute to dedicatednow.com (216.118.112.211), 30 hops max, 40 byte packets
1 wvi-gw.wvi.com (204.119.27.254) 1 ms 1 ms 1 ms
2 d1-8-1-5.a01.ptldor01.us.ra.verio.net (206.163.42.213) 24 ms 4 ms 4 ms
3 ge-1-0-0.r02.ptldor01.us.bb.verio.net (129.250.31.222) 4 ms 5 ms 6 ms
4 p4-1-2-0.r00.snjsca04.us.bb.verio.net (129.250.4.31) 30 ms 24 ms 19 ms
5 p16-0-1-0.r20.snjsca04.us.bb.verio.net (129.250.3.86) 23 ms 21 ms 58 ms
6 p16-1-1-2.r20.plalca01.us.bb.verio.net (129.250.2.196) 20 ms 23 ms 20 ms
7 p16-5-0-0.r02.mclnva02.us.bb.verio.net (129.250.2.193) 85 ms 82 ms 81 ms
8 p4-3-0.r00.mclnva02.us.bb.verio.net (129.250.5.249) 94 ms 84 ms 81 ms
9 mae-east-atm.peer.nac.net (198.32.187.103) 83 ms 87 ms 92 ms
10 209.123.11.138 (209.123.11.138) 91 ms 120 ms 98 ms
11 64.21.102.2 (64.21.102.2) 91 ms 91 ms 90 ms
12 fa0-0.core1.pwebtech.com (207.99.8.198) 91 ms 91 ms 92 ms
13 dedicatednow.com (216.118.112.211) 91 ms 91 ms 128 ms


Straight from Verio to us.




However, this is the route to your webserver which I believe is on NAC proper bandwidth. However, routing to actual DN servers does not go this way I believe depending upon the source. How about posting a traceroute to one of the IP blocks the servers you sell under DN are on.

direct to a dednow ip

FROM www.wvi.com TO 209.123.73.3.traceroute to 209.123.73.3 (209.123.73.3), 30 hops max, 40 byte packets
1 wvi-gw.wvi.com (204.119.27.254) 1 ms 1 ms 1 ms
2 d1-8-1-5.a01.ptldor01.us.ra.verio.net (206.163.42.213) 12 ms 11 ms 4 ms
3 ge-1-0-0.r02.ptldor01.us.bb.verio.net (129.250.31.222) 7 ms 4 ms 4 ms
4 p4-1-2-0.r00.snjsca04.us.bb.verio.net (129.250.4.31) 19 ms 25 ms 19 ms
5 p16-0-1-0.r20.snjsca04.us.bb.verio.net (129.250.3.86) 34 ms 20 ms 20 ms
6 p16-1-1-2.r20.plalca01.us.bb.verio.net (129.250.2.196) 21 ms 32 ms 23 ms
7 p16-5-0-0.r02.mclnva02.us.bb.verio.net (129.250.2.193) 88 ms 81 ms 86 ms
8 p4-3-0.r00.mclnva02.us.bb.verio.net (129.250.5.249) 105 ms 81 ms 81 ms
9 mae-east-atm.peer.nac.net (198.32.187.103) 86 ms 83 ms 83 ms
10 209.123.11.138 (209.123.11.138) 91 ms 99 ms 93 ms
11 64.21.102.2 (64.21.102.2) 101 ms 109 ms 98 ms
12 209.123.73.3 (209.123.73.3) 92 ms 101 ms 106 ms

But we both know that dedicated now servers are 66.246.xxx.xxx

Atleast my 3 are. I guess I am not getting what I paid for. Can you put my 3 servers on that same network?

FROM www.wvi.com TO 66.246.50.35.traceroute to 66.246.50.35 (66.246.50.35), 30 hops max, 40 byte packets
1 wvi-gw.wvi.com (204.119.27.254) 1 ms 1 ms 1 ms
2 d1-8-1-5.a01.ptldor01.us.ra.verio.net (206.163.42.213) 131 ms 12 ms 208 ms
3 ge-1-0-0.r02.ptldor01.us.bb.verio.net (129.250.31.222) 6 ms 5 ms 4 ms
4 p4-1-2-0.r00.snjsca04.us.bb.verio.net (129.250.4.31) 19 ms 19 ms 32 ms
5 p16-0-1-0.r20.snjsca04.us.bb.verio.net (129.250.3.86) 39 ms 22 ms 19 ms
6 p16-1-1-2.r20.plalca01.us.bb.verio.net (129.250.2.196) 20 ms 20 ms 31 ms
7 p16-5-0-0.r02.mclnva02.us.bb.verio.net (129.250.2.193) 81 ms 98 ms 86 ms
8 p4-3-0.r00.mclnva02.us.bb.verio.net (129.250.5.249) 81 ms 100 ms 81 ms
9 mae-east-atm.peer.nac.net (198.32.187.103) 91 ms 94 ms 88 ms
10 209.123.11.138 (209.123.11.138) 111 ms 91 ms 96 ms
11 64.21.102.2 (64.21.102.2) 109 ms 102 ms 90 ms
12 66.246.50.35 (66.246.50.35) 91 ms 96 ms 98 ms

Here is an especially nasty traceroute from colorado to a server at DN

| 1 | | 216.229.47.197 | dhcp.cos.pcisys.net | ?Colorado Springs CO 80915 | | 18 | x | Precision Communications, Inc. PCISYS-NET |
| 2 | | 216.229.32.161 | cartman-S3-0.pcisys.net | ?Colorado Springs CO 80915 | | 19 | x | Precision Communications, Inc. PCISYS-NET |
| 3 | | 216.52.42.13 | border10.s6-4.pcisys-1.den.pnap.net | - | | 20 | x | Internap Network Services PNAP-8-98 |
| 4 | | 216.52.40.1 | core1.ge0-0-bbnet1.den.pnap.net | - | | 21 | x | InterNAP Network Services, PNAP-DEN PNAP-DEN-INAP-BB-1 |
| 5 | | 160.81.54.45 | sl-gw14-che-0-1.sprintlink.net | Cheyenne, WY, USA | * | 22 | x | Sprint SPRN-BLKI |
| 6 | | 144.232.15.181 | sl-bb21-che-9-0.sprintlink.net | Cheyenne, WY, USA | * | 23 | x | Sprint SPRINT-INNET9 |
| 7 | | 144.232.18.6 | sl-bb21-chi-11-2.sprintlink.net | Chicago, IL, USA | +01:00 | 40 | x | Sprint SPRINT-INNET9 |
| 8 | | 144.232.8.54 | sl-bb21-fw-10-0.sprintlink.net | Fort Worth, TX, USA | | 61 | x | Sprint SPRINT-INNET9 |
| 9 | | 144.232.11.130 | sl-gw20-fw-9-0.sprintlink.net | Fort Worth, TX, USA | | 59 | x | Sprint SPRINT-INNET9 |
| 10 | 10 | 144.232.194.50 | sl-williamscom-11-0.sprintlink.net | - | | 122 | -x- | Sprint SPRINT-INNET9 |
| 11 | 10 | 64.200.240.25 | chcgil1wcx2-oc48.wcg.net | Chicago, IL, USA | +01:00 | 165 | -x | Williams Communication IP Services WLCO-CROSSINTERN-30-2 |
| 12 | | 64.200.103.78 | chcgil1wcx3-oc48.wcg.net | Chicago, IL, USA | +01:00 | 144 | x-- | Williams Communication IP Services WLCO-CHCGIL1INTERN-30 |
| 13 | | 64.200.240.38 | nycmny2wcx3-oc48.wcg.net | - | | 230 | ---x--- | Williams Communication IP Services WLCO-CROSSINTERN-30-2 |
| 14 | | 64.200.87.110 | nycmnyhlce1-oc48.wcg.net | - | | 156 | -x | Williams Communication IP Services WLCO-NYCMNY2INTERN-30 |
| 15 | 10 | 64.200.86.150 | nycmny2lce1-netaccess-atm.wcg.net | - | | 141 | x- | Williams Communication IP Services WLCO-NYCMNY2INTERN-30 |
| 16 | | 64.21.102.13 | 0094.ge-3-0-0.gbr2.nyc.nac.net | New York, NY, USA | +02:00 | 166 | -x- | Net Access Corporation NAC-NETBLK03 |
| 17 | 20 | 209.123.11.10 | 1194.at-0-0-0.gbr1.oct.nac.net | - | | 174 | x- | Net Access Corporation NAC-NETBLK02 |
| 18 | 20 | 64.21.102.2 | 0095.gi-1-1.msfc1.oct.nac.net | - | | 181 | x- | Net Access Corporation NAC-NETBLK03 |

6 p16-1-1-2.r20.plalca01.us.bb.verio.net (129.250.2.196) 20 ms 20 ms 31 ms
7 p16-5-0-0.r02.mclnva02.us.bb.verio.net (129.250.2.193) 81 ms 98 ms 86 ms
8 p4-3-0.r00.mclnva02.us.bb.verio.net (129.250.5.249) 81 ms 100 ms 81 ms
9 mae-east-atm.peer.nac.net (198.32.187.103) 91 ms 94 ms 88 ms
10 209.123.11.138 (209.123.11.138) 111 ms 91 ms 96 ms
11 64.21.102.2 (64.21.102.2) 109 ms 102 ms 90 ms
12 66.246.50.35 (66.246.50.35) 91 ms 96 ms 98 ms

That's peering at an exchange, right?
Should it count?

Having posted all of this information, I will now venture an opinion.

I do believe that Burst has better bandwidth. In that I mean they provide access to 3 very good providers, sprint, att and level3.

It does not appear, and I was told by someone at DN, that DN does not provide access to a few of NAC's tier one providers.

HOWEVER, I have found DN's network to be more stable, have better resiliency and is run more professionally. I also believe DN's data center to be more stable.

All that said, I am continuing to place business with DN. I wanted to make it clear with the information above that DN has some challenges when it comes to the manner that NAC advertises some of their networks, specifically with the use of Williams. I would also like to see DN improve support response times.

Nocster provides all 3 of those (ATT, Sprint, Level3) you can go to tracert.com (I think), traceroute from random locations in the world and you'll see them all.

From Internap (OnNet with nine providers, so good place to traceroute :)).


traceroute to 66.246.50.35 (66.246.50.35), 30 hops max, 38 byte packets
3 core4.ge0-0-0-bbnet1.bsn.pnap.net (63.251.128.6) 0.482 ms 0.402 ms 0.373 ms
4 bos-edge-02.inet.qwest.net (63.145.1.93) 0.721 ms 1.075 ms 0.821 ms
5 bos-core-02.inet.qwest.net (205.171.28.29) 0.687 ms 0.618 ms 0.813 ms
6 jfk-core-01.inet.qwest.net (205.171.8.19) 6.336 ms 5.906 ms 6.001 ms
7 jfk-core-03.inet.qwest.net (205.171.230.6) 6.022 ms 6.059 ms 6.314 ms
8 jfk-brdr-02.inet.qwest.net (205.171.230.25) 5.983 ms 5.953 ms 6.019 ms
9 qwest-gw.n54ny.ip.att.net (192.205.32.169) 6.499 ms 6.200 ms 6.912 ms
10 tbr1-p014001.n54ny.ip.att.net (12.123.3.1) 6.709 ms 8.765 ms 7.321 ms
11 gar1-p3100.nwrnj.ip.att.net (12.123.214.181) 6.611 ms 6.599 ms 6.596 ms
12 12.119.140.30 (12.119.140.30) 239.632 ms 222.599 ms 208.511 ms
13 1189.at-0-1-0.gbr1.oct.nac.net (209.123.11.69) 206.253 ms 231.526 ms 259.312 ms
14 0095.gi-1-1.msfc1.oct.nac.net (64.21.102.2) 251.676 ms 230.548 ms 221.784 ms
15 66.246.50.35 (66.246.50.35) 208.117 ms 208.141 ms 201.746 ms


It went through ATT, which is not bad, although it would be better if it stays on ATT instead of jumping over to qwest. But what's going on on hop 12 there?

Traceroute to nocster.com


traceroute to nocster.com (66.96.192.220), 30 hops max, 38 byte packets
3 core3.ge1-0-0-bbnet2.bsn.pnap.net (63.251.128.67) 0.450 ms 0.354 ms 0.364 ms
4 12.125.40.117 (12.125.40.117) 1.129 ms 1.358 ms 1.124 ms
5 gbr2-p52.cb1ma.ip.att.net (12.123.40.94) 1.816 ms 1.240 ms 2.105 ms
6 tbr1-p013701.cb1ma.ip.att.net (12.122.11.197) 2.869 ms 1.776 ms 2.526 ms
7 tbr2-p013701.n54ny.ip.att.net (12.122.10.22) 6.875 ms 6.938 ms 7.855 ms
8 gbr5-p40.n54ny.ip.att.net (12.122.11.26) 6.782 ms 7.334 ms 6.658 ms
9 gar2-p360.n54ny.ip.att.net (12.123.1.201) 6.877 ms 6.649 ms 6.644 ms
10 12.124.179.6 (12.124.179.6) 20.461 ms 20.075 ms 20.901 ms
11 66.96.192.220 (66.96.192.220) 21.268 ms 21.158 ms 20.187 ms


Shorter since it goes directly from ATT at Internap to ATT at Nocster.

BTW, feel free to use our traceroute utility (http://www.fluidhosting.com/traceroute.php) from our server.