Hi,
TL;DR version:
There's some work being done on our provider's network on Saturday
30th June between the stated times. It shouldn't be noticeable.
Longer version:
On Saturday 30th June between 1100Z and 2100Z our colo provider will
be undertaking some upgrade work on its core network. This work is
not expected to have any impact on your BitFolk service.
Most of the work will be taking place in racks not directly relating
to BitFolk.
At some point during the maintenance window one of the switches to
which several BitFolk nodes are connected will be replaced with an
upgraded model. All BitFolk nodes are connected to two separate
switches and interface bonding should ensure that no interruption to
service is experienced.
These nodes are:
curacao
faustino
kahlua
obstler
president
urquell
I will be online while the work is being carried out just in case
anything does go wrong.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
Hi,
Between approximately 2105Z and 2120Z tonight there was a total loss
of IPv6 connectivity for customers on the following servers:
cosmo
dunkel
kahlua
obstler
urquell
This was because our transit provider did some (planned) maintenance
involving switching off a router, and the above servers were not
correctly set up to have a redundant IPv6 default gateway.
Connectivity was restored when alerts were received and a working
IPv6 default gateway was configured.
It appears that the incorrect settings were used when the above
servers were switched over to use interface bonding two weeks ago,
to provide layer 2 resilience.
Unaffected:
barbar
bellini
curacao
faustino
kwak
The correct redundant IPv6 gateway is now configured on all servers.
Please accept my apologies for this error, and the resulting
disruption it may have caused you.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
Hi,
As of aprox 1819Z there have been network problems at our
colo/transit provider, resulting in high packet loss. This is not
specific to Bitfolk; it affects all customers that I am aware of.
I've spoken to provider and they are working on it, is more info as I
have it.
Apologies for the disruption.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
Hi,
As you may be aware from:
http://seclists.org/oss-sec/2012/q2/500
there is a rather serious Intel CPU bug which can allow 64-bit
paravirtualized guests to crash and/or potentially gain control of
the entire node.
TL;DR version:
BitFolk is not affected. You don't need to do anything.
Longer version:
As luck would have it, BitFolk does not happen to support 64-bit
guests, so the vast majority of customer systems cannot make use of
this exploit.
There is no technical barrier to prevent customers installing their
own 64-bit OS, however, and two customers have done so. In the
very short term, with the exception of the two customers who are
already running 64-bit, I have prevented 64-bit guests from being
booted. I shall contact the two customers individually to arrange
for them to be moved to an upgraded node.
The alternative would be to upgrade and reboot every node. For some
nodes this would mean a full OS upgrade. This will be done
eventually but over a longer time span, as it will obviously be
necessary in order to support 64-bit guests.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting