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.
RELIABLESITE ANNOUNCE OUR /24 RANGE WITHOUT OUR AUTHORIZATION
Today I tried to contact @ReliableSiteHosting @MrRadic and told them they basically announced our range without authorization, and we haven't received a proper response.
We sent a ticket, emailed it, and chatted via LET, and they just said they didn't do anything.
We never made any agreement, nor did we register in their system.
Today, our /24 range had been announced by your AS NUMBER.
We kindly ask that you remove it because it's harming us. Maybe you can respond here.
I'm attaching some evidence:
Thanked by 1dsbnoob
This discussion has been closed.
Comments
Why is this posted in news category?
If it is published in the wrong zone, some administrator should move it to the zone that is
Sorry!
@nohavps you're aware you could just set RPKI and that'd drop this announcement, right?
The problem is that they should do that, we never authorized this.
I’m uneducated on this topic, but can someone please explain in somewhat simple terms how it can seriously harm a company if someone else announces their /24 range?
Does it affect customers servers, or is there a risk of the company’s IPs getting blacklisted or something? I’m genuinely curious.
Is this ticket an hour old?
It was communicated this morning, just yesterday we migrated a node that had that range and it is harming us because it is not propagating correctly as it should be.
We don't offer support over LET, a network engineer will investigate this further. If it's a leased IP, it could have been an announcement that wasn't requested to be removed. This is just speculation, I don't have any concrete information for you, you'll hear back over the ticket.
If someone else announces a prefix that is already used by nohavps elsewhere, it can cause traffic to be routed to the wrong destination, some of it might end up in the reliablesite network instead of reaching nohavps.
As a result, nohavps servers can become unreachable because packets are being sent to the wrong destination.
Since the RIKI is invalid I assume that this only happens form very few locations, but it's still an issue.
... why would they set RPKI for you? That's not how it works.
This announcement was made yesterday without any authorization
@Berohost can confirm that we are migrating some nodes with that range and this announcement appeared yesterday. I kindly contacted them today indicating that they would delete this before publishing and they just ignored our messages.
You can check it out
https://bgp.he.net/net/64.253.91.0/24
Credits to @oloke
I see, thank you for the explanation. That could seem really damaging, hopefully Reliablesite fixes it soon.
What im also getting from this thread is basically any company can announce a prefix even if they don’t own it? And is it even possible for an individual to do this? Because if it is, i’d imagine a lot of trolls doing it to wreak havoc.
Also is it even legal to announce a prefix you don’t own, considering the amount of damage it can do. I’d imagine it’s incredibly illegal, no?
@nohavps But DP is right here.
At the moment the prefix is not announced by anyone.
What you are seeing right now are just some stuck routes, which unfortunately happens every now and then.
I would not say this is a reliablesite issue.
It looks like it's stuck with AS4230 which is just a peer of reliablesite.
I think @jh_aurologic should give @nohavps some tips on how to sue the living shit out of ReliableSite
https://bgp.he.net/net/64.253.91.0/24
This is what we are reviewing, ask by ticket, message from reliablesite and we do not have an answer about this problem, that is why we publish here, maybe they can answer what it is due to.
If RPKI is properly set. This won't effect you.
Now instead of sending a notification here on LET.
Should always lookup who the NOC is via ARIN or WHOIS and send an email to the NOC.
Very clear and simple explanation, thank you for this 😂
Did you look at the images in the post?
I contacted both users via message, ticket, and chat, and we haven't received any response.
Please use bgp.tools instead, as the dataset is more up to date.
At the moment the prefix is not in use by anyone at all.
It shows AS23470 as a upstream, because a route is stuck with AS4230.
I would say that this has near 0 real world impact, if you would use the prefix somewhere else right now.
bgp.he.net website isn't updated quickly at all.
Also as mentioned its not being announced by anyone.
And it won't get announced without a valid RPKI/ROA
I think it's about time we had a "Legal" category on the forum, what say you fellow kids?
Until yesterday, we had the range announced with Active Server. Yesterday, we switched to our AS63025, which was supposed to be advertised with Berohost. The strangest thing is that Reliablesite seemed to be there. That's why I'm posting to find out why they're showing up without us authorizing anything. The problem is that the range isn't being propagated to the new location.
Sadly, you'll likely have to wait several hours for a real human or someone with actual access to look into this on a Reliablesite ticket. And if they think they have something to do about it.
Its not going to propagate without a valid RPKI/ROA from IPXO saying that AS63025 is authorized to announce said range.
can also announce it for you and put your asn in the path
thanks.
Suing Massivegrid for 30 million because they terminated my $3/year vps, which was being used for mission-critical communications between the Mars rover and NASA’s mission control.