18 Jul
2022
18 Jul
'22
11:53 a.m.
Hi all,
I was working on my VM about an hour ago, and suddenly lost all
connection to
my VM on macallan.bitfolk.com
the recovery machine .console.bitfolk.com
the bitfolk website.
All back now.
It was not local to here (Bangkok) because I could reach every other
site I tried.
I would like to know what happened?
I'm guessing something got to hot on this hot day in London, and let out
its magic smoke.
Regards
Ian
--
Ian Hobson
Tel (+66) 626 544 695
18 Jul
18 Jul
1:42 p.m.
Hi Ian,,
On Mon, Jul 18, 2022 at 06:53:00PM +0700, Ian Hobson via BitFolk Users wrote:
I was working on my VM about an hour ago, and suddenly
lost all connection
to
my VM on macallan.bitfolk.com
the recovery machine .console.bitfolk.com
the bitfolk website.
Okay, so you lost connectivity to the entirety of BitFolk, possibly
more.
Since BitFolk is in the same AS as Jump and shares network fate, you
probably lost connectivity to Jump as well. In future you can
confirm that by trying to reach the web site at
https://www.jump.net.uk/
If that was the case and we'd caught this at the time, then I'd be
asking Jump to look into that. But we didn't notice anything on our
end, and have no other reports, so it's not really worth me saying,
"someone on the Internet couldn't reach Jump's network but now they
can".
What IP address were you coming from? I can look at the routing now,
and see if there was any disturbance known around the time you
mention (~10:50 UTC?)
It was not local to here (Bangkok) because I could
reach every other site I
tried.
Didn't notice anything here either, so was likely something way in
between.
I would like to know what happened?
It's mostly impossible to tell without records of traceroutes or
similar at the time of the outage. Did you happen to do any?
"traceroute" is okay, but "mtr -Zn [host]" is often more
interesting.
I'm guessing something got to hot on this hot day
in London, and let out its
magic smoke.
Or indeed any device between London and Bangkok! In theory things
are supposed to reroute quickly but doesn't always happen, depending
on the nature of the failure.
All I can say is it wasn't something directly under BitFolk's or
Jump's control / knowledge.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
2:26 p.m.
Hi Andy,
Take a look at https://photos.app.goo.gl/C3J4VFvWg81iWKfr7
Some machines appear to be dropping things, like a new waitress in
too-high heals :)
On 18/07/2022 20:42, Andy Smith via BitFolk Users wrote:>
What IP address were you coming from? I can look at
the routing now,
and see if there was any disturbance known around the time you
mention (~10:50 UTC?)
124.120.29.87
"traceroute" is okay, but "mtr -Zn [host]" is often more
interesting.
I had another break a while later. Oh well. Things happen.
Cheers.
Ian
--
Ian Hobson
Tel (+66) 626 544 695
I'm guessing something got to hot on this hot
day in London, and let out its
magic smoke.
Or indeed any device between London and Bangkok! In theory things
are supposed to reroute quickly but doesn't always happen, depending
on the nature of the failure.
All I can say is it wasn't something directly under BitFolk's or
Jump's control / knowledge.
2:40 p.m.
Hello,
On Mon, Jul 18, 2022 at 09:26:24PM +0700, Ian Hobson via BitFolk Users wrote:
Take a look at
https://photos.app.goo.gl/C3J4VFvWg81iWKfr7
If you use -r (report) in conjunction with -c 50 (count of 50) then
you'll get output you can copy and paste as plain text. So:
$ mtr -znrc50 171.102.248.43
Start: 2022-07-18T14:32:51+0000
HOST: macallan Loss% Snt Last Avg Best Wrst StDev
1. AS8943 85.119.80.3 0.0% 50 1.2 2.0 1.1 9.2 1.8
2. AS??? 194.153.169.238 0.0% 50 0.4 0.7 0.3 13.5 1.8
3. AS??? 194.153.169.185 0.0% 50 0.6 2.5 0.4 23.8 4.9
4. AS2914 129.250.3.248 8.0% 50 2.7 2.6 0.5 15.0 3.4
5. AS2914 129.250.5.2 0.0% 50 5.9 6.9 5.5 13.7 1.9
6. AS2914 129.250.7.28 0.0% 50 24.9 25.9 24.8 29.3 1.0
7. AS2914 129.250.4.182 98.0% 50 188.6 188.6 188.6 188.6 0.0
8. AS2914 129.250.2.240 0.0% 50 183.3 180.3 178.7 206.8 4.5
9. AS2914 116.51.18.181 0.0% 50 168.1 167.3 167.1 168.2 0.2
10. AS38082 113.21.247.173 0.0% 50 194.1 194.2 193.9 194.6 0.1
11. AS38082 113.21.245.82 0.0% 50 194.9 195.0 194.9 195.5 0.1
12. AS7470 171.102.250.181 32.0% 50 193.6 193.6 193.2 195.9 0.5
13. AS7470 203.144.161.72 0.0% 50 192.8 192.9 192.7 193.2 0.1
14. AS7470 171.102.250.222 0.0% 50 195.2 195.1 194.9 196.2 0.2
15. AS7470 171.102.250.18 0.0% 50 193.8 193.9 193.5 200.7 1.0
16. AS7470 171.102.248.43 0.0% 50 201.6 195.4 193.1 220.6 4.8
(there'll be no output until the 50 iterations are done)
I took a guess at an IP close by you from your photo, but it would
be better if you could work out your own public IP by going to
whatismyip.com or something.
Some machines appear to be dropping things
Well, in your photo and in my output the packets do make it to the
end without loss, and that's the most important thing. It's common
for hops in the middle to reject or drop packets directly to them.
The output above and your photo look pretty normal for what it is.
There's some asymmetric routing going on as well (normal): for you
to Jump goes through True / Asianet and then Hurricane Electric, but
from Jump to you goes NTT and then True / Asianet. I can look into
if there were any problems within NTT and HE earlier.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
920
days inactive
920
days old
4 comments
3 participants
participants (3)
-
Andy Smith -
Ian Hobson -
William Anderson