bgpreport

Network · data from 2026-11-12

AS394034 BROOKLYN-FIBER

Registry name: BROOKLYN-FIBER - Brooklyn Fiber, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS394034, 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.

38.83.38.0/23 No ROA Other IRR onlyRADB 671 100% 68
38.84.204.0/23 No ROA Other IRR onlyRADB 671 100% 68
38.89.128.0/23 No ROA Other IRR onlyRADB 671 100% 68
38.96.136.0/23 No ROA Other IRR onlyRADB 671 100% 68
38.96.171.0/24 No ROA Other IRR onlyRADB 671 100% 68
38.100.171.0/24 No ROA Other IRR onlyRADB 671 100% 68
38.105.230.0/24 No ROA Other IRR onlyRADB 671 100% 68
38.125.194.0/24 No ROA Other IRR onlyRADB 671 100% 68
2604:15e0::/32 No ROA RIR databaseARIN 632 99% 69
184.104.185.0/24 Valid Nonecovered by 184.104.184.0/23 673 100% 67
184.104.184.0/23 Valid RIR databaseARIN 671 100% 68

AS-SET

PeeringDB's irr_as_set for AS394034: AS394034:AS-BKFIBER. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS394034 isn't in the set, or no route object for AS394034 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS394034 in itNot covered
AS394034:AS-BKFIBER ARIN 1119 Yes 0

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 27 are in fix.csv.

  • ROA: none9
  • Route object: none1
  • Route object: RIR8
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none38.83.38.0/23No ROA covers it. Add a ROA for AS394034, maxLength 23.671 of 673
Route object: RIR38.83.38.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.84.204.0/23No ROA covers it. Add a ROA for AS394034, maxLength 23.671 of 673
Route object: RIR38.84.204.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.89.128.0/23No ROA covers it. Add a ROA for AS394034, maxLength 23.671 of 673
Route object: RIR38.89.128.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.96.136.0/23No ROA covers it. Add a ROA for AS394034, maxLength 23.671 of 673
Route object: RIR38.96.136.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.96.171.0/24No ROA covers it. Add a ROA for AS394034, maxLength 24.671 of 673
Route object: RIR38.96.171.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.100.171.0/24No ROA covers it. Add a ROA for AS394034, maxLength 24.671 of 673
Route object: RIR38.100.171.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.105.230.0/24No ROA covers it. Add a ROA for AS394034, maxLength 24.671 of 673
Route object: RIR38.105.230.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.125.194.0/24No ROA covers it. Add a ROA for AS394034, maxLength 24.671 of 673
Route object: RIR38.125.194.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2604:15e0::/32No ROA covers it. Add a ROA for AS394034, maxLength 32.632 of 636
Route object: none184.104.185.0/24No route object for it. A route object for 184.104.184.0/23 with origin AS394034 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394034 in the RIR database for the space.673 of 673

Route objects not announced

Route objects with origin AS394034 whose prefix no peer sees AS394034 announce. Many are kept on purpose (backup routes, space announced only in some places).

38.83.38.0/24RADBNo ROA
38.83.39.0/24RADBNo ROA
38.84.204.0/24RADBNo ROA
38.84.205.0/24RADBNo ROA
38.89.128.0/24RADBNo ROA
38.89.129.0/24RADBNo ROA
38.96.136.0/24RADBNo ROA
38.96.137.0/24RADBNo ROA
2001:470:33::/48ARINValid

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.