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.
Comments
Yesterday in their email they said the maximum downtime could be 30 minutes, it ended up being 2 hours, which I find still not unreasonable.
The current outage was unexpected though.
Why is my VPS unable to connect
Down for me still. So is their website.
Hello, we apologize for the downtime. It's being worked on at the datacenter. The upgrade had to finish yesterday as stated in the email, however another issue has arisen which will be resolved any moment.
An update will be posted later.
"Hope it gets resolved soon, I'm waiting."
@Bullethost A suggestion: host your corporate website outside of your own infrastructure, so that you can at least keep your customers updated during this kind of outages.
Still down for me. At least this is teaching me the importance of redundancy for my self-hosted services.
....aaaaand back online, after half a day downtime, not good.
Well, not completely. Missing 30% all of connectivity on IPv6
Well, I don't agree with that. The announcement was made at just after 3pm, while the maintenance would start at 21:00. The maintenance started a bit earlier at least, because the downtime started a couple of minutes before 9. And then it lasted just over 2 hours, while there was communication that most likely there wouldn't be downtime, but "worst scenario" 15 to 30 minutes.
If you say "worst scenario", obviously "an even worse than worst" scenario wasn't considered. In my networking time (grandpa tells a story again) we always had a "worst scenario" in which we would have a return-to-original when we wouldn't meet that worst given downtime. Now it took 4 times as long. In my opion, that's unreasonable, especially when no downtime was foreseen.
When there was communicated that downtime could be for say 1 or 2 hours, then I've taken measures. With 15 to 30 minutes of possible downtime, that was too much effort. This was a clear "oopsie" in foreseeing the impact IMHO.
Looking at what has been done, it could be that it's not unreasonable, however, regarding the communicated (possible) downtime, 2 hours is unreasonable, again IMHO.
To say the least...
They're likely use the network of HostSlick
My hostslick server is still offline though
Let's hope this upgrade leads to many months of uptime
Yes I know. But still. Hostslick announce maintenance quite some time before. And I'm customer of Bullethost, so expect things from them to communicate.
All in all in my opinion this maintenance these days is not good - communicationwise. Telling people that they'd normally won't have any downtime, and they are confronted with substational downtime isn't what you want.
I completely understand your expectations.
I was just giving information for everyone and I wasn't trying to deny what you said.
OK - misunderstood your comment then - no prob.
Update: I understand both sides and I agree, however the issues which have arisen during the maintenance weren't expected to happen at all since everything was preconfigured and I communicated the my network provider trough the whole process. The issue was in the upstreams after the initial downtime and not actually the network provider.
Skylink couldn't see the links of my network provider at first which caused confusion but it was resolved when the second downtime happened, it happened due to them using Arista and us - Juniper. There was signal both ways but still not coming trough.
Currently what's left is the ipv6 configuration which will be done tomorrow.
I will send emails once everything is done and will explain in detail.
Well, your website was down (at least on Thursday), I haven't seen much communication from your side to us, customers, about again downtime, or during the downtime what was happening. So that could definitely be improved.
That something wasn't expected is something that can always happen, however, there is a big difference between "no downtime, maybe 15 to 30 minutes" and 2 + 20.5 hours for IPv6.
I've always learned if you communicate worst case, it has to be worst case. And yes, a bit can be added to it without issues. However, there's quite a difference between 30 minutes and 23 hours (and counting).
And yes, I know IPv4 is working now. But if you didn't have IPv6, I wouldn't have acquired a VPS from you; for me IPv6 is an important part, so for me the VPS is practically unusable i.e. down without IPv6.
Some people may think I'm hammering or something like that, but it's not in my eyes. It's pointing out where improvements can be made. It's impossible to look back at this weekend and say "well, it went well, except for one small tiny issue".
You are not hammering or something, communication must be improved here.
I'm getting the impression that the last message was deliberately posted at 2 minutes past midnight, so "tomorrow" can still be Sunday...
1 day and 9+ hours no IPv6 connectivity now...
An update has been posted. Everything went smoothly and the network is fully running via the new MX960, however the IPv6 connectivity still has issues and we are working with our network provider on a solution.
So basically, it didn't went smoothly. If the announcement was made "no downtime, maybe 15 to 30 minutes" and we're approaching 3 days of no IPv6 connectivity... don't say things went smoothly.
IPv6 connectivity to my VPS just returned. Finally. After days I can start using the VPS again.
The ipv6 connectivity has been fixed, however we will still keep monitoring mtu to ensure there will be no more hiccups.
Again, we apologize for the inconvenience caused to all customers.
aaaand network is down once again aaaand is back after around 10 mins....very uncomfortable to use this server, tbh
I also lost connection to my server briefly this evening. 0 comms from BulletHost about it yet.
Our network provider had to perform a restart late at night in a emergency since there was a ARP resolving issue. The issue was present in larger VLAN due to the volume of the ARP traffic.
Dedicated server customers were not affected only some VPS nodes briefly. However we are still working with them and monitoring the traffic to ensure this will be fixed permanently.
Hmm, network is super slow, are there any issues? nah, network is good, was an issue at my end, fixed now.
1376, please double my bandwidth. Thank you
VPS down for half an hour now. Website of Bullethost also unreachable, most likely because they're still on the same location. Was pointed out several times that that is a bad idea in case of issues.
Same here!
There is a massive power outage in the datacenter and the whole region in general. Other providers are affected as well.