New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
LowEndBox & LowEndTalk.
Comments
today
classic story: it slowly becomes worse and worse and will probably be unusable in a few months. the server will expire soon so unfortunately i won't be able to post updates!
Ralph should stick to selling books. He's always been rude and his services are thrash.
What are you using to monitor your servers? (in particular the first and last screenshots)
I'd like to do the same.
Uptime kuma is first one, ping.pe is the second
It appears HostSlim's entire 69.174.98.0/23 range is unreachable at the moment.
Probing 69.174.98.1 shows it belongs to RIPE NCC, AS3257 (GTT-BACKBONE), GTT – Estonia, Harjumaa, Tallinn [hosting]. ( hmm, I have seen this shit before, literally like 24 hours ago )
The prefix 69.174.98.0/23 is clearly part of a larger aggregate, 69.174.0.0/17.
Unless HostSlim has actually withdrawn the entire /23 — which I highly doubt — this smells like pure GTT fuckery.
We’ve just gone through the exact same bullshit recently: a /24 we rented out suddenly started being announced again as part of the larger /19 it belonged to. After warning the broker for over two months that the subnet was being split incorrectly, I eventually dropped the entire subnet and told them to shove it up their ass.
Their reply? “Yes, but the more specific announcement takes precedence.”
Like I don’t know how BGP works.
I may not know everything about BGP, but this is basic stuff: if you carve a larger block into smaller prefixes, you do it properly. You withdraw the aggregate and announce only the /24 ( the active subnet depending on the split ). You don’t leave the larger prefix active and hope the Internet magically behaves.
Announce the /24 and be done with it. Anything else is sloppy at best and operationally broken at worst.
The subnet in question of HostSlim looks like the shit we had:
I personally doubt this is on them ( HostSlim ), I would say it is on the holder of the larger prefix ( this case GTT )
EDIT:
I’ve been seeing this more and more often lately. It genuinely feels like people are getting dumber at the NOC level.
I understand aggregation. This is not an aggregation problem.
We’re talking about larger prefixes being actively rented out as smaller blocks, while the parent aggregate is still being announced. That’s not a design choice, and it’s not a policy debate — it’s a lack of basic operational skill.
If you lease out a /24 from a /19 or /17, you either withdraw the aggregate or you very clearly control how it’s announced. Leaving the larger prefix active and relying on “longest prefix wins” is lazy, error-prone, and eventually causes exactly these conflicts.
This isn’t BGP being complex. This is people at the NOC not understanding — or not caring about — the consequences of what they announce.
The Internet still works because of math — not because of people doing their jobs well.