Results 1 to 19 of 19
  1. #1
    Join Date
    Aug 2001
    Posts
    287

    ThePlanet Houston Datacenter 1 & 2 having huge issues

    Has anyone else been having big latency issues with ThePlanet (EV1 Houston 1 or 2) datacenter?

    I called and they said they are having issues which was causing slow connection. If this was the case there would be at least some threads going on in here about it. Anyone else can confirm?

  2. #2
    Join Date
    Jun 2001
    Location
    Cheltenham
    Posts
    2,617
    http://www.webhostingtalk.com/forumdisplay.php?f=59

    check out the thread over there.
    l 201TB.com • 201TB bandwidth as standard in three USA DC’s. KVMoIP, auto reboot & OS install all included - Now available in the Netherlands!
    l udedi.com • UK, USA & NL unmetered 100mb & 1GB 100TB premium bandwidth servers
    l Assiva Ltd • UK Shared & Reseller LiteSpeed • 10 years of hosting • R1Soft

  3. #3
    Join Date
    Apr 2000
    Location
    California
    Posts
    3,051
    I'm not seeing any issues with them, but I've never used EV1, so I'm assuming that's the old EV1 DC they bought out/merged with that are having issues (at least from your end)?

  4. #4
    Join Date
    Aug 2001
    Posts
    287
    hmm. I see nothing listed on those forums. Could be the guy on the phone was blowing my horns?

  5. #5
    Join Date
    May 2005
    Location
    Houston, TX
    Posts
    193
    Quote Originally Posted by MMH-Moe View Post
    Has anyone else been having big latency issues with ThePlanet (EV1 Houston 1 or 2) datacenter?

    I called and they said they are having issues which was causing slow connection. If this was the case there would be at least some threads going on in here about it. Anyone else can confirm?
    I just spoke with a NOC manager, and we aren't experiencing any network problems at H1/H2, so it might be on a transit path into/out of the DCs. If you can post a traceroute, we might be able to discern where the connection is slowing down and make sure we're doing everything we can to get you the smoothest connection.
    Kevin Hazard
    Director, Digital Content
    SoftLayer, an IBM Companyhttp://twitter.com/softlayer

  6. #6
    HTH

    Code:
    --- 216.200.251.26 ping statistics ---
    24 packets transmitted, 19 received, 20% packet loss, time 23027ms
    rtt min/avg/max/mdev = 69.452/70.399/71.890/0.731 ms, pipe 2
    
    
    .... snip ....
     4  abovenet.ge2-8.br02.chc01.pccwbtn.net (63.218.5.42)  1.242 ms  1.842 ms  1.491 ms
    Icmp checksum is wrong
     5  so-0-1-0.mpr1.ord2.us.above.net (64.125.30.146)  1.371 msIcmp checksum is wrong
      1.475 ms *
    Icmp checksum is wrong
     6  so-2-0-0.cr1.dfw2.us.above.net (64.125.30.245)  27.745 msIcmp checksum is wrong
      27.420 msIcmp checksum is wrong
      27.711 ms
     7  so-1-1-0.mpr3.iah1.us.above.net (64.125.26.130)  32.590 ms  38.071 ms  32.590 ms
     8  * 289.ev1servers.net (216.200.251.26)  68.806 ms  67.289 ms
     9  ivhou-207-218-223-103.ev1servers.net (207.218.223.103)  68.076 ms  68.645 ms

  7. #7
    Join Date
    Jan 2005
    Posts
    296
    I'm seeing some problems as well.

    2 3 ms 3 ms 3 ms g0-1-0-440.car1.acm.pitbpa.e-xpedient.com [206.2
    10.75.248]
    3 3 ms 4 ms 3 ms 63.160.2.9
    4 28 ms 62 ms 29 ms 144.232.13.145
    5 54 ms 40 ms 22 ms sl-bb20-msq-2-0.sprintlink.net [144.232.20.74]
    6 30 ms 34 ms 34 ms sl-bb21-msq-15-0.sprintlink.net [144.232.9.110]

    7 26 ms 26 ms 26 ms sl-bb27-rly-8-0.sprintlink.net [144.232.20.73]
    8 30 ms 25 ms 39 ms sl-bb26-rly-13-0.sprintlink.net [144.232.14.181]

    9 27 ms 36 ms 56 ms sl-bb21-dc-12-0-0.sprintlink.net [144.232.9.212]

    10 40 ms 48 ms 33 ms sl-crs2-dc-0-4-0-0.sprintlink.net [144.232.15.19
    ]
    11 64 ms 65 ms 64 ms sl-crs2-fw-0-12-0-1.sprintlink.net [144.232.19.1
    02]
    12 82 ms 80 ms 65 ms sl-st21-dal-12-0-0.sprintlink.net [144.232.9.194
    ]
    13 164 ms 170 ms 164 ms sl-timewarner-174329-0.sprintlink.net [144.228.1
    33.222]
    14 489 ms * * 216-54-253-2.ev1.net.demarc [216.54.253.2]
    15 * * * Request timed out.
    16 506 ms 530 ms * ivhou-207-218-223-115.ev1servers.net [207.218.22
    3.115]

  8. #8
    Join Date
    May 2005
    Location
    Houston, TX
    Posts
    193
    Following up with those traceroutes, the NOC thinks the latency could have been caused by a DDoS attack we were mitigating ... The attack was handled very quickly, so it wouldn't explain the apparent latency earlier this morning. If you continue to have trouble getting a quick connection, let me know, and I'll keep sleuthing.
    Kevin Hazard
    Director, Digital Content
    SoftLayer, an IBM Companyhttp://twitter.com/softlayer

  9. #9
    Join Date
    Jan 2005
    Posts
    296
    It's fine for me now.

  10. #10
    Join Date
    Aug 2001
    Posts
    287
    Hello,

    YOu Might want to check your Savvis connection. It seems there might be an issue with the routing. See below:


    7 12 ms 12 ms 12 ms te-4-2-0.rar3.chicago-il.us.xo.net [207.88.12.17]
    8 11 ms 12 ms 12 ms 207.88.12.138.ptr.us.xo.net [207.88.12.138]
    9 12 ms 11 ms 12 ms bpr1-so-2-1-0.chicagoequinix.savvis.net [208.17.226.21]
    10 12 ms 12 ms 12 ms ber1-ge-4-1.chicagoequinix.savvis.net [204.70.14.250]
    11 3039 ms 1268 ms 12 ms ber1-vlan-241.chicago.savvis.net [204.70.196.21
    12 2195 ms 695 ms 1353 ms cr2-tengige0-7-5-0.dallas.savvis.net [204.70.19.29]
    13 229 ms 44 ms 44 ms 208.172.139.2
    14 45 ms 45 ms 45 ms gphou2-209-85-0-109.ev1servers.net [209.85.0.10]
    15 50 ms 44 ms 44 ms gphou2-209-85-0-109.ev1servers.net [209.85.0.10]
    16 44 ms 43 ms 43 ms Mydomain.com [209.85.xxx.xxx]

    Trace complete.

  11. #11
    Join Date
    Jan 2003
    Location
    Chicago, IL
    Posts
    6,889
    Quote Originally Posted by MMH-Moe View Post
    Hello,

    YOu Might want to check your Savvis connection. It seems there might be an issue with the routing. See below:


    7 12 ms 12 ms 12 ms te-4-2-0.rar3.chicago-il.us.xo.net [207.88.12.17]
    8 11 ms 12 ms 12 ms 207.88.12.138.ptr.us.xo.net [207.88.12.138]
    9 12 ms 11 ms 12 ms bpr1-so-2-1-0.chicagoequinix.savvis.net [208.17.226.21]
    10 12 ms 12 ms 12 ms ber1-ge-4-1.chicagoequinix.savvis.net [204.70.14.250]
    11 3039 ms 1268 ms 12 ms ber1-vlan-241.chicago.savvis.net [204.70.196.21
    12 2195 ms 695 ms 1353 ms cr2-tengige0-7-5-0.dallas.savvis.net [204.70.19.29]
    13 229 ms 44 ms 44 ms 208.172.139.2
    14 45 ms 45 ms 45 ms gphou2-209-85-0-109.ev1servers.net [209.85.0.10]
    15 50 ms 44 ms 44 ms gphou2-209-85-0-109.ev1servers.net [209.85.0.10]
    16 44 ms 43 ms 43 ms Mydomain.com [209.85.xxx.xxx]

    Trace complete.
    It seems the issue is with XO's routing, not ThePlanet's. The issue occurs in Chicago, on Savvis, well before it reaches ThePlanet.
    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

  12. #12
    Join Date
    Apr 2005
    Posts
    1,711
    Yeah, I called yesterday, they told me right off the bat they were getting attacked. Because my pings were timing out, and then getting laggy, which would be consistent with an attack then mitigation. Gotta love Cisco Guard.

  13. #13
    Join Date
    Aug 2001
    Posts
    287
    Karl,

    You sure, XO gets done at Hop 8 and the 3000 jump came at Hop 11, 3 hopes into the savvis network. How is it a XO issue? Sorry, I'm not that experienced.

    7 12 ms 12 ms 12 ms te-4-2-0.rar3.chicago-il.us.xo.net [207.88.12.17]
    8 11 ms 12 ms 12 ms 207.88.12.138.ptr.us.xo.net [207.88.12.138]
    9 12 ms 11 ms 12 ms bpr1-so-2-1-0.chicagoequinix.savvis.net [208.17.226.21]
    10 12 ms 12 ms 12 ms ber1-ge-4-1.chicagoequinix.savvis.net [204.70.14.250]
    11 3039 ms 1268 ms 12 ms ber1-vlan-241.chicago.savvis.net [204.70.196.21
    12 2195 ms 695 ms 1353 ms cr2-tengige0-7-5-0.dallas.savvis.net [204.70.19.29]
    13 229 ms 44 ms 44 ms 208.172.139.2
    14 45 ms 45 ms 45 ms gphou2-209-85-0-109.ev1servers.net [209.85.0.10]
    15 50 ms 44 ms 44 ms gphou2-209-85-0-109.ev1servers.net [209.85.0.10]
    16 44 ms 43 ms 43 ms Mydomain.com [209.85.xxx.xxx]

    Trace complete.

  14. #14
    This trace points out (once again) problems with a Savvis router(204.70.196.29 ?) between TX and CA (in our case)... This is the same router that we've seen major problems with several times over the past few weeks. I have been told that this is outside of The Planet network; what can we do about it (nobody in California can connect right now... as far as my client is concerned anyhow...)?

    TP told me they emailed Savvis to see if my clien't ip can be routed around this (thanks), but is that really a solution? What about the hundreds of thousands of other people that this is likely affecting on a regular basis?

    Apparently, "pressuring" Savvis to do something about this won't do any good... Anybody have a phone number? I'm willing to give it a try!

    Tracing route to somesite.com [75.125.xxx.xxx]

    over a maximum of 30 hops:

    1 38 ms 3 ms 1 ms 74.8.111.xxx

    2 4 ms 5 ms 5 ms ag-accessre-multilink48.laxca01.paetec.net [74.8.108.121]

    3 5 ms 6 ms 5 ms gi-4-0-1-12.core02.lsajca01.paetec.net [66.251.30.178]

    4 22 ms 15 ms 10 ms gi-2-0-1.gw01.lsajca01.paetec.net [66.251.30.36]

    5 5 ms 5 ms 5 ms 12.118.130.69

    6 6 ms 6 ms 7 ms tbr1.la2ca.ip.att.net [12.123.199.106]

    7 5 ms 5 ms 5 ms 12.127.3.217

    8 21 ms 6 ms 5 ms 204.255.169.70

    9 336 ms 708 ms 2725 ms cr2-tengige0-7-5-0.dallas.savvis.net [204.70.196.29]

    10 45 ms 45 ms 45 ms 208.172.139.2

    11 42 ms 41 ms 42 ms gphou2-209-85-0-101.ev1servers.net [209.85.0.101]

    12 42 ms 42 ms 45 ms 75.125.xxx.xxx

    Trace complete.

    Tracing route to somesite.com [75.125.xxx.xxx]

    over a maximum of 30 hops:

    1 38 ms 3 ms 1 ms 74.8.111.xxx

    2 4 ms 5 ms 5 ms ag-accessre-multilink48.laxca01.paetec.net [74.8.108.121]

    3 5 ms 6 ms 5 ms gi-4-0-1-12.core02.lsajca01.paetec.net [66.251.30.178]

    4 22 ms 15 ms 10 ms gi-2-0-1.gw01.lsajca01.paetec.net [66.251.30.36]

    5 5 ms 5 ms 5 ms 12.118.130.69

    6 6 ms 6 ms 7 ms tbr1.la2ca.ip.att.net [12.123.199.106]

    7 5 ms 5 ms 5 ms 12.127.3.217

    8 21 ms 6 ms 5 ms 204.255.169.70

    9 336 ms 708 ms 2725 ms cr2-tengige0-7-5-0.dallas.savvis.net [204.70.196.29]

    10 45 ms 45 ms 45 ms 208.172.139.2

    11 42 ms 41 ms 42 ms gphou2-209-85-0-101.ev1servers.net [209.85.0.101]

    12 42 ms 42 ms 45 ms 75.125.xxx.xxx

    Trace complete.

    A reverse trace is somewhat irrelevant at this time... This issue has been reported several times and spans several tickets.

    Thanks,

    Nick

  15. #15

  16. #16
    Spoke with somebody at SAVVIS Tech support and they are investigating... My fingers crossed!

    Nick

  17. #17
    Sorry... double post...

    Nick
    Last edited by mediast; 04-11-2008 at 06:36 PM. Reason: double post

  18. #18
    Join Date
    Apr 2000
    Location
    California
    Posts
    3,051
    I've never personally considered EV1 to be Theplanet or of the same quality. I was going to say I'm in California and I've never seen this problem, but then I noticed the ev1.net fqdn in your traceroute, so it's obviously a different data center. If you need someone to perform a traceroute whom is also in California, let me know the IP in a PM and I'll give you the results.

  19. #19
    Thanks Tim. SAVVIS has indicated that what appears to be "high latency" from their router is entirely "cosmetic" (something to do with the priority of traceroute requests), and that they are trying to resolve this issue with Cisco... Not sure what to make of that...

    Nick

Posting Permissions

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