Same here. No previous emails, the notice took us completely by surprise. This is very unwelcome news, since we no longer have proper time to inform our own paying B2B customers about the downtime.
It hadn’t occurred to me but it looks like if we deploy to and then re-route to other Meteor Cloud regions (which we’ve never used) we might be able to navigate around this.
Not exactly sure how that works with active users… guess they’re just have to refresh.
Thanks Meteor for the one day to get this up and going.
Hi, sorry by this but as I already explained to Ross in the ticket we announced this on December 1st in the official channel for notifications like that https://status.meteor.com/
But it’s ok, now that we know that we have some clients that are not subscribed to the status page (you should) we can wait to do this upgrade in our infrastructure.
Also, downtime is not something that we are used to having, as you know.
But in this case, we need to change some layers in our proxy and AWS can take a few minutes to catch up on new Security Groups and everything related.
The apps were not going to be down in fact.
But anyway, we are going to postpone this one and share more details later.
Please, subscribe to the status page, this was always the recommendation Status | Galaxy Docs
Definitely subscribed. How nice that a status page, which tend to send out seemingly thousands of notifications when fully subscribed, is the only channel of communication for knowing when the worldwide application platform, that supports your app and thousands of customers, will be down.
It sounds like Meteor Cloud didn’t want it etched into the ink of the Internet that their platform was going to have up to 30 minutes of downtime. Turns out that’s bad for new business huh?
But it’s okay to surprise existing customers by not sending an email, a forum post, or support them with a blog post with work-arounds, suggestions, etc. As that might scream “downtime” to the world.
I don’t want to do business with an organization like that. That puts appearances, new business interests, etc. out in front, at the cost of true paying clients. I don’t run my business like that.
Hi Ross, this downtime warning was an extra caution.
We did a lot of experimentation to avoid this downtime, and they were successful. But just in case AWS propagation of changes had a delay, our clients were prepared for a short downtime, probably less than 1 minute in a specific app. We were providing a cautious warning in advance as a possible short downtime.
Meteor was acquired two years ago, and we never had any planned downtime. And this is still the plan moving forward.
I’m pretty sure my freakout actually saved @filipenevola’s rear-end had apps actually went down, especially for up to thirty minutes.
The email above (many people’s only warning) says verbatim that it will be “downtime of 30 minutes”. There’s no language of “up to thirty minutes”, “but probably not”, “or maybe not at all”. It says thirty minutes, which about gave all of us a heart attack.
A potential downtime of thirty minutes should be a fricking telephone call to EVERY customer. Or wire up Twilio and send a SMS, something. Oh wait, they don’t have Twilio wired up - see current Galaxy 2FA
You can just setup another server and switch the dns to avoid any downtime btw guys. Been doing it for over a decade. Please don’t delete this post for community standards I am just sharing info. This is how it’s done at a professional level. Zero downtime.