Now this is kind of interesting. I see route-views can see the route
now...
BGP routing table entry for 23.151.232.0/24, version 2814701286
Paths: (19 available, best #19, table default)
Not advertised to any peer
Refresh Epoch 1
1257 6453 23470 23470 23470 23470
193.0.0.56 from
- Age: 3 hours (Wed, 26 Apr 2023 08:57:05 UTC)
Thanks
Travis
*From:* NANOG *On
Behalf Of *August Yang via NANOG
*Sent:* Tuesday, April 25, 2023 9:54 PM
*To:* Ryan Hamel ; Neel Chauhan ;
nanog@nanog.org
*Subject:* Re: IPv4 Subnet 23.151.232.0/24 blackholed?
The range has only been
NANOG
Sent: Tuesday, April 25, 2023 9:54 PM
To: Ryan Hamel ; Neel Chauhan ;
nanog@nanog.org
Subject: Re: IPv4 Subnet 23.151.232.0/24 blackholed?
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
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
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:
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
6 matches
Mail list logo
