Results 1 to 27 of 27
  1. #1

    Chicago Colo for Game Server

    I'm looking for a Colo provider for a 2u server in the Chicago area. I'll be running a game server that will host at least two 24 player servers, so I'm thinking I need a 10Mb unmetered connection.

    Ideally, I'd like to get it at $100/mo, but I understand that may be unlikely.

    Recommendations?

  2. #2
    Join Date
    Jan 2003
    Location
    Chicago, IL
    Posts
    6,889
    2u + 10 Mbit/sec for $100 isn't going to happen anywhere, for the most part. My hint to you, find out exactly how much bandwidth you'll need and go from there. If you'll only use 4 Mbit/sec on 95th percentile there is no reason to pay for 10 Mbit/sec.
    Karl Zimmerman - Steadfast: Managed Dedicated Servers and Premium Colocation
    karl @ steadfast.net - Sales/Support: 312-602-2689
    Cloud Hosting, Managed Dedicated Servers, Chicago Colocation, and New Jersey Colocation
    Now Open in New Jersey! - Contact us for New Jersey colocation or dedicated servers

  3. #3
    Right, I figured as such, but I always try to "shoot high"

    Well, perhaps you might be able to provide assistance with the bandwidth numbers since I'm aware that Steadfast also provides Colo services and numerous game servers are hosted there.

    Right now, we're running 24-man TF2 and COD4 servers but due to some issues with our current provider, I can't just pull network data from our own. All the information I've seen online about calculating bandwidth based off rates looks like a 24 person server running at a 25000 rate would need a 5Mb connection. I used that to come up with the 10Mb connection.

    Is that incorrect based on your experience?

    Also, is it usually pretty easy to up your connection if you determine that the current contracted speed is too slow?

  4. #4
    Join Date
    Jan 2003
    Location
    Chicago, IL
    Posts
    6,889
    I do not know precisely what our customers run on their servers, so I couldn't really say. I did find this though: http://www.infinityward.com/communit....html#msg48445 It seems to indicate 1 Mbit/sec is enough for a 24 player COD4 server. Also, if they are private servers they likely won't be full 24/7, etc. either.
    Karl Zimmerman - Steadfast: Managed Dedicated Servers and Premium Colocation
    karl @ steadfast.net - Sales/Support: 312-602-2689
    Cloud Hosting, Managed Dedicated Servers, Chicago Colocation, and New Jersey Colocation
    Now Open in New Jersey! - Contact us for New Jersey colocation or dedicated servers

  5. #5
    So, what does Steadfast offer for 2u at 2-5Mbps?

  6. #6
    Join Date
    Oct 2001
    Location
    Miami,FL
    Posts
    612
    Contact globalcon.net they do pure internap in chicago. It's excellent quality for gaming.
    Joman Sierra
    http://www.dominet.net

  7. #7
    Join Date
    Mar 2003
    Location
    Chicago
    Posts
    285
    FDC Server offers 2u with 5mbit unmetered on a shared link for $119. Some people seem to really dig them. I personally have not used them.

    Most places you are looking at least $150 a month for 2u and 2mbit/s.
    Last edited by CArmstrong; 01-24-2008 at 12:43 AM. Reason: Fixed typo

  8. #8
    Join Date
    Mar 2003
    Location
    Chicago
    Posts
    285
    Steadfast seems to have a deal for 1u + 10mbit/s for $199. So probably $225 or $250 for a 2u and 10mbit/s on their standard network.
    Last edited by CArmstrong; 01-24-2008 at 12:44 AM.

  9. #9
    Join Date
    Jun 2003
    Location
    Israel
    Posts
    376
    There is an offer on the colo section from FDC. They seem to be offering pure internap which should result in better perfomance.. good for your gaming.
    You should check out that subforum, many other interesting offers.

  10. #10
    Join Date
    Apr 2006
    Location
    Phoenix
    Posts
    808
    Karl is not able to link to his own prices even though their was a direct question so here is the link:
    http://steadfast.net/services/colocation.php
    Jordan Jacobs | VP, Products|SingleHop| JJ @SingleHop.com
    Managed Dedicated Servers | Bare-Metal Servers | Cloud Services

  11. #11
    Join Date
    Oct 2004
    Posts
    391
    You can also check with ServerCentral, FastServers, SingleHop in addition to the ones listed.

  12. #12
    Join Date
    Jan 2003
    Location
    Chicago, IL
    Posts
    6,889
    Quote Originally Posted by Noam View Post
    There is an offer on the colo section from FDC. They seem to be offering pure internap which should result in better perfomance.. good for your gaming.
    Better performance than?
    Karl Zimmerman - Steadfast: Managed Dedicated Servers and Premium Colocation
    karl @ steadfast.net - Sales/Support: 312-602-2689
    Cloud Hosting, Managed Dedicated Servers, Chicago Colocation, and New Jersey Colocation
    Now Open in New Jersey! - Contact us for New Jersey colocation or dedicated servers

  13. #13
    Join Date
    Mar 2002
    Location
    Philadelphia, PA
    Posts
    2,508
    For gaming in Chicago go with Steadfast... They have great routing and gamerail support to boot.
    Linux junkie | steward.io

  14. #14
    Join Date
    Jun 2003
    Location
    Israel
    Posts
    376

    Quote Originally Posted by KarlZimmer View Post
    Better performance than?
    Internap can spin their own product, they don't need me to do it for them.

    If you are wondering if I meant compared to your service, I don't have a direct experience with Steadfast's bandwidth so I cannot compare.
    However, I will open the door so the mods don't get angry,


    Karl, as president of Steadfast/NoZone, does the NoZone Performance network give better gaming related performance (low latency, low jitter) compared to the local Chicago-based pnap of Internap to the eyeball networks in the Chicago/east-coast area?

    A simple yes is enough for me, but potential customers can be impressed with traceroute comparison or whatever you see fit.

  15. #15
    Join Date
    Mar 2002
    Location
    Philadelphia, PA
    Posts
    2,508
    Quote Originally Posted by Noam View Post
    A simple yes is enough for me, but potential customers can be impressed with traceroute comparison or whatever you see fit.
    I'm obviously not Karl But I can say that in most cases Steadfast out performs Internap in Chicago on a ton of routes. To me Level3 & Savvis properly routed is an incredible combination, throw in the additional providers Steadfast has and you have yourself a heck of a network.

    If you do some research you will see quite a few large scale providers are moving away from Internap, due to poor routing and Internap unwilling to make adjustments. One company that comes to mind is Hi-Def (HD-Gaming.com) recently moved most of their stuff off Internap.
    Linux junkie | steward.io

  16. #16
    Join Date
    Jan 2003
    Location
    Chicago, IL
    Posts
    6,889
    Well, Comcast, AT&T/SBC, and RCN make up almost the entire make-up of the eyeball networks in Chicago, so here are some traces. I used an InterNAP IP at FDC.

    From AT&T/SBC

    InterNAP:
    1 2 ms 1 ms 1 ms 10.0.0.1
    2 1 ms 1 ms 1 ms 192.168.0.1
    3 7 ms 7 ms 7 ms adsl-75-33-239-254.dsl.chcgil.sbcglobal.net [75.33.239.254]
    4 7 ms 7 ms 7 ms dist1-vlan52.chcgil.sbcglobal.net [99.164.168.129]
    5 6 ms 7 ms 8 ms bb1-g6-0.chcgil.ameritech.net [151.164.190.120]
    6 25 ms 26 ms 26 ms ex1-p5-0.eqabva.sbcglobal.net [151.164.191.134]
    7 25 ms 26 ms 27 ms asn4766-koreantelecom.eqlaca.sbcglobal.net [151.164.250.206]
    8 24 ms 25 ms 25 ms ae-2.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.86]
    9 32 ms 31 ms 31 ms as-0.r21.nycmny01.us.bb.gin.ntt.net [129.250.2.8]
    10 56 ms 57 ms 56 ms p64-2-0-0.r20.chcgil09.us.bb.gin.ntt.net [129.250.5.4]
    11 61 ms 254 ms 284 ms xe-3-1.r01.chcgil09.us.bb.gin.ntt.net [129.250.3.206]
    12 32 ms 33 ms 32 ms xe-3-3.r01.chcgil09.us.ce.gin.ntt.net [129.250.208.6]
    13 32 ms 43 ms 33 ms border5.pc2-bbnet2.chg.pnap.net [64.94.32.74]
    14 33 ms 32 ms 34 ms 66.90.127.205 [66.90.127.205]
    15 33 ms 33 ms 32 ms 66.90.127.138 [66.90.127.138]
    16 32 ms 36 ms 33 ms . [74.63.66.114]

    Steadfast:
    1 1 ms 1 ms 1 ms 10.0.0.1
    2 1 ms 1 ms 1 ms 192.168.0.1
    3 7 ms 7 ms 7 ms adsl-75-33-239-254.dsl.chcgil.sbcglobal.net [75.33.239.254]
    4 7 ms 8 ms 7 ms dist2-vlan52.chcgil.sbcglobal.net [99.164.168.130]
    5 22 ms 7 ms 7 ms bb2-g3-0.chcgil.ameritech.net [151.164.190.122]
    6 7 ms 7 ms 7 ms 151.164.95.164
    7 7 ms 7 ms 7 ms xe-2-3.bbr01.ord01.us.xeex.net [206.223.119.87]
    8 9 ms 8 ms 8 ms unknown.ord01.us.xeex.net [69.26.182.250]
    9 8 ms 7 ms 7 ms 17.208-100-32.static.steadfast.net [208.100.32.17]
    10 7 ms 8 ms 7 ms resolver1.steadfast.net [216.86.146.8]

    From Comcast

    InterNAP
    traceroute 74.63.66.114
    traceroute to 74.63.66.114 (74.63.66.114), 64 hops max, 40 byte packets
    1 10.0.0.1 (10.0.0.1) 2.675 ms 2.068 ms 2.052 ms
    2 * * *
    3 * * ge-7-19-ur01.area4.il.chicago.comcast.net (68.86.114.77) 56.292 ms
    4 68.86.90.182 (68.86.90.182) 68.778 ms * 14.106 ms
    5 COMCAST-IP.edge1.Chicago2.Level3.net (4.71.248.18) 10.559 ms 15.481 ms *
    6 xe-10-1-0.edge1.Chicago2.Level3.net (4.71.248.17) 10.573 ms 9.898 ms 10.120 ms
    7 ge-9-1.ipcolo1.Chicago1.Level3.net (4.68.101.74) 13.349 ms 11.365 ms ge-7-1.ipcolo1.Chicago1.Level3.net (4.68.101.106) 13.520 ms
    8 unknown.Level3.net (209.247.34.166) 11.739 ms 14.706 ms 12.190 ms
    9 border5.pc2-bbnet2.chg.pnap.net (64.94.32.74) 15.770 ms 18.279 ms 12.986 ms
    10 66.90.127.205 (66.90.127.205) 35.072 ms 32.761 ms 33.015 ms
    11 66.90.127.138 (66.90.127.138) 34.207 ms 32.548 ms 42.475 ms

    Steadfast:

    traceroute 216.86.146.8
    traceroute to 216.86.146.8 (216.86.146.8), 64 hops max, 40 byte packets
    1 10.0.0.1 (10.0.0.1) 2.694 ms 2.696 ms 2.023 ms
    2 * * *
    3 ge-7-19-ur01.area4.il.chicago.comcast.net (68.86.114.77) 12.545 ms 12.284 ms 9.017 ms
    4 68.86.90.178 (68.86.90.178) 13.028 ms * 10.079 ms
    5 COMCAST-IP.edge1.Chicago2.Level3.net (4.71.248.22) 16.083 ms 13.591 ms 14.013 ms
    6 xe-9-3-0.edge1.Chicago2.Level3.net (4.71.248.21) 54.549 ms 12.613 ms 10.836 ms
    7 ae-24-56.car4.Chicago1.Level3.net (4.68.101.168) 15.068 ms ae-24-54.car4.Chicago1.Level3.net (4.68.101.104) 11.704 ms ae-14-55.car4.Chicago1.Level3.net (4.68.101.136) 11.876 ms
    8 WBS-CONNECT.car4.Chicago1.Level3.net (4.79.208.154) 11.568 ms 11.806 ms 12.623 ms
    9 61.216-86-149.static.steadfast.net (216.86.149.61) 12.138 ms 12.966 ms 14.275 ms
    10 resolver1.steadfast.net (216.86.146.8) 14.370 ms 12.228 ms 15.906 ms

    From RCN

    InterNAP:
    Tracing route to . [74.63.66.114]
    over a maximum of 30 hops:

    1 8 ms 32 ms 10 ms 172.30.96.1
    2 21 ms 9 ms 10 ms mart-h1.chi-mart.il.cable.rcn.net [207.229.191.130]
    3 8 ms 19 ms 23 ms ge1-0-2.core2.chsl.il.rcn.net [207.172.19.61]
    4 11 ms 22 ms 34 ms ge5-0.border1.eqnx.il.rcn.net [207.172.19.15]
    5 11 ms 7 ms 8 ms xe-0.equinix.chcgil09.us.bb.gin.ntt.net [206.223.119.12]
    6 11 ms 16 ms 10 ms xe-3-1.r01.chcgil09.us.bb.gin.ntt.net [129.250.3.206]
    7 23 ms 38 ms 37 ms xe-3-3.r01.chcgil09.us.ce.gin.ntt.net [129.250.208.6]
    8 10 ms 14 ms 8 ms border5.pc2-bbnet2.chg.pnap.net [64.94.32.74]
    9 10 ms 32 ms 10 ms 66.90.127.205 [66.90.127.205]
    10 11 ms 14 ms 12 ms 66.90.127.138 [66.90.127.138]
    11 9 ms 23 ms 15 ms . [74.63.66.114]

    Steadfast:
    Tracing route to resolver1.steadfast.net [216.86.146.8]
    over a maximum of 30 hops:

    1 11 ms 23 ms 33 ms 172.30.96.1
    2 22 ms 13 ms 9 ms mart-h1.chi-mart.il.cable.rcn.net [207.229.191.130]
    3 15 ms 13 ms 9 ms ge0-0-2.core2.chsl.il.rcn.net [207.172.19.43]
    4 22 ms 16 ms 9 ms ge5-0.border1.eqnx.il.rcn.net [207.172.19.15]
    5 12 ms 9 ms 28 ms xe-2-3.bbr01.ord01.us.xeex.net [206.223.119.87]
    6 9 ms 12 ms 12 ms unknown.ord01.us.xeex.net [69.26.182.250]
    7 11 ms 39 ms 7 ms 17.208-100-32.static.steadfast.net [208.100.32.17]
    8 14 ms 9 ms 11 ms resolver1.steadfast.net [216.86.146.8]

    I believe that indicates that yes, we are better.

    Note: I did not pick and choose results, etc. I had friends in the area on each of those ISPs send me their traceroute results.
    Karl Zimmerman - Steadfast: Managed Dedicated Servers and Premium Colocation
    karl @ steadfast.net - Sales/Support: 312-602-2689
    Cloud Hosting, Managed Dedicated Servers, Chicago Colocation, and New Jersey Colocation
    Now Open in New Jersey! - Contact us for New Jersey colocation or dedicated servers

  17. #17
    Join Date
    Nov 2002
    Location
    Chicago IL
    Posts
    885
    Quote Originally Posted by KarlZimmer View Post
    Well, Comcast, AT&T/SBC, and RCN make up almost the entire make-up of the eyeball networks in Chicago, so here are some traces. I used an InterNAP IP at FDC.

    From AT&T/SBC

    InterNAP:
    1 2 ms 1 ms 1 ms 10.0.0.1
    2 1 ms 1 ms 1 ms 192.168.0.1
    3 7 ms 7 ms 7 ms adsl-75-33-239-254.dsl.chcgil.sbcglobal.net [75.33.239.254]
    4 7 ms 7 ms 7 ms dist1-vlan52.chcgil.sbcglobal.net [99.164.168.129]
    5 6 ms 7 ms 8 ms bb1-g6-0.chcgil.ameritech.net [151.164.190.120]
    6 25 ms 26 ms 26 ms ex1-p5-0.eqabva.sbcglobal.net [151.164.191.134]
    7 25 ms 26 ms 27 ms asn4766-koreantelecom.eqlaca.sbcglobal.net [151.164.250.206]
    8 24 ms 25 ms 25 ms ae-2.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.86]
    9 32 ms 31 ms 31 ms as-0.r21.nycmny01.us.bb.gin.ntt.net [129.250.2.8]
    10 56 ms 57 ms 56 ms p64-2-0-0.r20.chcgil09.us.bb.gin.ntt.net [129.250.5.4]
    11 61 ms 254 ms 284 ms xe-3-1.r01.chcgil09.us.bb.gin.ntt.net [129.250.3.206]
    12 32 ms 33 ms 32 ms xe-3-3.r01.chcgil09.us.ce.gin.ntt.net [129.250.208.6]
    13 32 ms 43 ms 33 ms border5.pc2-bbnet2.chg.pnap.net [64.94.32.74]
    14 33 ms 32 ms 34 ms 66.90.127.205 [66.90.127.205]
    15 33 ms 33 ms 32 ms 66.90.127.138 [66.90.127.138]
    16 32 ms 36 ms 33 ms . [74.63.66.114]

    Steadfast:
    1 1 ms 1 ms 1 ms 10.0.0.1
    2 1 ms 1 ms 1 ms 192.168.0.1
    3 7 ms 7 ms 7 ms adsl-75-33-239-254.dsl.chcgil.sbcglobal.net [75.33.239.254]
    4 7 ms 8 ms 7 ms dist2-vlan52.chcgil.sbcglobal.net [99.164.168.130]
    5 22 ms 7 ms 7 ms bb2-g3-0.chcgil.ameritech.net [151.164.190.122]
    6 7 ms 7 ms 7 ms 151.164.95.164
    7 7 ms 7 ms 7 ms xe-2-3.bbr01.ord01.us.xeex.net [206.223.119.87]
    8 9 ms 8 ms 8 ms unknown.ord01.us.xeex.net [69.26.182.250]
    9 8 ms 7 ms 7 ms 17.208-100-32.static.steadfast.net [208.100.32.17]
    10 7 ms 8 ms 7 ms resolver1.steadfast.net [216.86.146.8]

    From Comcast

    InterNAP
    traceroute 74.63.66.114
    traceroute to 74.63.66.114 (74.63.66.114), 64 hops max, 40 byte packets
    1 10.0.0.1 (10.0.0.1) 2.675 ms 2.068 ms 2.052 ms
    2 * * *
    3 * * ge-7-19-ur01.area4.il.chicago.comcast.net (68.86.114.77) 56.292 ms
    4 68.86.90.182 (68.86.90.182) 68.778 ms * 14.106 ms
    5 COMCAST-IP.edge1.Chicago2.Level3.net (4.71.248.18) 10.559 ms 15.481 ms *
    6 xe-10-1-0.edge1.Chicago2.Level3.net (4.71.248.17) 10.573 ms 9.898 ms 10.120 ms
    7 ge-9-1.ipcolo1.Chicago1.Level3.net (4.68.101.74) 13.349 ms 11.365 ms ge-7-1.ipcolo1.Chicago1.Level3.net (4.68.101.106) 13.520 ms
    8 unknown.Level3.net (209.247.34.166) 11.739 ms 14.706 ms 12.190 ms
    9 border5.pc2-bbnet2.chg.pnap.net (64.94.32.74) 15.770 ms 18.279 ms 12.986 ms
    10 66.90.127.205 (66.90.127.205) 35.072 ms 32.761 ms 33.015 ms
    11 66.90.127.138 (66.90.127.138) 34.207 ms 32.548 ms 42.475 ms

    Steadfast:

    traceroute 216.86.146.8
    traceroute to 216.86.146.8 (216.86.146.8), 64 hops max, 40 byte packets
    1 10.0.0.1 (10.0.0.1) 2.694 ms 2.696 ms 2.023 ms
    2 * * *
    3 ge-7-19-ur01.area4.il.chicago.comcast.net (68.86.114.77) 12.545 ms 12.284 ms 9.017 ms
    4 68.86.90.178 (68.86.90.178) 13.028 ms * 10.079 ms
    5 COMCAST-IP.edge1.Chicago2.Level3.net (4.71.248.22) 16.083 ms 13.591 ms 14.013 ms
    6 xe-9-3-0.edge1.Chicago2.Level3.net (4.71.248.21) 54.549 ms 12.613 ms 10.836 ms
    7 ae-24-56.car4.Chicago1.Level3.net (4.68.101.168) 15.068 ms ae-24-54.car4.Chicago1.Level3.net (4.68.101.104) 11.704 ms ae-14-55.car4.Chicago1.Level3.net (4.68.101.136) 11.876 ms
    8 WBS-CONNECT.car4.Chicago1.Level3.net (4.79.208.154) 11.568 ms 11.806 ms 12.623 ms
    9 61.216-86-149.static.steadfast.net (216.86.149.61) 12.138 ms 12.966 ms 14.275 ms
    10 resolver1.steadfast.net (216.86.146.8) 14.370 ms 12.228 ms 15.906 ms

    From RCN

    InterNAP:
    Tracing route to . [74.63.66.114]
    over a maximum of 30 hops:

    1 8 ms 32 ms 10 ms 172.30.96.1
    2 21 ms 9 ms 10 ms mart-h1.chi-mart.il.cable.rcn.net [207.229.191.130]
    3 8 ms 19 ms 23 ms ge1-0-2.core2.chsl.il.rcn.net [207.172.19.61]
    4 11 ms 22 ms 34 ms ge5-0.border1.eqnx.il.rcn.net [207.172.19.15]
    5 11 ms 7 ms 8 ms xe-0.equinix.chcgil09.us.bb.gin.ntt.net [206.223.119.12]
    6 11 ms 16 ms 10 ms xe-3-1.r01.chcgil09.us.bb.gin.ntt.net [129.250.3.206]
    7 23 ms 38 ms 37 ms xe-3-3.r01.chcgil09.us.ce.gin.ntt.net [129.250.208.6]
    8 10 ms 14 ms 8 ms border5.pc2-bbnet2.chg.pnap.net [64.94.32.74]
    9 10 ms 32 ms 10 ms 66.90.127.205 [66.90.127.205]
    10 11 ms 14 ms 12 ms 66.90.127.138 [66.90.127.138]
    11 9 ms 23 ms 15 ms . [74.63.66.114]

    Steadfast:
    Tracing route to resolver1.steadfast.net [216.86.146.8]
    over a maximum of 30 hops:

    1 11 ms 23 ms 33 ms 172.30.96.1
    2 22 ms 13 ms 9 ms mart-h1.chi-mart.il.cable.rcn.net [207.229.191.130]
    3 15 ms 13 ms 9 ms ge0-0-2.core2.chsl.il.rcn.net [207.172.19.43]
    4 22 ms 16 ms 9 ms ge5-0.border1.eqnx.il.rcn.net [207.172.19.15]
    5 12 ms 9 ms 28 ms xe-2-3.bbr01.ord01.us.xeex.net [206.223.119.87]
    6 9 ms 12 ms 12 ms unknown.ord01.us.xeex.net [69.26.182.250]
    7 11 ms 39 ms 7 ms 17.208-100-32.static.steadfast.net [208.100.32.17]
    8 14 ms 9 ms 11 ms resolver1.steadfast.net [216.86.146.8]

    I believe that indicates that yes, we are better.

    Note: I did not pick and choose results, etc. I had friends in the area on each of those ISPs send me their traceroute results.



    How many traceroutes did they do? Im using WoW at home

    To Steadfast, to FDC/internap and to Us they were all inconsistent, QoS?


    traceroute to steadfast.net (216.86.146.9), 64 hops max, 40 byte packets
    1 192.168.1.1 (192.168.1.1) 3.375 ms 2.047 ms 1.065 ms
    2 d47-69-1-208.try.wideopenwest.com (69.47.208.1) 20.302 ms 16.118 ms 16.502 ms
    3 172.31.17.246 (172.31.17.246) 13.954 ms 14.969 ms 10.923 ms
    4 sl-gw33-chi-3-1.sprintlink.net (144.232.205.197) 14.508 ms 26.359 ms 19.529 ms
    5 sl-bb22-chi-6-0.sprintlink.net (144.232.26.21) 18.042 ms 28.461 ms 14.932 ms
    6 sl-bb20-chi-15-0.sprintlink.net (144.232.26.5) 14.457 ms 17.391 ms 15.906 ms
    7 sl-st20-chi-12-0-0.sprintlink.net (144.232.8.219) 15.871 ms 15.019 ms 14.077 ms
    8 144.232.8.114 (144.232.8.114) 13.445 ms 13.480 ms 32.928 ms
    9 WBS-CONNECT.car4.Chicago1.Level3.net (4.79.208.154) 16.409 ms 14.397 ms 14.493 ms
    10 61.216-86-149.static.steadfast.net (216.86.149.61) 13.418 ms 14.505 ms 16.073 ms
    11 utility1.steadfast.net (216.86.146.9) 18.549 ms 13.932 ms 19.047 ms


    Macintosh:~ apishdadi$ traceroute steadfast.net
    traceroute to steadfast.net (216.86.146.9), 64 hops max, 40 byte packets
    1 192.168.1.1 (192.168.1.1) 2.606 ms 0.954 ms 2.110 ms
    2 d47-69-1-208.try.wideopenwest.com (69.47.208.1) 12.150 ms 17.484 ms 13.946 ms
    3 172.31.17.246 (172.31.17.246) 16.457 ms 23.791 ms 17.110 ms
    4 sl-gw33-chi-3-1.sprintlink.net (144.232.205.197) 15.956 ms 15.399 ms 13.670 ms
    5 sl-bb22-chi-6-0.sprintlink.net (144.232.26.21) 15.740 ms 14.563 ms 47.401 ms
    6 sl-bb20-chi-15-0.sprintlink.net (144.232.26.5) 16.088 ms 16.339 ms 14.360 ms
    7 sl-st20-chi-12-0-0.sprintlink.net (144.232.8.219) 13.888 ms 15.722 ms 15.345 ms
    8 144.232.8.114 (144.232.8.114) 14.821 ms * 21.875 ms
    9 WBS-CONNECT.car4.Chicago1.Level3.net (4.79.208.154) 21.067 ms 33.561 ms 35.526 ms
    10 61.216-86-149.static.steadfast.net (216.86.149.61) 35.529 ms 34.612 ms 32.687 ms
    11 utility1.steadfast.net (216.86.146.9) 18.172 ms 24.866 ms 32.326 ms

    TO FDC
    traceroute to 74.63.66.114 (74.63.66.114), 64 hops max, 40 byte packets
    1 192.168.1.1 (192.168.1.1) 1.518 ms 1.876 ms 0.970 ms
    2 d47-69-1-208.try.wideopenwest.com (69.47.208.1) 29.041 ms 32.235 ms 35.028 ms
    3 172.31.17.246 (172.31.17.246) 30.279 ms 32.811 ms 26.716 ms
    4 sl-gw36-chi-10-0.sprintlink.net (144.223.139.253) 61.781 ms 29.415 ms 56.624 ms
    5 sl-crs1-chi-0-4-0-1.sprintlink.net (144.232.26.69) 33.607 ms 46.339 ms 24.684 ms
    6 sl-st21-chi-12-0-0.sprintlink.net (144.232.19.142) 25.175 ms 25.376 ms 19.430 ms
    7 sl-internap-117-0.sprintlink.net (144.223.241.6) 25.837 ms 13.737 ms 15.960 ms
    8 border5.pc1-bbnet1.chg.pnap.net (64.94.32.10) 22.820 ms 27.317 ms 42.548 ms
    9 66.90.127.205 (66.90.127.205) 32.903 ms 29.760 ms 26.185 ms
    10 66.90.127.138 (66.90.127.138) 14.447 ms 16.429 ms 19.701 ms


    traceroute to 74.63.66.114 (74.63.66.114), 64 hops max, 40 byte packets
    1 192.168.1.1 (192.168.1.1) 2.170 ms 10.742 ms 2.796 ms
    2 d47-69-1-208.try.wideopenwest.com (69.47.208.1) 12.947 ms 12.260 ms 11.126 ms
    3 172.31.17.246 (172.31.17.246) 14.179 ms 11.943 ms 13.931 ms
    4 sl-gw36-chi-10-0.sprintlink.net (144.223.139.253) 15.216 ms 14.232 ms 14.747 ms
    5 sl-crs1-chi-0-4-0-1.sprintlink.net (144.232.26.69) 15.053 ms * 44.949 ms
    6 sl-st21-chi-12-0-0.sprintlink.net (144.232.19.142) 15.382 ms 15.325 ms 16.277 ms
    7 sl-internap-117-0.sprintlink.net (144.223.241.6) 15.630 ms 20.496 ms 15.890 ms
    8 border5.pc1-bbnet1.chg.pnap.net (64.94.32.10) 28.376 ms 16.325 ms 62.414 ms
    9 66.90.127.205 (66.90.127.205) 51.121 ms 14.077 ms 16.899 ms
    10 66.90.127.138 (66.90.127.138) 27.997 ms 22.749 ms 25.069 ms


    TO us GIGENET

    traceroute to gigenet.com (69.65.39.163), 64 hops max, 40 byte packets
    1 192.168.1.1 (192.168.1.1) 2.300 ms 0.951 ms 1.516 ms
    2 d47-69-1-208.try.wideopenwest.com (69.47.208.1) 28.180 ms 22.468 ms 20.484 ms
    3 172.31.17.246 (172.31.17.246) 12.757 ms 12.011 ms 11.636 ms
    4 sl-gw36-chi-10-0.sprintlink.net (144.223.139.253) 22.468 ms 13.795 ms 15.192 ms
    5 sl-crs1-chi-0-4-0-1.sprintlink.net (144.232.26.69) 14.995 ms 15.678 ms 13.134 ms
    6 sl-st20-chi-4-0-0.sprintlink.net (144.232.18.153) 14.645 ms 19.729 ms 20.020 ms
    7 144.232.8.114 (144.232.8.114) 21.917 ms 36.758 ms 35.113 ms
    8 ae-11-51.car1.Chicago1.Level3.net (4.68.101.2) 26.044 ms 17.403 ms 22.202 ms
    9 CWIE-LLC.car1.Chicago1.Level3.net (4.79.65.50) 14.288 ms 16.375 ms 14.296 ms
    10 pos-2-1.chi3.servernap.com (69.39.239.170) 25.509 ms 13.819 ms 15.525 ms
    11 69.65.39.163 (69.65.39.163) 14.695 ms 16.512 ms 15.124 ms



    1 192.168.1.1 (192.168.1.1) 2.651 ms 1.721 ms 1.810 ms
    2 d47-69-1-208.try.wideopenwest.com (69.47.208.1) 11.156 ms 17.999 ms 15.621 ms
    3 172.31.17.246 (172.31.17.246) 11.327 ms 12.619 ms 13.544 ms
    4 sl-gw36-chi-10-0.sprintlink.net (144.223.139.253) 12.999 ms 14.392 ms 25.766 ms
    5 sl-crs1-chi-0-4-0-1.sprintlink.net (144.232.26.69) 12.922 ms 15.295 ms 14.569 ms
    6 sl-st20-chi-4-0-0.sprintlink.net (144.232.18.153) 31.058 ms 16.250 ms 22.396 ms
    7 144.232.8.114 (144.232.8.114) 27.127 ms 30.224 ms 25.465 ms
    8 ae-11-51.car1.Chicago1.Level3.net (4.68.101.2) 27.592 ms 35.911 ms 30.793 ms
    9 CWIE-LLC.car1.Chicago1.Level3.net (4.79.65.50) 34.235 ms 32.948 ms 35.163 ms
    10 pos-2-1.chi3.servernap.com (69.39.239.170) 36.111 ms 26.190 ms 24.822 ms
    11 69.65.39.163 (69.65.39.163) 23.997 ms 15.584 ms 22.741 ms


    I dont know but WoW Sucks, maybe i should switch to SBC thats some pretty low latency from the user end to SBC's router (to the CO), that person must be within several hundred feet of the CO.

    Im not saying those above traceroutes are incorrect, just saying some times traceroutes can be extremely volatile like mine...

    All except for tht first traceroute you posted from SBC to FDC/Internap which takes a retarded route across the country could be volatile and go up and down depending on how many you do, i just did a bunch and pasted a low one and a higher one and it was definitly not consistent, which has more to blame on WoW then it does on any of us.
    GigeNET
    Dedicated Servers + Cloud Servers + Colocation + DDOS Protection + IP Transit with FCP optimized routing
    Locations in Chicago Los Angeles and Ashburn

  18. #18
    Join Date
    Jan 2003
    Location
    Chicago, IL
    Posts
    6,889
    I just posted the ones they sent. I had the AT&T and RCN ones checked later on as well, with several other traces, and they all seemed pretty consistent. As far as consistency though, Comcast is terrible...
    Karl Zimmerman - Steadfast: Managed Dedicated Servers and Premium Colocation
    karl @ steadfast.net - Sales/Support: 312-602-2689
    Cloud Hosting, Managed Dedicated Servers, Chicago Colocation, and New Jersey Colocation
    Now Open in New Jersey! - Contact us for New Jersey colocation or dedicated servers

  19. #19
    Join Date
    Apr 2002
    Location
    chicago
    Posts
    717
    Quote Originally Posted by KarlZimmer View Post
    Well, Comcast, AT&T/SBC, and RCN make up almost the entire make-up of the eyeball networks in Chicago, so here are some traces. I used an InterNAP IP at FDC.

    From AT&T/SBC

    InterNAP:
    1 2 ms 1 ms 1 ms 10.0.0.1
    2 1 ms 1 ms 1 ms 192.168.0.1
    3 7 ms 7 ms 7 ms adsl-75-33-239-254.dsl.chcgil.sbcglobal.net [75.33.239.254]
    4 7 ms 7 ms 7 ms dist1-vlan52.chcgil.sbcglobal.net [99.164.168.129]
    5 6 ms 7 ms 8 ms bb1-g6-0.chcgil.ameritech.net [151.164.190.120]
    6 25 ms 26 ms 26 ms ex1-p5-0.eqabva.sbcglobal.net [151.164.191.134]
    7 25 ms 26 ms 27 ms asn4766-koreantelecom.eqlaca.sbcglobal.net [151.164.250.206]
    8 24 ms 25 ms 25 ms ae-2.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.86]
    9 32 ms 31 ms 31 ms as-0.r21.nycmny01.us.bb.gin.ntt.net [129.250.2.8]
    10 56 ms 57 ms 56 ms p64-2-0-0.r20.chcgil09.us.bb.gin.ntt.net [129.250.5.4]
    11 61 ms 254 ms 284 ms xe-3-1.r01.chcgil09.us.bb.gin.ntt.net [129.250.3.206]
    12 32 ms 33 ms 32 ms xe-3-3.r01.chcgil09.us.ce.gin.ntt.net [129.250.208.6]
    13 32 ms 43 ms 33 ms border5.pc2-bbnet2.chg.pnap.net [64.94.32.74]
    14 33 ms 32 ms 34 ms 66.90.127.205 [66.90.127.205]
    15 33 ms 33 ms 32 ms 66.90.127.138 [66.90.127.138]
    16 32 ms 36 ms 33 ms . [74.63.66.114]

    Steadfast:
    1 1 ms 1 ms 1 ms 10.0.0.1
    2 1 ms 1 ms 1 ms 192.168.0.1
    3 7 ms 7 ms 7 ms adsl-75-33-239-254.dsl.chcgil.sbcglobal.net [75.33.239.254]
    4 7 ms 8 ms 7 ms dist2-vlan52.chcgil.sbcglobal.net [99.164.168.130]
    5 22 ms 7 ms 7 ms bb2-g3-0.chcgil.ameritech.net [151.164.190.122]
    6 7 ms 7 ms 7 ms 151.164.95.164
    7 7 ms 7 ms 7 ms xe-2-3.bbr01.ord01.us.xeex.net [206.223.119.87]
    8 9 ms 8 ms 8 ms unknown.ord01.us.xeex.net [69.26.182.250]
    9 8 ms 7 ms 7 ms 17.208-100-32.static.steadfast.net [208.100.32.17]
    10 7 ms 8 ms 7 ms resolver1.steadfast.net [216.86.146.8]

    From Comcast

    InterNAP
    traceroute 74.63.66.114
    traceroute to 74.63.66.114 (74.63.66.114), 64 hops max, 40 byte packets
    1 10.0.0.1 (10.0.0.1) 2.675 ms 2.068 ms 2.052 ms
    2 * * *
    3 * * ge-7-19-ur01.area4.il.chicago.comcast.net (68.86.114.77) 56.292 ms
    4 68.86.90.182 (68.86.90.182) 68.778 ms * 14.106 ms
    5 COMCAST-IP.edge1.Chicago2.Level3.net (4.71.248.18) 10.559 ms 15.481 ms *
    6 xe-10-1-0.edge1.Chicago2.Level3.net (4.71.248.17) 10.573 ms 9.898 ms 10.120 ms
    7 ge-9-1.ipcolo1.Chicago1.Level3.net (4.68.101.74) 13.349 ms 11.365 ms ge-7-1.ipcolo1.Chicago1.Level3.net (4.68.101.106) 13.520 ms
    8 unknown.Level3.net (209.247.34.166) 11.739 ms 14.706 ms 12.190 ms
    9 border5.pc2-bbnet2.chg.pnap.net (64.94.32.74) 15.770 ms 18.279 ms 12.986 ms
    10 66.90.127.205 (66.90.127.205) 35.072 ms 32.761 ms 33.015 ms
    11 66.90.127.138 (66.90.127.138) 34.207 ms 32.548 ms 42.475 ms

    Steadfast:

    traceroute 216.86.146.8
    traceroute to 216.86.146.8 (216.86.146.8), 64 hops max, 40 byte packets
    1 10.0.0.1 (10.0.0.1) 2.694 ms 2.696 ms 2.023 ms
    2 * * *
    3 ge-7-19-ur01.area4.il.chicago.comcast.net (68.86.114.77) 12.545 ms 12.284 ms 9.017 ms
    4 68.86.90.178 (68.86.90.178) 13.028 ms * 10.079 ms
    5 COMCAST-IP.edge1.Chicago2.Level3.net (4.71.248.22) 16.083 ms 13.591 ms 14.013 ms
    6 xe-9-3-0.edge1.Chicago2.Level3.net (4.71.248.21) 54.549 ms 12.613 ms 10.836 ms
    7 ae-24-56.car4.Chicago1.Level3.net (4.68.101.168) 15.068 ms ae-24-54.car4.Chicago1.Level3.net (4.68.101.104) 11.704 ms ae-14-55.car4.Chicago1.Level3.net (4.68.101.136) 11.876 ms
    8 WBS-CONNECT.car4.Chicago1.Level3.net (4.79.208.154) 11.568 ms 11.806 ms 12.623 ms
    9 61.216-86-149.static.steadfast.net (216.86.149.61) 12.138 ms 12.966 ms 14.275 ms
    10 resolver1.steadfast.net (216.86.146.8) 14.370 ms 12.228 ms 15.906 ms

    From RCN

    InterNAP:
    Tracing route to . [74.63.66.114]
    over a maximum of 30 hops:

    1 8 ms 32 ms 10 ms 172.30.96.1
    2 21 ms 9 ms 10 ms mart-h1.chi-mart.il.cable.rcn.net [207.229.191.130]
    3 8 ms 19 ms 23 ms ge1-0-2.core2.chsl.il.rcn.net [207.172.19.61]
    4 11 ms 22 ms 34 ms ge5-0.border1.eqnx.il.rcn.net [207.172.19.15]
    5 11 ms 7 ms 8 ms xe-0.equinix.chcgil09.us.bb.gin.ntt.net [206.223.119.12]
    6 11 ms 16 ms 10 ms xe-3-1.r01.chcgil09.us.bb.gin.ntt.net [129.250.3.206]
    7 23 ms 38 ms 37 ms xe-3-3.r01.chcgil09.us.ce.gin.ntt.net [129.250.208.6]
    8 10 ms 14 ms 8 ms border5.pc2-bbnet2.chg.pnap.net [64.94.32.74]
    9 10 ms 32 ms 10 ms 66.90.127.205 [66.90.127.205]
    10 11 ms 14 ms 12 ms 66.90.127.138 [66.90.127.138]
    11 9 ms 23 ms 15 ms . [74.63.66.114]

    Steadfast:
    Tracing route to resolver1.steadfast.net [216.86.146.8]
    over a maximum of 30 hops:

    1 11 ms 23 ms 33 ms 172.30.96.1
    2 22 ms 13 ms 9 ms mart-h1.chi-mart.il.cable.rcn.net [207.229.191.130]
    3 15 ms 13 ms 9 ms ge0-0-2.core2.chsl.il.rcn.net [207.172.19.43]
    4 22 ms 16 ms 9 ms ge5-0.border1.eqnx.il.rcn.net [207.172.19.15]
    5 12 ms 9 ms 28 ms xe-2-3.bbr01.ord01.us.xeex.net [206.223.119.87]
    6 9 ms 12 ms 12 ms unknown.ord01.us.xeex.net [69.26.182.250]
    7 11 ms 39 ms 7 ms 17.208-100-32.static.steadfast.net [208.100.32.17]
    8 14 ms 9 ms 11 ms resolver1.steadfast.net [216.86.146.8]

    I believe that indicates that yes, we are better.

    Note: I did not pick and choose results, etc. I had friends in the area on each of those ISPs send me their traceroute results.

    Interesting.....


    FDC to RCN
    Tracing route to vl2.aggr1.chgo.il.rcn.net [207.229.191.130]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms . [74.63.64.1]
    2 <1 ms <1 ms <1 ms 66.90.127.137 [66.90.127.137]
    3 <1 ms <1 ms <1 ms border8.tenge3-3.fdcs-1.chg.pnap.net [64.74.10
    77]
    4 <1 ms <1 ms <1 ms core5.te6-2-bbnet2.chg.pnap.net [64.94.32.78]
    5 <1 ms <1 ms <1 ms ge-8-0-519.ipcolo1.Chicago1.Level3.net [209.24
    34.165]
    6 <1 ms <1 ms <1 ms ae-12-51.car2.Chicago1.Level3.net [4.68.101.3]
    7 <1 ms <1 ms <1 ms RCN-CORPORA.car2.Chicago1.Level3.net [63.208.1
    .10]
    8 1 ms <1 ms <1 ms vl2.aggr1.chgo.il.rcn.net [207.229.191.130]


    FDC to Comcast
    Tracing route to ge-7-19-ur01.area4.il.chicago.comcast.net [68.86.114.77]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms . [74.63.64.1]
    2 <1 ms <1 ms <1 ms 66.90.127.137 [66.90.127.137]
    3 <1 ms <1 ms <1 ms border8.tenge3-3.fdcs-1.chg.pnap.net [64.74.106.
    77]
    4 <1 ms <1 ms <1 ms core3.te6-1-bbnet1.chg.pnap.net [64.94.32.3]
    5 <1 ms <1 ms <1 ms TenGigabitEthernet2-4.ar5.CHI1.gblx.net [208.48.
    24.185]
    6 1 ms 1 ms 1 ms te-0-3-0-0-cr01.chicago.il.ibone.comcast.net [68
    .86.90.169]
    7 * 2 ms 1 ms te-9-3-ar01.area4.il.chicago.comcast.net [68.87.
    230.93]
    8 1 ms * 1 ms ge-7-19-ur01.area4.il.chicago.comcast.net [68.86
    .114.77]

    Trace complete.


    FDC to SBC
    Tracing route to adsl-75-33-239-254.dsl.chcgil.sbcglobal.net [75.33.239.254]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms . [74.63.64.1]
    2 <1 ms <1 ms <1 ms 66.90.127.137 [66.90.127.137]
    3 <1 ms <1 ms <1 ms border8.tenge3-3.fdcs-1.chg.pnap.net [64.74.106.
    77]
    4 <1 ms <1 ms <1 ms core3.te6-2-bbnet2.chg.pnap.net [64.94.32.67]
    5 <1 ms <1 ms <1 ms TenGigabitEthernet2-4.ar5.CHI1.gblx.net [208.48.
    24.185]
    6 <1 ms <1 ms <1 ms 67.17.109.117
    7 26 ms 25 ms 25 ms ex2-g7-0.eqchil.sbcglobal.net [151.164.248.17]
    8 26 ms 26 ms 26 ms dist2-g1-2.chcgil.ameritech.net [151.164.242.211
    ]
    9 26 ms 26 ms 26 ms adsl-75-33-239-254.dsl.chcgil.sbcglobal.net [75.
    33.239.254]

    Trace complete.
    Petr Kral - FDCServers.net LLC
    Los Angeles - Seattle - Denver - Chicago - Miami- New York - Paris - London - Madrid - Amsterdam - Frankfurt - Vienna - DATACENTERS
    10+Tbps of internet connectivity --- 10G, 20G, 40Gbps unmetered services in 17 US & EU locations

  20. #20
    Join Date
    Jan 2003
    Location
    Chicago, IL
    Posts
    6,889
    Quote Originally Posted by bummer6666 View Post
    Interesting.....
    Yes, I would say we're the same as InterNAP to RCN and Comcast, not better, the difference is that AT&T/SBC route, and I have no idea what InterNAP is doing there...
    Karl Zimmerman - Steadfast: Managed Dedicated Servers and Premium Colocation
    karl @ steadfast.net - Sales/Support: 312-602-2689
    Cloud Hosting, Managed Dedicated Servers, Chicago Colocation, and New Jersey Colocation
    Now Open in New Jersey! - Contact us for New Jersey colocation or dedicated servers

  21. #21
    Join Date
    Dec 2004
    Location
    New York, NY
    Posts
    10,574
    Quote Originally Posted by KarlZimmer View Post
    Yes, I would say we're the same as InterNAP to RCN and Comcast, not better, the difference is that AT&T/SBC route, and I have no idea what InterNAP is doing there...
    Internap isn't doing anything there - it's SBC's inbound route where the issue is.

    If you look at Petr's trace:

    Tracing route to adsl-75-33-239-254.dsl.chcgil.sbcglobal.net [75.33.239.254]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms . [74.63.64.1]
    2 <1 ms <1 ms <1 ms 66.90.127.137 [66.90.127.137]
    3 <1 ms <1 ms <1 ms border8.tenge3-3.fdcs-1.chg.pnap.net [64.74.106.
    77]
    4 <1 ms <1 ms <1 ms core3.te6-2-bbnet2.chg.pnap.net [64.94.32.67]
    5 <1 ms <1 ms <1 ms TenGigabitEthernet2-4.ar5.CHI1.gblx.net [208.48.
    24.185]
    6 <1 ms <1 ms <1 ms 67.17.109.117
    7 26 ms 25 ms 25 ms ex2-g7-0.eqchil.sbcglobal.net [151.164.248.17]
    8 26 ms 26 ms 26 ms dist2-g1-2.chcgil.ameritech.net [151.164.242.211
    ]
    9 26 ms 26 ms 26 ms adsl-75-33-239-254.dsl.chcgil.sbcglobal.net [75.
    33.239.254]

    The latency jump occurs at hop 7. This indicates that SBC's return path is not optimal which isn't really something that Internap can correct. As far as Internap is concerned, their route is looking good there.

    That said, from a gamer's perspective - the source of the problem doesn't really matter. At the end of the day, I'm sure they'd be much happier with Steadfast in terms of latency if using SBC.
    Last edited by layer0; 01-25-2008 at 03:20 PM.

  22. #22
    Join Date
    Apr 2006
    Location
    Michigan
    Posts
    135
    Quote Originally Posted by layer0 View Post
    Internap isn't doing anything there - it's SBC's inbound route where the issue is.

    If you look at Petr's trace:

    Tracing route to adsl-75-33-239-254.dsl.chcgil.sbcglobal.net [75.33.239.254]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms . [74.63.64.1]
    2 <1 ms <1 ms <1 ms 66.90.127.137 [66.90.127.137]
    3 <1 ms <1 ms <1 ms border8.tenge3-3.fdcs-1.chg.pnap.net [64.74.106.
    77]
    4 <1 ms <1 ms <1 ms core3.te6-2-bbnet2.chg.pnap.net [64.94.32.67]
    5 <1 ms <1 ms <1 ms TenGigabitEthernet2-4.ar5.CHI1.gblx.net [208.48.
    24.185]
    6 <1 ms <1 ms <1 ms 67.17.109.117
    7 26 ms 25 ms 25 ms ex2-g7-0.eqchil.sbcglobal.net [151.164.248.17]
    8 26 ms 26 ms 26 ms dist2-g1-2.chcgil.ameritech.net [151.164.242.211
    ]
    9 26 ms 26 ms 26 ms adsl-75-33-239-254.dsl.chcgil.sbcglobal.net [75.
    33.239.254]

    The latency jump occurs at hop 7. This indicates that SBC's return path is not optimal which isn't really something that Internap can correct. As far as Internap is concerned, their route is looking good there.

    That said, from a gamer's perspective - the source of the problem doesn't really matter. At the end of the day, I'm sure they'd be much happier with Steadfast in terms of latency if using SBC.
    Just an idear of what I see from Mzima:

    traceroute to 75.33.239.254 (75.33.239.254), 30 hops max, 40 byte packets
    1 72.37.229.193 (72.37.229.193) 0.759 ms 1.202 ms 1.184 ms
    2 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 7.157 ms 7.151 ms 7.137 ms
    3 ex1-g1-0.eqchil.sbcglobal.net (206.223.119.79) 62.823 ms 62.815 ms 62.802 ms
    4 dist2-g1-3.chcgil.ameritech.net (151.164.190.123) 1.325 ms * *
    5 adsl-75-33-239-254.dsl.chcgil.sbcglobal.net (75.33.239.254) 3.015 ms 3.005 ms 3.229 ms

    traceroute to 68.86.114.77 (68.86.114.77), 30 hops max, 40 byte packets
    1 72.37.229.193 (72.37.229.193) 0.609 ms 1.064 ms 1.293 ms
    2 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 7.518 ms 7.515 ms 7.505 ms
    3 4.79.210.1 (4.79.210.1) 0.987 ms 0.974 ms 0.946 ms
    4 ae-1-51.edge1.Chicago2.Level3.net (4.68.101.19) 9.925 ms ae-2-52.edge1.Chicago2.Level3.net (4.68.101.51) 1.183 ms ae-2-56.edge1.Chicago2.Level3.net (4.68.101.179) 1.161 ms
    5 te-0-3-0-4-cr01.chicago.il.ibone.comcast.net (68.86.90.177) 2.645 ms 2.640 ms 2.867 ms
    6 te-9-3-ar01.area4.il.chicago.comcast.net (68.87.230.93) 2.604 ms 2.655 ms 2.577 ms
    7 te-3-1-ur01.area4.il.chicago.comcast.net (68.87.230.94) 2.536 ms * *
    Joseph Laws
    President - Hi-Definition Gaming LLC

    (http://www.hd-gaming.com)
    Professional Gaming Services For The Professional Gamer

  23. #23
    Join Date
    Dec 2004
    Location
    New York, NY
    Posts
    10,574
    Quote Originally Posted by HiDef-Laws View Post
    Just an idear of what I see from Mzima:

    traceroute to 75.33.239.254 (75.33.239.254), 30 hops max, 40 byte packets
    1 72.37.229.193 (72.37.229.193) 0.759 ms 1.202 ms 1.184 ms
    2 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 7.157 ms 7.151 ms 7.137 ms
    3 ex1-g1-0.eqchil.sbcglobal.net (206.223.119.79) 62.823 ms 62.815 ms 62.802 ms
    4 dist2-g1-3.chcgil.ameritech.net (151.164.190.123) 1.325 ms * *
    5 adsl-75-33-239-254.dsl.chcgil.sbcglobal.net (75.33.239.254) 3.015 ms 3.005 ms 3.229 ms

    traceroute to 68.86.114.77 (68.86.114.77), 30 hops max, 40 byte packets
    1 72.37.229.193 (72.37.229.193) 0.609 ms 1.064 ms 1.293 ms
    2 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 7.518 ms 7.515 ms 7.505 ms
    3 4.79.210.1 (4.79.210.1) 0.987 ms 0.974 ms 0.946 ms
    4 ae-1-51.edge1.Chicago2.Level3.net (4.68.101.19) 9.925 ms ae-2-52.edge1.Chicago2.Level3.net (4.68.101.51) 1.183 ms ae-2-56.edge1.Chicago2.Level3.net (4.68.101.179) 1.161 ms
    5 te-0-3-0-4-cr01.chicago.il.ibone.comcast.net (68.86.90.177) 2.645 ms 2.640 ms 2.867 ms
    6 te-9-3-ar01.area4.il.chicago.comcast.net (68.87.230.93) 2.604 ms 2.655 ms 2.577 ms
    7 te-3-1-ur01.area4.il.chicago.comcast.net (68.87.230.94) 2.536 ms * *
    Yes, I'm not saying that SBC is having issues in general, but for that particular route the issue appears to be on their end.

    Here's a quick test from Gigenet:

    Code:
    # mtr --report -c 5 75.33.239.254
    HOST                                    LOSS  RCVD SENT    BEST     AVG   WORST
    69.65.40.62                               0%     5    5    0.43    0.68    1.06
    cr2.chi1.servernap.com                    0%     5    5    1.46    1.70    1.88
    ge-6-20.car1.Chicago1.Level3.net          0%     5    5    1.37    1.59    1.79
    ae-23-54.car3.Chicago1.Level3.net         0%     5    5    1.83    2.24    2.82
    sbc-level3-te.Chicago1.Level3.net         0%     5    5    1.95   22.82  105.95
    dist2-g1-2.chcgil.ameritech.net           0%     5    5    1.93    2.05    2.13
    adsl-75-33-239-254.dsl.chcgil.sbcglobal.net    0%     5    5    1.93    2.15    2.37
    
    # mtr --report -c 5 68.86.114.77
    HOST                                    LOSS  RCVD SENT    BEST     AVG   WORST
    69.65.40.62                               0%     5    5    0.32    0.47    0.73
    cr2.chi1.servernap.com                    0%     5    5    1.46    1.70    1.88
    ge-6-20.car1.Chicago1.Level3.net          0%     5    5    1.68   51.88  152.25
    ae-2-56.edge1.Chicago2.Level3.net         0%     5    5    1.79    1.90    1.97
    te-0-3-0-5-cr01.chicago.il.ibone.comcast.net    0%     5    5    2.57    5.53   16.41
    te-9-3-ar01.area4.il.chicago.comcast.net   80%     1    5    3.47    3.47    3.47
    ge-7-19-ur01.area4.il.chicago.comcast.net    0%     5    5    2.78    2.92    3.26
    As an aside, Gigenet has a great network and I think they would be perfectly suitable to the OP.

  24. #24
    Join Date
    Jan 2003
    Location
    Chicago, IL
    Posts
    6,889
    Quote Originally Posted by HiDef-Laws View Post
    Just an idear of what I see from Mzima:

    traceroute to 75.33.239.254 (75.33.239.254), 30 hops max, 40 byte packets
    1 72.37.229.193 (72.37.229.193) 0.759 ms 1.202 ms 1.184 ms
    2 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 7.157 ms 7.151 ms 7.137 ms
    3 ex1-g1-0.eqchil.sbcglobal.net (206.223.119.79) 62.823 ms 62.815 ms 62.802 ms
    4 dist2-g1-3.chcgil.ameritech.net (151.164.190.123) 1.325 ms * *
    5 adsl-75-33-239-254.dsl.chcgil.sbcglobal.net (75.33.239.254) 3.015 ms 3.005 ms 3.229 ms

    traceroute to 68.86.114.77 (68.86.114.77), 30 hops max, 40 byte packets
    1 72.37.229.193 (72.37.229.193) 0.609 ms 1.064 ms 1.293 ms
    2 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 7.518 ms 7.515 ms 7.505 ms
    3 4.79.210.1 (4.79.210.1) 0.987 ms 0.974 ms 0.946 ms
    4 ae-1-51.edge1.Chicago2.Level3.net (4.68.101.19) 9.925 ms ae-2-52.edge1.Chicago2.Level3.net (4.68.101.51) 1.183 ms ae-2-56.edge1.Chicago2.Level3.net (4.68.101.179) 1.161 ms
    5 te-0-3-0-4-cr01.chicago.il.ibone.comcast.net (68.86.90.177) 2.645 ms 2.640 ms 2.867 ms
    6 te-9-3-ar01.area4.il.chicago.comcast.net (68.87.230.93) 2.604 ms 2.655 ms 2.577 ms
    7 te-3-1-ur01.area4.il.chicago.comcast.net (68.87.230.94) 2.536 ms * *
    Well, so we're all comparing it to the same destinations:

    traceroute to 75.33.239.254 (75.33.239.254), 30 hops max, 38 byte packets
    1 gw-shared (216.86.146.1) 99.774 ms 4.038 ms 0.560 ms
    2 60.216-86-149.static.steadfast.net (216.86.149.60) 0.398 ms 0.319 ms 0.281 ms
    3 12.119.137.89 (12.119.137.89) 0.424 ms 0.372 ms 0.517 ms
    4 tbr1.cgcil.ip.att.net (12.123.4.70) 1.108 ms 2.393 ms 1.469 ms
    5 gar8.cgcil.ip.att.net (12.122.99.5) 0.842 ms 0.611 ms 0.763 ms
    6 12.122.79.86 (12.122.79.86) 50.818 ms 11.344 ms 1.208 ms
    7 dist2-g1-2.chcgil.ameritech.net (151.164.242.211) 1.618 ms 1.627 ms 1.587 ms
    8 adsl-75-33-239-254.dsl.chcgil.sbcglobal.net (75.33.239.254) 1.501 ms 1.508 ms 1.600 ms

    traceroute to 68.87.230.94 (68.87.230.94), 30 hops max, 38 byte packets
    1 gw-shared (216.86.146.1) 0.366 ms 0.257 ms 0.228 ms
    2 60.216-86-149.static.steadfast.net (216.86.149.60) 0.336 ms 0.295 ms 0.318 ms
    3 ge5-1.br03.chc01.pccwbtn.net (63.218.5.97) 1.278 ms 1.421 ms 1.379 ms
    4 64.213.176.241 (64.213.176.241) 0.659 ms 0.833 ms 0.871 ms
    5 te2-1-10G.ar5.CHI1.gblx.net (67.17.106.133) 1.238 ms 0.933 ms 0.928 ms
    6 te-0-3-0-5-cr01.chicago.il.ibone.comcast.net (68.86.90.181) 2.214 ms 25.949 ms 32.030 ms
    7 te-9-3-ar01.area4.il.chicago.comcast.net (68.87.230.93) 2.156 ms 2.097 ms 1.769 ms
    8 te-3-1-ur01.area4.il.chicago.comcast.net (68.87.230.94) 1.652 ms 1.519 ms *
    Karl Zimmerman - Steadfast: Managed Dedicated Servers and Premium Colocation
    karl @ steadfast.net - Sales/Support: 312-602-2689
    Cloud Hosting, Managed Dedicated Servers, Chicago Colocation, and New Jersey Colocation
    Now Open in New Jersey! - Contact us for New Jersey colocation or dedicated servers

  25. #25
    Join Date
    Apr 2006
    Location
    Michigan
    Posts
    135
    I traced to: 68.86.114.77 for Comcast

    Frankly, any network in Chicago is going to be great for Chicago-area connectivity unless there is an odd peer issue. The true difference between all networks is the way in which they deal and are dealt with by ISPs and their related peers throughout the midwest. I am much more concerned with support and stability than a difference of 1-2ms...I realize others in my market may not look for the same thing but I build my service around stability.

    Quote Originally Posted by KarlZimmer View Post
    Well, so we're all comparing it to the same destinations:

    traceroute to 75.33.239.254 (75.33.239.254), 30 hops max, 38 byte packets
    1 gw-shared (216.86.146.1) 99.774 ms 4.038 ms 0.560 ms
    2 60.216-86-149.static.steadfast.net (216.86.149.60) 0.398 ms 0.319 ms 0.281 ms
    3 12.119.137.89 (12.119.137.89) 0.424 ms 0.372 ms 0.517 ms
    4 tbr1.cgcil.ip.att.net (12.123.4.70) 1.108 ms 2.393 ms 1.469 ms
    5 gar8.cgcil.ip.att.net (12.122.99.5) 0.842 ms 0.611 ms 0.763 ms
    6 12.122.79.86 (12.122.79.86) 50.818 ms 11.344 ms 1.208 ms
    7 dist2-g1-2.chcgil.ameritech.net (151.164.242.211) 1.618 ms 1.627 ms 1.587 ms
    8 adsl-75-33-239-254.dsl.chcgil.sbcglobal.net (75.33.239.254) 1.501 ms 1.508 ms 1.600 ms

    traceroute to 68.87.230.94 (68.87.230.94), 30 hops max, 38 byte packets
    1 gw-shared (216.86.146.1) 0.366 ms 0.257 ms 0.228 ms
    2 60.216-86-149.static.steadfast.net (216.86.149.60) 0.336 ms 0.295 ms 0.318 ms
    3 ge5-1.br03.chc01.pccwbtn.net (63.218.5.97) 1.278 ms 1.421 ms 1.379 ms
    4 64.213.176.241 (64.213.176.241) 0.659 ms 0.833 ms 0.871 ms
    5 te2-1-10G.ar5.CHI1.gblx.net (67.17.106.133) 1.238 ms 0.933 ms 0.928 ms
    6 te-0-3-0-5-cr01.chicago.il.ibone.comcast.net (68.86.90.181) 2.214 ms 25.949 ms 32.030 ms
    7 te-9-3-ar01.area4.il.chicago.comcast.net (68.87.230.93) 2.156 ms 2.097 ms 1.769 ms
    8 te-3-1-ur01.area4.il.chicago.comcast.net (68.87.230.94) 1.652 ms 1.519 ms *
    Joseph Laws
    President - Hi-Definition Gaming LLC

    (http://www.hd-gaming.com)
    Professional Gaming Services For The Professional Gamer

  26. #26
    Join Date
    Jan 2003
    Location
    Chicago, IL
    Posts
    6,889
    Quote Originally Posted by HiDef-Laws View Post
    I traced to: 68.86.114.77 for Comcast

    Frankly, any network in Chicago is going to be great for Chicago-area connectivity unless there is an odd peer issue. The true difference between all networks is the way in which they deal and are dealt with by ISPs and their related peers throughout the midwest. I am much more concerned with support and stability than a difference of 1-2ms...I realize others in my market may not look for the same thing but I build my service around stability.
    Ah, yes, huge difference, they both have the same last traceable location and traces to both of those IPs are exactly the same...

    Also, yes, I agree that information isn't all that useful, I was asked to show how my network compared for connectivity to local ISPs and I provided that information. I never indicated there was great importance in that information, it is what was requested. Also, this did point out that there IS one of those odd peering/connection issues between AT&T/SBC and InterNAP in Chicago.

    Also, yes, I'm sure you're the only one who cares about stability...
    Karl Zimmerman - Steadfast: Managed Dedicated Servers and Premium Colocation
    karl @ steadfast.net - Sales/Support: 312-602-2689
    Cloud Hosting, Managed Dedicated Servers, Chicago Colocation, and New Jersey Colocation
    Now Open in New Jersey! - Contact us for New Jersey colocation or dedicated servers

  27. #27
    Join Date
    Aug 2006
    Location
    Los Angeles
    Posts
    166
    yea steadfast seems to have lots of happy clients and from the gameservers ive played on hosted by them ive noticed pretty good pings for centrally hosted machines

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •