bgpreport

Network · data from 2026-11-12

AS394449 FYBERCOM

Registry name: FYBERCOM - FyberCom, LLC, US · PeeringDB

26IPv4 routes 3.8% RPKI valid · 92.3% with a route object
2IPv6 routes 100.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
25No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS394449, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS394449, 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.43.0.0/24 No ROA Nonecovered by 38.43.0.0/18 672 100% 67
23.154.168.0/24 No ROA None 112 17% 40
38.43.0.0/18 No ROA Other IRR onlyALTDB, RADB 673 100% 67
38.78.196.0/24 No ROA Other IRR onlyALTDB, RADB 670 100% 67
38.78.197.0/24 No ROA Other IRR onlyALTDB, RADB 670 100% 67
38.78.198.0/24 No ROA Other IRR onlyALTDB, RADB 670 100% 67
38.78.199.0/24 No ROA Other IRR onlyALTDB, RADB 670 100% 67
38.141.48.0/24 No ROA Other IRR onlyALTDB, RADB 670 100% 67
38.141.49.0/24 No ROA Other IRR onlyALTDB, RADB 670 100% 67
38.141.50.0/24 No ROA Other IRR onlyALTDB, RADB 670 100% 67
38.141.52.0/24 No ROA Other IRR onlyALTDB, RADB 670 100% 67
38.141.53.0/24 No ROA Other IRR onlyALTDB, RADB 670 100% 67
38.141.54.0/24 No ROA Other IRR onlyALTDB, RADB 670 100% 67
38.141.55.0/24 No ROA Other IRR onlyALTDB, RADB 670 100% 67
38.141.56.0/24 No ROA Other IRR onlyALTDB, RADB 670 100% 67
38.141.57.0/24 No ROA Other IRR onlyALTDB, RADB 670 100% 67
38.141.58.0/24 No ROA Other IRR onlyALTDB, RADB 670 100% 67
38.141.59.0/24 No ROA Other IRR onlyALTDB, RADB 670 100% 67
38.141.51.0/24 No ROA Other IRR onlyALTDB, RADB 667 99% 67
38.43.8.0/21 No ROA Other IRR onlyALTDB, RADB 204 30% 56
38.43.16.0/20 No ROA Other IRR onlyALTDB, RADB 204 30% 56
38.43.32.0/19 No ROA Other IRR onlyALTDB, RADB 204 30% 56
38.141.48.0/21 No ROA Other IRR onlyALTDB, RADB 204 30% 56
38.78.196.0/22 No ROA Other IRR onlyALTDB, RADB 202 30% 56
38.141.56.0/22 No ROA Other IRR onlyALTDB, RADB 202 30% 56
2604:3dc0:2::/48 Valid Nonecovered by 2604:3dc0::/32 605 95% 67
199.68.53.0/24 Valid RIR databaseALTDB, ARIN, RADB 671 100% 67
2604:3dc0::/32 Valid RIR databaseARIN 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS394449: AS-ORG-FYBERCOM. 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 (AS394449 isn't in the set, or no route object for AS394449 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 objectsAS394449 in itNot covered
AS-ORG-FYBERCOM ARIN 010 No 28

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

  • ROA: none25
  • Route object: none3
  • Route object: RIR23
  • AS-SET: own ASN1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none38.43.0.0/24No ROA covers it. Add a ROA for AS394449, maxLength 24.672 of 673
Route object: none38.43.0.0/24No route object for it. A route object for 38.43.0.0/18 with origin AS394449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394449 in the RIR database for the space.672 of 673
ROA: none23.154.168.0/24No ROA covers it. Add a ROA for AS394449, maxLength 24.112 of 673
Route object: none23.154.168.0/24No route object for it. Add a route object with origin AS394449 in the RIR database for the space.112 of 673
ROA: none38.43.0.0/18No ROA covers it. Add a ROA for AS394449, maxLength 18.673 of 673
Route object: RIR38.43.0.0/18Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.78.196.0/24No ROA covers it. Add a ROA for AS394449, maxLength 24.670 of 673
Route object: RIR38.78.196.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.78.197.0/24No ROA covers it. Add a ROA for AS394449, maxLength 24.670 of 673
Route object: RIR38.78.197.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.78.198.0/24No ROA covers it. Add a ROA for AS394449, maxLength 24.670 of 673
Route object: RIR38.78.198.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.78.199.0/24No ROA covers it. Add a ROA for AS394449, maxLength 24.670 of 673
Route object: RIR38.78.199.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.141.48.0/24No ROA covers it. Add a ROA for AS394449, maxLength 24.670 of 673
Route object: RIR38.141.48.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.141.49.0/24No ROA covers it. Add a ROA for AS394449, maxLength 24.670 of 673
Route object: RIR38.141.49.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.141.50.0/24No ROA covers it. Add a ROA for AS394449, maxLength 24.670 of 673
Route object: RIR38.141.50.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.141.52.0/24No ROA covers it. Add a ROA for AS394449, maxLength 24.670 of 673
Route object: RIR38.141.52.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.141.53.0/24No ROA covers it. Add a ROA for AS394449, maxLength 24.670 of 673
Route object: RIR38.141.53.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.141.54.0/24No ROA covers it. Add a ROA for AS394449, maxLength 24.670 of 673
Route object: RIR38.141.54.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.141.55.0/24No ROA covers it. Add a ROA for AS394449, maxLength 24.670 of 673
Route object: RIR38.141.55.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.141.56.0/24No ROA covers it. Add a ROA for AS394449, maxLength 24.670 of 673
Route object: RIR38.141.56.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.141.57.0/24No ROA covers it. Add a ROA for AS394449, maxLength 24.670 of 673
Route object: RIR38.141.57.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.141.58.0/24No ROA covers it. Add a ROA for AS394449, maxLength 24.670 of 673
Route object: RIR38.141.58.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.141.59.0/24No ROA covers it. Add a ROA for AS394449, maxLength 24.670 of 673
Route object: RIR38.141.59.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.141.51.0/24No ROA covers it. Add a ROA for AS394449, maxLength 24.667 of 673
Route object: RIR38.141.51.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.667 of 673
ROA: none38.43.8.0/21No ROA covers it. Add a ROA for AS394449, maxLength 21.204 of 673
Route object: RIR38.43.8.0/21Route object only in ALTDB, RADB. Add it in the RIR database for the space.204 of 673
ROA: none38.43.16.0/20No ROA covers it. Add a ROA for AS394449, maxLength 20.204 of 673
Route object: RIR38.43.16.0/20Route object only in ALTDB, RADB. Add it in the RIR database for the space.204 of 673
ROA: none38.43.32.0/19No ROA covers it. Add a ROA for AS394449, maxLength 19.204 of 673
Route object: RIR38.43.32.0/19Route object only in ALTDB, RADB. Add it in the RIR database for the space.204 of 673
ROA: none38.141.48.0/21No ROA covers it. Add a ROA for AS394449, maxLength 21.204 of 673
Route object: RIR38.141.48.0/21Route object only in ALTDB, RADB. Add it in the RIR database for the space.204 of 673
ROA: none38.78.196.0/22No ROA covers it. Add a ROA for AS394449, maxLength 22.202 of 673
Route object: RIR38.78.196.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.202 of 673
ROA: none38.141.56.0/22No ROA covers it. Add a ROA for AS394449, maxLength 22.202 of 673
Route object: RIR38.141.56.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.202 of 673
Route object: none2604:3dc0:2::/48No route object for it. A route object for 2604:3dc0::/32 with origin AS394449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394449 in the RIR database for the space.605 of 636
AS-SET: own ASNAS-ORG-FYBERCOMAS394449 isn't in AS-ORG-FYBERCOM (ARIN) once expanded. Add AS394449 to it.

Route objects not announced

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

23.170.192.0/24ALTDB, ARIN, RADBValid
38.141.48.0/22RADBNo ROA

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.