Managed Down?

Andrej · #1 02-05-2004, 08:27 PM

I cannot ping, SSH, connect in any way to my server. I've asked other people to ping and try to connect but nothing. Is there something up with the MGS network or power failure or something? Please let me know!

Thanks

rcthost · #2 02-05-2004, 08:28 PM

Same for me. I have at least 3 out of 5 servers down right now.

EDIT: Make that 4 out of 5.

Andrej · #3 02-05-2004, 08:29 PM

I just sent in two tickets.
Thing is, it's so sudden. Like they yanked the connectio from it.

simonhouse · #4 02-05-2004, 08:33 PM

I noticed some routing issues earlier (going via layer42 instead of Abovenet), but they resolved that within the hour. My box is reachable as usual right now, no latency or packet loss.

Maybe they are performing maintenance one switch at a time or something .....

Andrej · #5 02-05-2004, 08:37 PM

There should've been a warning about maintenance.

LoL! They're moving us to Florida

jasonl813 · #6 02-05-2004, 08:40 PM

Managed.com's response:

K.K. has responded to your help desk request.

-----------------------------------------------
(K.K.)
-----------------------------------------------
Hello!

We are installing some more ports in order to expand our bandwidth. Due to this, some servers may be expiriencing some delay. We apolgize for this matter. If you are still expiriencing delay in an hour, please send a request to support@managed.com

Best Regards,
Mananged.com

ckh · #7 02-05-2004, 08:46 PM

02/05/04 17:42:28 Fast traceroute 66.79.172.129
Trace 66.79.172.129 ...
1 10.33.0.1 16ms 0ms 0ms TTL: 0 (No rDNS)
2 68.2.1.141 15ms 0ms 0ms TTL: 0 (ip68-2-1-141.ph.ph.cox.net ok)
3 68.2.14.33 0ms 0ms 0ms TTL: 0 (chnddsrc02-gew0602.rd.ph.cox.net ok)
4 68.1.0.160 0ms 0ms 0ms TTL: 0 (chndbbrc01-pos0203.rd.ph.cox.net ok)
5 68.1.0.88 16ms 15ms 15ms TTL: 0 (lvxxbbrc01-pos0103.rd.lv.cox.net ok)
6 68.1.0.95 32ms 63ms 31ms TTL: 0 (paltbbrj01-pos010000.r2.pt.cox.net ok)
7 68.105.31.18 47ms 46ms 32ms TTL: 0 (No rDNS)
8 208.184.233.141 47ms 31ms 31ms TTL: 0 (so-6-1-0.mpr3.sjc2.us.above.net ok)
9 64.125.30.90 32ms 32ms 31ms TTL: 0 (so-2-0-0.er10a.sjc2.us.above.net probable bogus rDNS: No DNS)
10 209.66.79.101 47ms 31ms 31ms TTL: 0 (above.sjc.assertivenetworks.net probable bogus rDNS: No DNS)
11 66.154.102.5 * * 2156ms TTL: 0 (assertive.managed.com probable bogus rDNS: No DNS)
12 No Response * * *
13 No Response * * *
14 No Response * * *
15 No Response * * *
16 No Response * * *
17 No Response * * *
18 66.154.102.5 3344ms * * TTL: 0 (assertive.managed.com probable bogus rDNS: No DNS)
19 No Response * * *
20 No Response * * *
21 66.154.102.5 * * 1062ms TTL: 0 (assertive.managed.com probable bogus rDNS: No DNS)
22 No Response * * *
23 No Response * * *
24 No Response * * *
25 No Response * * *
26 No Response * * *
27 No Response * * *
28 66.154.102.5 2250ms * * TTL: 0 (assertive.managed.com probable bogus rDNS: No DNS)
29 No Response * * *

ckh · #8 02-05-2004, 08:47 PM

Why don't they do this when it would effect us the least, like at 1 -3 AM?

tommyd · #9 02-05-2004, 08:47 PM

It is due to them adding another backbone.

simonhouse · #10 02-05-2004, 08:49 PM

I spoke too soon - my box is once again unreachable and/or losing lots of packets.

Great afternoon this is turning out to be. I wish they would give us some advanced notice if they are planning to perform downtime-inducing maintenance.

Andrej · #11 02-05-2004, 08:49 PM

Tracing route to technics.priorahost.com [66.79.184.210]
over a maximum of 30 hops:

1 26 ms 23 ms 24 ms mcr4.mtun.phub.net.cable.rogers.com [24.101.128.
1]
2 46 ms 47 ms 47 ms 66.185.92.129
3 * * * Request timed out.
4 26 ms 23 ms 23 ms gw01.ajax.phub.net.cable.rogers.com [66.185.81.1
70]
5 23 ms 23 ms 24 ms gw02.bloor.phub.net.cable.rogers.com [66.185.80.
134]
6 34 ms 35 ms 36 ms gw02.chi.phub.net.cable.rogers.com [66.185.81.1]

7 35 ms 36 ms 40 ms ge3-1.cr01.chc01.pccwbtn.net [63.218.5.5]
8 101 ms 108 ms 100 ms pos3-0.cr02.sjo01.pccwbtn.net [63.218.6.66]
9 106 ms 101 ms 101 ms 63.218.7.6
10 107 ms 100 ms 101 ms f3-0.core1.eqx.layer42.net [69.36.239.42]
11 107 ms 108 ms 105 ms f2-0-1.core1.sjc.layer42.net [69.36.239.61]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
(Continues like that)

Seems like it's something with the Layer42 route.

yaax · #12 02-05-2004, 08:49 PM

I also get response from managed.com reseller:

You may notice a degrad in speed on all servers, including dedicated servers. This is due to the Datacenter make arrangments for installing a second backbone. The slow down shouldn't be for to long. Once everythis is completed, the speeds overall will increase by far as they are doubling the network capcity. In the next 90 days or so a 3rd Backbone will be added we are told.