Results 1 to 19 of 19
  1. #1
    Join Date
    Mar 2004
    Location
    Seattle, WA
    Posts
    2,580

    Colo4 - High Pings Anyone?

    From my laptop here in Kansas City, it seems that pings have severely increased. I was usually able to get around 30ms however now I'm experiencing an average of 77ms, and 31ms to The Planet each datacenter pulling me down to Dallas using ATT, so I know it is not my connection.

    I asked Colo4 about this and they said there is nothing wrong, however from what I see, I think there is.

    Could other users please post their pings here and if you have tried to ping them before, tell me if the pings you're getting is normal for you or also an increase....

    Thanks.
    ColoInSeattle - From 1U to cage space colocation in Seattle
    ServerStadium - Affordable Dedicated Servers
    Come visit our 18k sq ft. facility in Seattle!
    Managed Private Cloud | Colocation | Disaster Recovery | Dedicated Servers

  2. #2
    Join Date
    Dec 2004
    Location
    New York, NY
    Posts
    10,710
    Run a traceroute back from a server of yours at C4D to your local IP. traceroute <ip> in shell. Then you can post it here for member analysis.

    It is likely that they simply have a poor route going back to your ISP which can be fixed by prefrencing another, more optimal route.

    To answer your question, no I am not seeing an increased ping at this time.
    MediaLayer, LLC - www.medialayer.com Learn how we can make your website load faster, translating to better conversion rates for your business!
    The pioneers of optimized web hosting, featuring LiteSpeed Web Server & SSD Storage - Celebrating 10 Years in Business

  3. #3
    Join Date
    Mar 2004
    Location
    Seattle, WA
    Posts
    2,580
    routing is normal:

    1 1 ms <1 ms <1 ms 192.168.0.1
    2 * * * Request timed out.
    3 16 ms 8 ms 20 ms GE-1-2-ur01.independence.mo.indepen.comcast.net
    [68.87.234.73]
    4 11 ms 10 ms 9 ms 10g-3-3-ar01.independence.mo.indepen.comcast.net
    [68.87.234.9]
    5 15 ms 40 ms 42 ms 12.125.74.21
    6 76 ms 32 ms 44 ms tbr1-p011903.sl9mo.ip.att.net [12.123.24.234]
    7 34 ms 42 ms 34 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
    8 54 ms 60 ms 61 ms gar1-p370.dlrtx.ip.att.net [12.123.16.173]
    9 * * * Request timed out.
    10 37 ms 35 ms 34 ms border4.tge4-1-bbnet2.ext1.dal.pnap.net [216.52.
    191.94]
    11 36 ms 34 ms 52 ms colo4dallas-3.border4.ext1.dal.pnap.net [216.52.
    189.10]
    12 51 ms 63 ms 83 ms 206.123.64.34
    13 61 ms 63 ms 62 ms colo4dallas.com [206.123.64.250]
    ColoInSeattle - From 1U to cage space colocation in Seattle
    ServerStadium - Affordable Dedicated Servers
    Come visit our 18k sq ft. facility in Seattle!
    Managed Private Cloud | Colocation | Disaster Recovery | Dedicated Servers

  4. #4
    Join Date
    Aug 2004
    Location
    Houston, TX
    Posts
    1,405
    Everything seems normal for me. I run smokeping and from C4D to our Houston location, we are about 11ms consistently for the past 3 weeks, which then had a spike to around 20, but only shortly, which is still good.
    Eleven2 Web Hosting - World-Wide Hosting, Done Right!
    Shared Hosting | Reseller Hosting | Dedicated | Virtual Premium Servers
    Server Locations in: Dallas | Los Angeles | Singapore | Amsterdam

  5. #5
    Join Date
    Dec 2004
    Location
    New York, NY
    Posts
    10,710
    Quote Originally Posted by Virpus-Ken
    routing is normal:

    1 1 ms <1 ms <1 ms 192.168.0.1
    2 * * * Request timed out.
    3 16 ms 8 ms 20 ms GE-1-2-ur01.independence.mo.indepen.comcast.net
    [68.87.234.73]
    4 11 ms 10 ms 9 ms 10g-3-3-ar01.independence.mo.indepen.comcast.net
    [68.87.234.9]
    5 15 ms 40 ms 42 ms 12.125.74.21
    6 76 ms 32 ms 44 ms tbr1-p011903.sl9mo.ip.att.net [12.123.24.234]
    7 34 ms 42 ms 34 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
    8 54 ms 60 ms 61 ms gar1-p370.dlrtx.ip.att.net [12.123.16.173]
    9 * * * Request timed out.
    10 37 ms 35 ms 34 ms border4.tge4-1-bbnet2.ext1.dal.pnap.net [216.52.
    191.94]
    11 36 ms 34 ms 52 ms colo4dallas-3.border4.ext1.dal.pnap.net [216.52.
    189.10]
    12 51 ms 63 ms 83 ms 206.123.64.34
    13 61 ms 63 ms 62 ms colo4dallas.com [206.123.64.250]
    Please provide the traceroute from the other side (not from your side, but C4D) as instructed above.
    MediaLayer, LLC - www.medialayer.com Learn how we can make your website load faster, translating to better conversion rates for your business!
    The pioneers of optimized web hosting, featuring LiteSpeed Web Server & SSD Storage - Celebrating 10 Years in Business

  6. #6
    Join Date
    Mar 2004
    Location
    Seattle, WA
    Posts
    2,580
    traceroute to 69.247.194.122 (69.247.194.122), 30 hops max, 38 byte packets
    1 65.99.208.217 (65.99.208.217) 0.475 ms 0.395 ms 0.386 ms
    2 206.123.64.25 (206.123.64.25) 0.447 ms 0.413 ms 0.401 ms
    3 4.78.224.73 (4.78.224.73) 1.699 ms 1.870 ms 1.512 ms
    4 ae-2-54.bbr2.Dallas1.Level3.net (4.68.122.97) 1.998 ms ae-2-52.bbr2.Dallas1.Level3.net (4.68.122.33) 2.047 ms ae-2-56.bbr2.Dallas1.Level3.net (4.68.122.161) 1.894 ms
    5 as-1-0.bbr2.LosAngeles1.Level3.net (64.159.0.246) 33.947 ms 33.865 ms ae-0-0.bbr1.LosAngeles1.Level3.net (64.159.1.125) 33.974 ms
    6 ae-21-52.car1.LosAngeles1.Level3.net (4.68.102.44) 33.114 ms 33.580 ms 33.553 ms
    7 192.205.33.229 (192.205.33.229) 30.207 ms 192.205.33.225 (192.205.33.225) 33.099 ms 192.205.33.229 (192.205.33.229) 30.731 ms
    8 12.127.3.214 (12.127.3.214) 50.457 ms 50.840 ms 50.781 ms
    MPLS Label=32407 CoS=5 TTL=1 S=0
    9 tbr2-cl21.sl9mo.ip.att.net (12.122.10.13) 50.639 ms 50.437 ms 51.597 ms
    MPLS Label=32456 CoS=5 TTL=1 S=0
    10 gar2-p370.sl9mo.ip.att.net (12.123.24.237) 47.430 ms 47.230 ms 47.332 ms
    11 12.125.74.22 (12.125.74.22) 53.761 ms 53.097 ms 53.164 ms
    12 10g-5-3-ur01.independence.mo.indepen.comcast.net (68.87.234.10) 54.021 ms 54.437 ms 53.688 ms




    Rodney-E2,

    I skimmed, and your comment was very unnecessary
    ColoInSeattle - From 1U to cage space colocation in Seattle
    ServerStadium - Affordable Dedicated Servers
    Come visit our 18k sq ft. facility in Seattle!
    Managed Private Cloud | Colocation | Disaster Recovery | Dedicated Servers

  7. #7
    Join Date
    Aug 2004
    Location
    Houston, TX
    Posts
    1,405
    That trace looks pretty darn normal for me.
    Eleven2 Web Hosting - World-Wide Hosting, Done Right!
    Shared Hosting | Reseller Hosting | Dedicated | Virtual Premium Servers
    Server Locations in: Dallas | Los Angeles | Singapore | Amsterdam

  8. #8
    Join Date
    Dec 2004
    Location
    New York, NY
    Posts
    10,710
    Quote Originally Posted by Virpus-Ken
    traceroute to 69.247.194.122 (69.247.194.122), 30 hops max, 38 byte packets
    1 65.99.208.217 (65.99.208.217) 0.475 ms 0.395 ms 0.386 ms
    2 206.123.64.25 (206.123.64.25) 0.447 ms 0.413 ms 0.401 ms
    3 4.78.224.73 (4.78.224.73) 1.699 ms 1.870 ms 1.512 ms
    4 ae-2-54.bbr2.Dallas1.Level3.net (4.68.122.97) 1.998 ms ae-2-52.bbr2.Dallas1.Level3.net (4.68.122.33) 2.047 ms ae-2-56.bbr2.Dallas1.Level3.net (4.68.122.161) 1.894 ms
    5 as-1-0.bbr2.LosAngeles1.Level3.net (64.159.0.246) 33.947 ms 33.865 ms ae-0-0.bbr1.LosAngeles1.Level3.net (64.159.1.125) 33.974 ms
    6 ae-21-52.car1.LosAngeles1.Level3.net (4.68.102.44) 33.114 ms 33.580 ms 33.553 ms
    7 192.205.33.229 (192.205.33.229) 30.207 ms 192.205.33.225 (192.205.33.225) 33.099 ms 192.205.33.229 (192.205.33.229) 30.731 ms
    8 12.127.3.214 (12.127.3.214) 50.457 ms 50.840 ms 50.781 ms
    MPLS Label=32407 CoS=5 TTL=1 S=0
    9 tbr2-cl21.sl9mo.ip.att.net (12.122.10.13) 50.639 ms 50.437 ms 51.597 ms
    MPLS Label=32456 CoS=5 TTL=1 S=0
    10 gar2-p370.sl9mo.ip.att.net (12.123.24.237) 47.430 ms 47.230 ms 47.332 ms
    11 12.125.74.22 (12.125.74.22) 53.761 ms 53.097 ms 53.164 ms
    12 10g-5-3-ur01.independence.mo.indepen.comcast.net (68.87.234.10) 54.021 ms 54.437 ms 53.688 ms

    Bad route as I suspected.

    C4D is wrong when they say there is no problem here.

    Have them preference Internap for this route.
    MediaLayer, LLC - www.medialayer.com Learn how we can make your website load faster, translating to better conversion rates for your business!
    The pioneers of optimized web hosting, featuring LiteSpeed Web Server & SSD Storage - Celebrating 10 Years in Business

  9. #9
    Join Date
    Mar 2004
    Location
    Seattle, WA
    Posts
    2,580
    Routing outbound seems to be a bit weird. Goes all the way to LA then to STL...
    ColoInSeattle - From 1U to cage space colocation in Seattle
    ServerStadium - Affordable Dedicated Servers
    Come visit our 18k sq ft. facility in Seattle!
    Managed Private Cloud | Colocation | Disaster Recovery | Dedicated Servers

  10. #10
    Join Date
    Dec 2004
    Location
    New York, NY
    Posts
    10,710
    Quote Originally Posted by Virpus-Ken
    Routing outbound seems to be a bit weird. Goes all the way to LA then to STL...
    Indeed. That is the cause for the latency

    Hope C4D takes care of this. I remember I've brought up similar routes in the past with dreadful performance, but they never fixed them and claimed everything was okay. *shrug*
    MediaLayer, LLC - www.medialayer.com Learn how we can make your website load faster, translating to better conversion rates for your business!
    The pioneers of optimized web hosting, featuring LiteSpeed Web Server & SSD Storage - Celebrating 10 Years in Business

  11. #11
    Join Date
    Mar 2004
    Location
    Seattle, WA
    Posts
    2,580
    Quote Originally Posted by Rodney-E2
    That trace looks pretty darn normal for me.
    Please just do not post in this thread any longer. *sighs*
    ColoInSeattle - From 1U to cage space colocation in Seattle
    ServerStadium - Affordable Dedicated Servers
    Come visit our 18k sq ft. facility in Seattle!
    Managed Private Cloud | Colocation | Disaster Recovery | Dedicated Servers

  12. #12
    Join Date
    Mar 2004
    Location
    Seattle, WA
    Posts
    2,580
    Quote Originally Posted by layer0
    Indeed. That is the cause for the latency

    Hope C4D takes care of this. I remember I've brought up similar routes in the past with dreadful performance, but they never fixed them and claimed everything was okay. *shrug*
    Ah. Well we'll see how it goes. I've never had a problem with them as far as network performance; this would be the first. I just updated the ticket and will see what they say.
    ColoInSeattle - From 1U to cage space colocation in Seattle
    ServerStadium - Affordable Dedicated Servers
    Come visit our 18k sq ft. facility in Seattle!
    Managed Private Cloud | Colocation | Disaster Recovery | Dedicated Servers

  13. #13
    Join Date
    Nov 2005
    Posts
    3,944
    Shouldn't be too hard for them to switch the outbound provider your going through

  14. #14
    This is the route that Level3 is preferring right now, as well as our BGP and FCP. That does not mean that it is not what you are used to seeing. There may be an issue on Level3, but their equipment is designed to route around issues. This may be the best route out there to get from us to you.

    We called and opened a ticket with Level3 and got back the response that it is currently the best route. That doesnt mean it has changed for good or that anyone is saying there is not an issue somewhere from point A to B. If there is an issue the equipment on Level3 is properly routing you to the next best route.

    We have no other tickets opened this evening for any network related issue. Again, this does not in any way mean that I am saying the route between these 2 points was not affected this evening. I believe you when you say what it was before, but most times the alternate route is not going to be as fast as the original. If Plan B takes you up to 70ms with 0 packet loss you are fortunate compared to many others.

    Layer0, you jump in every post on WHT and other forums that even begins to question us and make statements to make it look like the absolute worst case scenario is happening. This thread only took 6 minutes for you to jump on. Obviously, being anonymous makes it pretty difficult to check up on your statements about your previous reports. Care to tell your name or company name so I can check on the specifics of your tickets you opened?
    Looking for next opportunity

  15. #15
    Join Date
    Dec 2004
    Location
    New York, NY
    Posts
    10,710
    Quote Originally Posted by Colo4-Paul
    This is the route that Level3 is preferring right now, as well as our BGP and FCP. That does not mean that it is not what you are used to seeing. There may be an issue on Level3, but their equipment is designed to route around issues. This may be the best route out there to get from us to you.

    We called and opened a ticket with Level3 and got back the response that it is currently the best route. That doesnt mean it has changed for good or that anyone is saying there is not an issue somewhere from point A to B. If there is an issue the equipment on Level3 is properly routing you to the next best route.

    We have no other tickets opened this evening for any network related issue. Again, this does not in any way mean that I am saying the route between these 2 points was not affected this evening. I believe you when you say what it was before, but most times the alternate route is not going to be as fast as the original. If Plan B takes you up to 70ms with 0 packet loss you are fortunate compared to many others.

    Layer0, you jump in every post on WHT and other forums that even begins to question us and make statements to make it look like the absolute worst case scenario is happening. This thread only took 6 minutes for you to jump on. Obviously, being anonymous makes it pretty difficult to check up on your statements about your previous reports. Care to tell your name or company name so I can check on the specifics of your tickets you opened?
    You don't have to go through so much analysis.

    Simply preference Internap for your outbound route. The inbound route goes fine over Internap. This is the most basic stuff ever.

    A friend linked me to this thread. I frequent this forum often and it isn't rare for me to respond to a thread quickly.

    I am not treating this as a major issue, but I do find it a major issue that you can see the simplicity in that you can just preference Internap for this particular route on your side and call it a day...you use Internap for other Comcast routes, why not this one?

    I like to keep my anonymity on these forums, I hope you respect that.

    P.S. I have never posted on 'another forum' about you.

    P.S. 2: Internap FCP isn't an 'end-all' 'be-all' solution. There WILL be times such as this where you have to do manual tweaks.
    MediaLayer, LLC - www.medialayer.com Learn how we can make your website load faster, translating to better conversion rates for your business!
    The pioneers of optimized web hosting, featuring LiteSpeed Web Server & SSD Storage - Celebrating 10 Years in Business

  16. #16
    Join Date
    Mar 2004
    Location
    Seattle, WA
    Posts
    2,580
    Looks like Colo4Dallas is now routing over InterNAP

    traceroute to 69.247.194.122 (69.247.194.122), 30 hops max, 38 byte packets
    1 65.99.208.217 (65.99.208.217) 0.500 ms 12.838 ms 0.773 ms
    2 206.123.64.25 (206.123.64.25) 0.476 ms 0.454 ms 0.408 ms
    3 206.123.64.22 (206.123.64.22) 0.372 ms 0.308 ms 0.305 ms
    4 border4.g3-2.colo4dallas-3.ext1.dal.pnap.net (216.52.189.9) 1.304 ms 0.855 ms 0.871 ms
    5 core4.ge3-0-bbnet2.ext1.dal.pnap.net (216.52.191.99) 0.849 ms 0.952 ms 0.801 ms
    6 12.119.136.21 (12.119.136.21) 0.828 ms 1.560 ms 1.053 ms
    7 tbr2-p011303.dlstx.ip.att.net (12.123.16.166) 19.069 ms 18.596 ms 20.203 ms
    MPLS Label=31643 CoS=5 TTL=1 S=0
    8 tbr1-cl6.sl9mo.ip.att.net (12.122.10.89) 21.388 ms 19.259 ms 20.524 ms
    MPLS Label=31316 CoS=5 TTL=1 S=0
    9 gar2-p360.sl9mo.ip.att.net (12.123.24.233) 20.394 ms 26.629 ms 26.851 ms
    10 12.125.74.22 (12.125.74.22) 37.154 ms 25.116 ms 28.590 ms
    11 10g-5-3-ur01.independence.mo.indepen.comcast.net (68.87.234.10) 25.075 ms * 33.580 ms


    Thanks Colo4!
    ColoInSeattle - From 1U to cage space colocation in Seattle
    ServerStadium - Affordable Dedicated Servers
    Come visit our 18k sq ft. facility in Seattle!
    Managed Private Cloud | Colocation | Disaster Recovery | Dedicated Servers

  17. #17
    Join Date
    Dec 2004
    Location
    New York, NY
    Posts
    10,710
    Paul,

    So which is more optimal?

    traceroute to 69.247.194.122 (69.247.194.122), 30 hops max, 38 byte packets
    1 65.99.208.217 (65.99.208.217) 0.475 ms 0.395 ms 0.386 ms
    2 206.123.64.25 (206.123.64.25) 0.447 ms 0.413 ms 0.401 ms
    3 4.78.224.73 (4.78.224.73) 1.699 ms 1.870 ms 1.512 ms
    4 ae-2-54.bbr2.Dallas1.Level3.net (4.68.122.97) 1.998 ms ae-2-52.bbr2.Dallas1.Level3.net (4.68.122.33) 2.047 ms ae-2-56.bbr2.Dallas1.Level3.net (4.68.122.161) 1.894 ms
    5 as-1-0.bbr2.LosAngeles1.Level3.net (64.159.0.246) 33.947 ms 33.865 ms ae-0-0.bbr1.LosAngeles1.Level3.net (64.159.1.125) 33.974 ms
    6 ae-21-52.car1.LosAngeles1.Level3.net (4.68.102.44) 33.114 ms 33.580 ms 33.553 ms
    7 192.205.33.229 (192.205.33.229) 30.207 ms 192.205.33.225 (192.205.33.225) 33.099 ms 192.205.33.229 (192.205.33.229) 30.731 ms
    8 12.127.3.214 (12.127.3.214) 50.457 ms 50.840 ms 50.781 ms
    MPLS Label=32407 CoS=5 TTL=1 S=0
    9 tbr2-cl21.sl9mo.ip.att.net (12.122.10.13) 50.639 ms 50.437 ms 51.597 ms
    MPLS Label=32456 CoS=5 TTL=1 S=0
    10 gar2-p370.sl9mo.ip.att.net (12.123.24.237) 47.430 ms 47.230 ms 47.332 ms
    11 12.125.74.22 (12.125.74.22) 53.761 ms 53.097 ms 53.164 ms
    12 10g-5-3-ur01.independence.mo.indepen.comcast.net (68.87.234.10) 54.021 ms 54.437 ms 53.688 ms
    traceroute to 69.247.194.122 (69.247.194.122), 30 hops max, 38 byte packets
    1 65.99.208.217 (65.99.208.217) 0.500 ms 12.838 ms 0.773 ms
    2 206.123.64.25 (206.123.64.25) 0.476 ms 0.454 ms 0.408 ms
    3 206.123.64.22 (206.123.64.22) 0.372 ms 0.308 ms 0.305 ms
    4 border4.g3-2.colo4dallas-3.ext1.dal.pnap.net (216.52.189.9) 1.304 ms 0.855 ms 0.871 ms
    5 core4.ge3-0-bbnet2.ext1.dal.pnap.net (216.52.191.99) 0.849 ms 0.952 ms 0.801 ms
    6 12.119.136.21 (12.119.136.21) 0.828 ms 1.560 ms 1.053 ms
    7 tbr2-p011303.dlstx.ip.att.net (12.123.16.166) 19.069 ms 18.596 ms 20.203 ms
    MPLS Label=31643 CoS=5 TTL=1 S=0
    8 tbr1-cl6.sl9mo.ip.att.net (12.122.10.89) 21.388 ms 19.259 ms 20.524 ms
    MPLS Label=31316 CoS=5 TTL=1 S=0
    9 gar2-p360.sl9mo.ip.att.net (12.123.24.233) 20.394 ms 26.629 ms 26.851 ms
    10 12.125.74.22 (12.125.74.22) 37.154 ms 25.116 ms 28.590 ms
    11 10g-5-3-ur01.independence.mo.indepen.comcast.net (68.87.234.10) 25.075 ms * 33.580 ms


    Do you finally understand my point here?
    MediaLayer, LLC - www.medialayer.com Learn how we can make your website load faster, translating to better conversion rates for your business!
    The pioneers of optimized web hosting, featuring LiteSpeed Web Server & SSD Storage - Celebrating 10 Years in Business

  18. #18
    No change was made on our part. No route changes manually "tweaked." As I said in my post, I don’t doubt that a route changed to one that was not as good as the route normally chosen. We didn’t change anything manually, nor would I imagine that Level3 did. There was more than likely an issue that was routed around either by Level3 or the FCP.

    I never said the FCP was the end all solution. But route optimization performed by a technology like the FCP is better than just running plain ol' vanilla BGP, even if you try to manipulate routes when you find one. No human could analyze as much traffic 24/7 and make changes. In this case I would simply suggest that the FCP found a better route and manipulated the BGP tables. This is the technology we chose and it is no doubt that it has improved the performance of a network that was already great. That being said, can it catch every route every time? No.

    Layer0, you are arguing and trying to make a point with someone that is not arguing or trying to say you are wrong. We are not saying that we couldnt manipulate a route. It is our policy not to do it except in a case where there is packet loss. Going from 20 - 70ms is not extreme.
    Looking for next opportunity

  19. #19
    Join Date
    Mar 2004
    Location
    Seattle, WA
    Posts
    2,580
    It went back...I wonder why FCP would have went back to Level 3 when InterNAP was found to be the best route previously

    traceroute to 69.247.194.122 (69.247.194.122), 30 hops max, 38 byte packets
    1 65.99.208.217 (65.99.208.217) 0.460 ms 0.428 ms 0.398 ms
    2 206.123.64.25 (206.123.64.25) 0.470 ms 0.410 ms 0.408 ms
    3 4.78.224.73 (4.78.224.73) 1.743 ms 1.638 ms 1.750 ms
    4 ae-2-52.bbr2.Dallas1.Level3.net (4.68.122.33) 1.964 ms ae-2-54.bbr2.Dallas1.Level3.net (4.68.122.97) 1.792 ms 1.817 ms
    5 as-1-0.bbr2.LosAngeles1.Level3.net (64.159.0.246) 99.415 ms 56.794 ms 34.239 ms
    6 ae-11-55.car1.LosAngeles1.Level3.net (4.68.102.140) 33.725 ms 34.417 ms ae-21-56.car1.LosAngeles1.Level3.net (4.68.102.172) 33.405 ms
    7 192.205.33.225 (192.205.33.225) 32.940 ms 192.205.33.229 (192.205.33.229) 30.544 ms 192.205.33.225 (192.205.33.225) 33.050 ms
    8 12.127.3.214 (12.127.3.214) 50.644 ms 50.636 ms 50.334 ms
    MPLS Label=32407 CoS=5 TTL=1 S=0
    9 tbr2-cl21.sl9mo.ip.att.net (12.122.10.13) 50.365 ms 50.186 ms 50.580 ms
    MPLS Label=32481 CoS=5 TTL=1 S=0
    10 gar2-p370.sl9mo.ip.att.net (12.123.24.237) 47.966 ms 47.353 ms 46.821 ms
    11 12.125.74.22 (12.125.74.22) 52.788 ms 53.164 ms 53.224 ms
    12 10g-5-3-ur01.independence.mo.indepen.comcast.net (68.87.234.10) 54.301 ms 53.242 ms 53.337 ms
    ColoInSeattle - From 1U to cage space colocation in Seattle
    ServerStadium - Affordable Dedicated Servers
    Come visit our 18k sq ft. facility in Seattle!
    Managed Private Cloud | Colocation | Disaster Recovery | Dedicated Servers

Posting Permissions

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