Results 1 to 10 of 10

Thread: Network Maintenance June 22, 2010

  1. #1
    Join Date
    Mar 2010
    Posts
    234

    Default Network Maintenance June 22, 2010

    We will be performing network maintenance tonight starting at 1 AM Eastern to bring over the last 2 netblocks from the Seattle datacenter. Impact from the network maintenance should be minimal at best and may involve outage of a few minutes for customers on the network blocks being moved.

    66.249.0.0/19
    209.40.192.0/20

    This work will reduce ping times and latency for VPS accounts on the effected net blocks.

  2. #2
    Join Date
    Aug 2009
    Posts
    3

    Default

    Anyone else experiencing IP resolution issues? One of my vps has a 67.223* which works fine (touch wood), but 209.40.195*'s don't - on, off, on, off, on...

    Is this still related to ongoing or incomplete moves from Seattle or nY?

  3. #3
    Join Date
    Jul 2009
    Location
    New York
    Posts
    465

    Default

    Quote Originally Posted by chrisurban View Post
    Anyone else experiencing IP resolution issues? One of my vps has a 67.223* which works fine (touch wood), but 209.40.195*'s don't - on, off, on, off, on...

    Is this still related to ongoing or incomplete moves from Seattle or nY?
    Have you opened a ticket or called the 800 number? Did you do traceroute/tracert and ping? POSTING IN THE FORUMS DOES NOT HELP OR SOLVE YOUR PROBLEMS.
    Happily on a Link3. Feel free to request a refferal code that takes a 10% lifetime discount off your hosting.
    Please open a SUPPORT TICKET AND CALL vpslink to resolve your vpslink problems FIRST
    I am a CUSTOMER Only. Any vpslink issues should be directed to Matt@VPSLink and/or Michael@VPSLink

  4. #4
    Join Date
    Jun 2010
    Posts
    5

    Default 209.40.202.* is also on, off, on, off, on ...

    You are not alone.

    See the thread:

    VPSlink Forums > General > System and Network Status > Wednesday, June 16, 2010 Network Maintenance Wednesday, June 16, 2010 Network Maintenance

  5. #5
    Join Date
    Aug 2009
    Posts
    3

    Default

    Cwewmpz, I did open a ticket, actually two - for two different accounts - that were having this issue at nearly the same time.

    I'm sorry I wasn't more clear in my post, as I assumed that such tasks were obvious to be performed: I did perform a traceroute, from two different locations, to validate the issue was not mine. In fact, what's interesting is that the primary IP is functioning fine; the secondaries are failing at cogentco, similar to other posts I saw.

    Let me be clear: I do not expect my issues to be resolved as a result of my posting. I am simply interested in knowing if other users are having similar issues, so as to gauge how how isolated or severe my issue might be. Let's be frank - who else is reading these forums other than other customers looking for answers or explanations that we are not receiving in a timely manner?

    My clients expect immediate responses to requests made of me and my company; I see no reason why this should not apply vendors I choose to use. As a customer therefore, I expect prompt responses, even acknowledgments, to the few tickets I ever open. When I don't receive any explanations for outages or problems, I get concerned.

  6. #6
    Join Date
    Jul 2009
    Location
    New York
    Posts
    465

    Default

    You have a right to receive a vpslink response but it would not be forthcoming in the forums. I only reiterate the support ticket and calling because it seems there are plenty of new registrations that post topics which would not be helpful to their situations. Please call if you can as well because tickets about downtime as a response would be much slower than you may like.
    Happily on a Link3. Feel free to request a refferal code that takes a 10% lifetime discount off your hosting.
    Please open a SUPPORT TICKET AND CALL vpslink to resolve your vpslink problems FIRST
    I am a CUSTOMER Only. Any vpslink issues should be directed to Matt@VPSLink and/or Michael@VPSLink

  7. #7
    Join Date
    May 2006
    Location
    GMT +10
    Posts
    375

    Default

    Gack. I was migrated a long time ago but troubles remain.

    Access to all of my VPSLink IP addresses is now dead. They die with a traceroute that looks like this:
    Code:
    traceroute to 64.79.19*.*** (64.79.19*.***), 25 hops max, 40 byte packets
    1 ip-10-218-90-2.ec2.internal (10.218.90.2) 0.518 ms 0.469 ms 1.301 ms
    2 216.182.224.229 (216.182.224.229) 1.288 ms 216.182.224.225 (216.182.224.225) 0.401 ms 216.182.224.229 (216.182.224.229) 1.252 ms
    3 216.182.232.70 (216.182.232.70) 0.373 ms 216.182.232.72 (216.182.232.72) 0.358 ms 216.182.232.70 (216.182.232.70) 0.362 ms
    4 216.182.232.54 (216.182.232.54) 1.176 ms 216.182.232.52 (216.182.232.52) 1.154 ms 216.182.232.54 (216.182.232.54) 1.145 ms
    5 72.21.222.154 (72.21.222.154) 1.677 ms 1.660 ms 72.21.222.65 (72.21.222.65) 2.073 ms
    6 72.21.197.39 (72.21.197.39) 1.621 ms 1.533 ms 72.21.222.154 (72.21.222.154) 1.490 ms
    7 72.21.197.39 (72.21.197.39) 1.598 ms ge-4-1-0.mpr1.iad10.us.mfnx.net (206.223.115.86) 2.642 ms 72.21.197.39 (72.21.197.39) 1.623 ms
    8 ge-3-0-0.mpr1.dca2.above.net (64.125.26.237) 3.302 ms ge-4-1-0.mpr1.iad10.us.mfnx.net (206.223.115.86) 2.568 ms ge-3-0-0.mpr1.dca2.above.net (64.125.26.237) 3.064 ms
    9 xe-1-1-0.cr1.dca2.us.above.net (64.125.26.173) 3.221 ms ge-3-0-0.mpr1.dca2.above.net (64.125.26.237) 3.191 ms xe-1-1-0.cr1.dca2.us.above.net (64.125.26.173) 3.357 ms
    10 xe-1-0-0.cr2.dca2.us.above.net (64.125.28.250) 3.001 ms xe-1-1-0.cr1.dca2.us.above.net (64.125.26.173) 3.176 ms 3.068 ms
    11 xe-1-0-0.cr2.dca2.us.above.net (64.125.28.250) 3.274 ms ge-1-3-0.mpr2.dca2.us.above.net (64.125.29.26) 41.561 ms 41.334 ms
    12 ge-1-3-0.mpr2.dca2.us.above.net (64.125.29.26) 40.177 ms xe-1-1-0.mpr4.bos2.us.above.net (64.125.25.69) 12.346 ms ge-1-3-0.mpr2.dca2.us.above.net (64.125.29.26) 39.958 ms
    13 xe-1-0-0.mpr3.bos2.us.above.net (64.125.25.65) 12.102 ms 12.065 ms xe-1-1-0.mpr4.bos2.us.above.net (64.125.25.69) 12.430 ms
    14 64.124.50.5.available.above.net (64.124.50.5) 13.321 ms 13.358 ms xe-1-0-0.mpr3.bos2.us.above.net (64.125.25.65) 12.264 ms
    15 64.124.50.5.available.above.net (64.124.50.5) 13.569 ms 13.291 ms *
    16 * * *
    17 * * *
    18 * * *
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    Before it was just one of the IP's that was dead. Now it's two of them.

    And my SSH session to VPSLink was disconnected mid-session while typing this too. WTF?

    Trouble ticket on the way.

  8. #8
    Join Date
    Jul 2009
    Location
    New York
    Posts
    465

    Default

    lol. strange to see that ip range. I block that whole subnet
    Happily on a Link3. Feel free to request a refferal code that takes a 10% lifetime discount off your hosting.
    Please open a SUPPORT TICKET AND CALL vpslink to resolve your vpslink problems FIRST
    I am a CUSTOMER Only. Any vpslink issues should be directed to Matt@VPSLink and/or Michael@VPSLink

  9. #9
    Join Date
    May 2006
    Location
    GMT +10
    Posts
    375

    Default

    64.79.192.0/19 is/was always a Spry Hosting netblock.

    I'd block it too if I wasn't in it.

    Now 64.79.192.0/19 is part of the much larger AS29873 - The Endurance International Group, Inc, which comprises about 50 netblocks.

  10. #10
    Join Date
    May 2006
    Location
    GMT +10
    Posts
    375

    Default

    Just in case anyone else is having similar issues - ie external access to IP addresses on your migrated VPS failing randomly - according to the response to my support request, the networking issues I am having are associated with an 'open issue'. What that means was not specified.

    Apparently resolving the issue may involve un-announced reboots of your VPS too...

Bookmarks

Posting Permissions

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