bgpreport

Network · data from 2026-11-12

AS18461 BELL-ATL - Verizon Business

Registry name: BELL-ATL - Verizon Business, US · not in PeeringDB

10IPv4 routes 0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
6RPKI invalid 6 origin · 0 maxLength
4No ROA 10 with no route object for this origin
9Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS18461, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS18461, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

63.21.176.0/21 Invalid: origin None 1 0%low visibility 1
63.21.184.0/21 Invalid: origin None 1 0%low visibility 1
63.25.0.0/17 Invalid: origin None 1 0%low visibility 1
153.114.128.0/20 Invalid: origin None 1 0%low visibility 1
153.114.183.0/24 Invalid: origin None 1 0%low visibility 1
153.114.216.0/22 Invalid: origin None 1 0%low visibility 1
138.83.75.0/24 No ROA None 673 100% 67
138.83.99.0/24 No ROA None 1 0%low visibility 1
138.83.109.0/24 No ROA None 1 0%low visibility 1
148.131.24.0/24 No ROA None 1 0%low visibility 1

AS-SET

AS18461 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 20 are in fix.csv.

  • ROA: origin6
  • ROA: none4
  • Route object: none10
ChangePrefix or setDetailFull-table peers
ROA: origin63.21.176.0/21ROAs covering it name AS701, not AS18461. If AS18461 should announce it, add a ROA for AS18461.1 of 673
Route object: none63.21.176.0/21No route object for it. Add a route object with origin AS18461 in the RIR database for the space.1 of 673
ROA: origin63.21.184.0/21ROAs covering it name AS701, not AS18461. If AS18461 should announce it, add a ROA for AS18461.1 of 673
Route object: none63.21.184.0/21No route object for it. Add a route object with origin AS18461 in the RIR database for the space.1 of 673
ROA: origin63.25.0.0/17ROAs covering it name AS701, not AS18461. If AS18461 should announce it, add a ROA for AS18461.1 of 673
Route object: none63.25.0.0/17No route object for it. Add a route object with origin AS18461 in the RIR database for the space.1 of 673
ROA: origin153.114.128.0/20ROAs covering it name AS12079, not AS18461. If AS18461 should announce it, add a ROA for AS18461.1 of 673
Route object: none153.114.128.0/20No route object for it. Add a route object with origin AS18461 in the RIR database for the space.1 of 673
ROA: origin153.114.183.0/24ROAs covering it name AS12079, not AS18461. If AS18461 should announce it, add a ROA for AS18461.1 of 673
Route object: none153.114.183.0/24No route object for it. Add a route object with origin AS18461 in the RIR database for the space.1 of 673
ROA: origin153.114.216.0/22ROAs covering it name AS12079, not AS18461. If AS18461 should announce it, add a ROA for AS18461.1 of 673
Route object: none153.114.216.0/22No route object for it. Add a route object with origin AS18461 in the RIR database for the space.1 of 673
ROA: none138.83.75.0/24No ROA covers it. Add a ROA for AS18461, maxLength 24.673 of 673
Route object: none138.83.75.0/24No route object for it. Add a route object with origin AS18461 in the RIR database for the space.673 of 673
ROA: none138.83.99.0/24No ROA covers it. Add a ROA for AS18461, maxLength 24.1 of 673
Route object: none138.83.99.0/24No route object for it. Add a route object with origin AS18461 in the RIR database for the space.1 of 673
ROA: none138.83.109.0/24No ROA covers it. Add a ROA for AS18461, maxLength 24.1 of 673
Route object: none138.83.109.0/24No route object for it. Add a route object with origin AS18461 in the RIR database for the space.1 of 673
ROA: none148.131.24.0/24No ROA covers it. Add a ROA for AS18461, maxLength 24.1 of 673
Route object: none148.131.24.0/24No route object for it. Add a route object with origin AS18461 in the RIR database for the space.1 of 673

Route objects not announced

Every route object with origin AS18461 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.