Hello,
On Thu, Nov 21, 2019 at 11:22:14PM +0000, Dom Latter wrote:
Did I notice?
No.
:)
I know you're not looking for an explanation but in terms of who was
affected and to what degree, it really will vary quite a lot here.
BitFolk's servers are split between two different racks at the colo
provider, with a pair of switches in each rack. One of those pairs
of switches also hosts the target of this attack, so that pair was
affected a bit worse. That covers servers:
hen
hobgoblin
leffe
macallan
paradox
In addition, some of the colo provider's private peering comes in
there, so that was affected quite badly. That covers my home for
example, since peering with Andrews&Arnold is there. So for me from
my home it looked like everything was down.
Some of their transit was affected, to a degree I do not know yet,
but LINX peering was probably unaffected.
So customers on servers on the other pair of switches, which are:
elephant
limoncello
snaps
talisker
…may not have seen any issue at all, depending on the route their
legit traffic was taking.
On top of that, our internal monitoring node is on a server on the
target switch pair, so from its point of view everything was also
flapping up and down. So even if you did get alerts from us, they
were not necessarily reflective of full reality.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting