23 Nov
2015
23 Nov
'15
10:42 p.m.
I noticed something strange happening with routing at that sort of time
(1945 GMT Monday). I couldn't reach my Bitfolk VPS, nor a machine owned
by a different Jump Networks customer, over IPv4 - though I could reach
my VPS over IPv6. For me, connecting from my home broadband in New
Zealand, IPv4 traceroutes were looping within level3.net.
As luck would have it I know one of the gurus at Jump socially and it
turned out he was already onto the issue - he had seen trouble within
level3 and was tweaking routing for the entire Jump network (which
includes Bitfolk). This resolved my issue at 1959 GMT, though I know he
was still watching the situation 20 minutes later. He commented that it
looked like level3 rebooted their core network around 2010.
Ross
On 24/11/15 11:21, Samuel Bächler wrote:
Dear All
I logged into my vps around 21:00 CET today using ssh. When I typed the
command *ls* it took quite a while (5 to 20 seconds - these things are
hard to tell when one does not measure it with a clock).
I also tried to request a page from my web server which did not work. I
do apologize for not knowing the exact error anymore.
Finally, *git pull origin master* against the repository on my vps got a
time out.
When I tried all the above mentioned things again a few minutes later
things were back to normal.
Now, what could that have been?
Regards,
Sam
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users