Re: IPv4 Subnet 23.151.232.0/24 blackholed?

[August Yang via NANOG <nanog () nanog org>]

The range has only been announced for 2 hours. Just wait longer for 
filters to refresh as Ryan advised.

On 2023-04-25 10:49 p.m., Ryan Hamel wrote:
> Neel,
>
> Carriers rebuild their prefixes lists once or twice in a 24 hour 
> period. Considering that you just got the block today and is in 
> ReliableSite's AS-SET, you just got to be patient.
>
> Having announcements propagated immediately either sounds like it 
> happened a day after you gave them the LOA, or they have unfiltered 
> transit circuits, which is worrisome.
>
> Ryan
>
> ------ Original Message ------
> From "Neel Chauhan" <neel () neelc org>
> To nanog () nanog org
> Date 4/25/2023 7:35:40 PM
> Subject IPv4 Subnet 23.151.232.0/24 blackholed?
>
> > 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
--
Best regards
August Yang

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature