You need to talk to ReliableSite and have them talk to their transits about accepting 23.151.232.0/24. I see that you did create a route object... route: 23.151.232.0/24 origin: AS23470 descr: Qeru Systems, LLC mnt-by: MAINT-AS23470 changed: jcid@reliablesite.net 20230425 #01:09:36Z source: RADB but I'd dump RADB and create this object in the authoratative IRR, in this case ARIN's rr.arin.net. At least some "Tier 1's" no longer honor route objects from non-authoratative IRRs when building prefix-list filters for their customers BGP sessions. I'm not receiving your route, and route-views doesn't see it either. On Tue, 25 Apr 2023, Neel Chauhan wrote:
Hi,
I recently got the IPv4 allocation 23.151.232.0/24 from ARIN. I also had my hosting company ReliableSite announce it to the internet.
Right now, I can only access networks that peer with ReliableSite via internet exchanges, such as Google, CloudFlare, OVH, Hurricane Electric, et al.
It seems the Tier 1 ISPs (e.g. Lumen, Cogent, AT&T, et al.) are blackholing the IPv4 subnet 23.151.232.0/24. Could someone who works at a Tier 1 NOC please check and remove the blackhole if any exists?
Normally when ReliableSite announced my prior (then-leased) IPv4 space it gets propagated via BGP almost immediately. This time it's not going through at all.
Best,
Neel Chauhan
---------------------------------------------------------------------- Jon Lewis, MCP :) | I route StackPath, Sr. Neteng | therefore you are _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________