So last Tuesday my Hostinger VPS just... vanished. Panel green, bills paid, but traceroute died in Kansas City. Support ticket got "we see no issues." I was ready to flame them.
Turns out it wasn't Hostinger at all. Some AS upstream had leaked a /24 that swallowed my IP block. Four hours of my life, not their fault. I feel you if you've cursed support for routing issues they can't see. Have you checked bgp.he.net when your "host" goes down? Might save you the embarrassment I had.
So this is how to check if its actually the host or the routing? I try traceroute but not work? Just times out everywhere? Is bgp.he.net free to use or you need some account?
Member
Right then, full disclosure: we've had customers absolutely torch us in reviews for "our" outages that were actually Level3 having a moment. Proper frustrating. Can't exactly tell a client "cheers lads, it's someone else's fault" and expect a hug. We now have a status page that separates our kit from upstream drama. 🦡
Member
Optimization here is knowing whose electricity costs you're actually paying for. Four hours of "downtime" that was just routing interception... my workload kept running, just couldn't phone home. Profitability calculation gets interesting when you measure hash submission windows versus actual uptime. Had me checking my own bgp feeds after that — https://bgp.tools
Status page separating kit from upstream is the real MVP move
