New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
CVPS - Their solus / chicago location is down?
Is anyone else able to access CVPS' Solus Master? My VPS in Chicago with them is also down (other locations still up). No notification of upcoming downtime. Just put in a ticket.
Comments
Solus and VPS both up for me.
solus and vps both down for me as well
@ShardHost - Hmmm UptimeRobot is showing it's down too... and I still can't get to it.
@cosmicgate - thanks for confirming i'm not going mad.
Solus is down for me. (but responds to ping)
VPS is up for me.
Thanks - I just managed to log on to Solus however when I try and do anything with the VPS it just sits there spinning and spinning. Looks like they are having issues.
Now Solus is down for me.
well i hope the datas in therr are safe. i was suppose to back it up but was a little too late.
I'm sure its just a network issue. My VPS is up, panel is down.
VPS is up, panel is down.
Down VPS and panel.
Not sure if it's been utilized here, but give Just-Ping.com a try to see if it's a specific region that is experience the problem.
VPS up, panel is down.
odd.
Amsterdam2, Netherlands: Okay 101.9 102.0 102.2 205.234.159.138
Florida, U.S.A.: Okay 40.5 40.9 41.1 205.234.159.138
Amsterdam3, Netherlands: Okay 101.2 101.3 101.5 205.234.159.138
Sydney, Australia: Okay 225.3 226.5 230.1 205.234.159.138
New York, U.S.A.: Okay 21.8 22.1 22.6 205.234.159.138
Stockholm, Sweden: Okay 118.2 118.3 118.5 205.234.159.138
Santa Clara, U.S.A.: Okay 68.3 73.5 81.8 205.234.159.138
Vancouver, Canada: Okay 66.4 66.8 67.2 205.234.159.138
London, United Kingdom: Okay 87.7 88.2 88.7 205.234.159.138
Madrid, Spain: Okay 132.7 138.1 144.5 205.234.159.138
Padova, Italy: Okay 122.9 128.8 133.9 205.234.159.138
Singapore, Singapore: Okay 204.9 220.1 261.2 205.234.159.138
Austin, U.S.A.: Okay 36.4 38.9 41.2 205.234.159.138
Cologne, Germany: Okay 110.7 110.8 110.9 205.234.159.138
München, Germany: Okay 118.8 120.3 131.5 205.234.159.138
Amsterdam, Netherlands: Okay 101.2 101.3 101.7 205.234.159.138
Shanghai, China: Okay 239.3 250.5 257.1 205.234.159.138
Hong Kong, China: Okay 199.0 203.5 208.9 205.234.159.138
Melbourne, Australia: Okay 262.0 262.2 262.4 205.234.159.138
Copenhagen, Denmark: Okay 113.3 113.5 113.8 205.234.159.138
Lille, France: Okay 110.7 115.9 122.7 205.234.159.138
San Francisco, U.S.A.: Checkpoint temporarily not available - - - -
Zurich, Switzerland: Okay 121.2 121.4 121.5 205.234.159.138
Mumbai, India: Okay 258.3 261.4 267.7 205.234.159.138
Auckland, New Zealand: Okay 179.0 179.4 180.1 205.234.159.138
Groningen, Netherlands: Okay 107.7 108.4 109.7 205.234.159.138
Antwerp, Belgium: Okay 104.9 105.1 106.0 205.234.159.138
Dublin, Ireland: Okay 107.1 107.2 107.3 205.234.159.138
Kharkov, Ukraine: Okay 162.9 164.5 167.4 205.234.159.138
Manchester, United Kingdom: Okay 95.8 97.8 108.9 205.234.159.138
Vilnius, Lithuania: Okay 131.5 131.6 131.7 205.234.159.138
Bucharest, Romania: Okay 137.8 148.0 181.1 205.234.159.138
Bangkok, Thailand: Okay 283.7 285.7 288.1 205.234.159.138
Kuala Lumpur, Malaysia: Okay 257.6 257.8 258.2 205.234.159.138
Jakarta, Indonesia: Okay 274.8 275.0 275.4 205.234.159.138
Cape Town, South Africa: Okay 239.8 240.1 240.5 205.234.159.138
Glasgow, United Kingdom: Okay 91.3 91.4 91.5 205.234.159.138
Lisbon, Portugal: Okay 139.7 148.8 161.0 205.234.159.138
Chicago, U.S.A.: Okay 2.1 2.2 2.3 205.234.159.138
Dallas, U.S.A.: Okay 26.0 26.4 26.9 205.234.159.138
Istanbul, Turkey: Okay 145.6 146.1 146.9 205.234.159.138
Gdansk, Poland: Okay 133.8 134.0 134.2 205.234.159.138
Cairo, Egypt: Okay 152.9 156.1 161.3 205.234.159.138
Buenos Aires, Argentina: Packets lost (10%) 779.7 1,043.0 1,262.6 205.234.159.138
Belgrade, Serbia: Okay 127.0 127.1 127.2 205.234.159.138
Toronto, Canada: Okay 14.8 15.0 15.1 205.234.159.138
Frankfurt, Germany: Okay 110.8 111.0 111.3 205.234.159.138
Sofia, Bulgaria: Okay 130.8 131.1 131.9 205.234.159.138
Budapest, Hungary: Okay 122.0 122.7 123.7 205.234.159.138
Sao Paulo, Brazil: Okay 167.3 167.4 167.7 205.234.159.138
Paris, France: Okay 127.4 128.0 128.4 205.234.159.138
Mumbai, India: Okay 274.3 275.0 278.1 205.234.159.138
New Delhi, India: Okay 277.6 284.2 292.6 205.234.159.138
Chicago, U.S.A.: Okay 1.1 1.4 1.5 205.234.159.138
Bangalore, India: Okay 264.5 275.4 280.5 205.234.159.138
Montreal, Canada: Okay 26.4 27.8 33.7 205.234.159.138
Tokyo, Japan: Okay 177.5 186.2 190.7 205.234.159.138
Milan, Italy: Okay 126.3 127.0 127.5 205.234.159.138
Hangzhou, China: Okay 252.0 256.8 262.0 205.234.159.138
SolusVM has a 'feature' if someone tries to interact with a VPS on a down node it can cause the web UI to become unresponsive for all other requests for about 10 minutes at a time.
SolusVM: Down
VPS: Up
No report from uptimerobot at all.
As I can access this every now and then I think the above is happening. Also when it pulls via the API within WHMCS it creates the same lock up.
I think maybe one or two nodes are down and this is the issue.
I had the same problem when one of mine went down. I don't know what is up with the robot. It works with some of mine but just that one it did not do anything.
So far all my downtimes are reported properly, well if they exceed the 5 minutes..
For current CVPS case I guess no report because the VPS is actually running fine, just the SolusVM that is down (I'm not tracking SolusVM ofc).
Yay - Solus came back up properly and now I booted the VPS again and I'm back online, so it looks like (finally) someone is working on it.
SolusVM is up now
Laff... anyway
This appears to have been resolved. There was nothing we could do and was isolated to a few machines not ALL of Chicago. We notified upstream when it happened but was not able to get resolved until this morning.
Regards
Thanks, although you could have notified customers.
@Shardhost
We were kind of caught off guard because we didnt get any down notification. Pingdom apparently has been down as well. I guess this happened at the worst timing!
Yes, thats an unfortunate coincidence and understandable if you use Pingdom for monitoring.
10:20 < ChicagoVPS> its been down all night lol 10:20 < ChicagoVPS> and morning 10:20 < ChicagoVPS> I didnt even realize I had nodes down because of it! 10:20 < ChicagoVPS> so I agree, pingdom needs to fix their shit 10:21 < FreeSpencer> You dont have a backup notification system :o 10:21 < ChicagoVPS> I did 10:21 < ChicagoVPS> until Jeremiah left and I dont get those notifications lol 10:21 < ChicagoVPS> I fixed that already but still 10:21 <@Zigara> you didn't notice a node is down all night and morning? 10:22 < ChicagoVPS> nope 10:22 <@Zigara> pro 10:22 < ChicagoVPS> until a ticket came in 10:22 < ChicagoVPS> your pro 10:22 <@Zigara> you're a great systems administrator 10:22 <@Zigara> +1 10:22 < ChicagoVPS> im not s SA so whats the point? 10:22 < ChicagoVPS> idiot 10:22 <@Zigara> I'm not the idiot that leaves his node down all night and day 10:23 <@Zigara> because I don't rely on some shit service such as pingdom 10:23 < ChicagoVPS> lol 10:23 < ChicagoVPS> your so dumb 10:23 <@Zigara> lol you're an idiot if you're calling ME dumb because YOU fucked up 10:23 <@__william__> nagios... 10:23 <@Zigara> ^ 10:23 < ChicagoVPS> I didnt know it was down yes, the reason it was down, not my problem 10:23 <@__william__> or if modern 10:23 <@Zigara> not your problem? 10:23 <@__william__> "icinga" 10:23 < ChicagoVPS> Even if I knew it was down, I couldnt fix it 10:23 < ChicagoVPS> Yes upstream problem 10:24 <@Zigara> you're in the wrong dude 10:24 <@Zigara> just accept it 10:24 < ChicagoVPS> how am I in the wrong 10:24 < ChicagoVPS> I just stated, even if I KNEW it was down 10:24 < ChicagoVPS> I COULDNT FIX 10:24 <@Zigara> 'not my problem' lol 10:24 < ChicagoVPS> It wasnt my problem 10:24 < ChicagoVPS> it was upstream 10:24 <@Zigara> it becomes your problem 10:25 <@Zigara> you could let your clients know it's not your fault, you know, some PR 10:25 <@Zigara> all night and morning seems like a lot of downtime
Also, to Liam's "Apparently that conversation is spoofed according to chris..." - that is complete bullshit. You can ask anyone on the LEB IRC channel. I'm also a channel operator on IRC, I have no reason to spoof logs. Chris is just trying to cover his fuckup.
sigh
@Liam - can you close this thread please before it follows the standard @CVPS_Chris bashing
we pretentious now
So that's not true then?
I can confirm that the conversation is definitely not spoofed, 200 other people have logs proving the same too.
That said, the drama has already died down, so meh.
Thanks! Well, another provider on my 'Do-not-make-contract-with'-list.