bgpreport

Network · data from 2026-11-12

AS22906 TWAI - FRIT

Registry name: TWAI - FRIT, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22906, 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.
199.169.194.0/23 No ROA None 672 100% 67
2605:3100:fffd::/48 No ROA None 2 0%low visibility 2
199.169.196.0/24 No ROA Other IRR onlyRADB 672 100% 67
199.169.198.0/24 No ROA Other IRR onlyRADB 672 100% 67
2605:3100:fffb::/48 No ROA Other IRR onlyRADB 633 100% 70
2605:3100:fffc::/48 No ROA Other IRR onlyRADB 633 100% 70
199.169.192.0/23 No ROA Other IRR onlyRADB 2 0%low visibility 2
199.169.196.0/23 No ROA Other IRR onlyRADB 2 0%low visibility 2
199.169.198.0/23 No ROA Other IRR onlyRADB 2 0%low visibility 2
199.169.194.0/24 No ROA RIR databaseARIN, RADB 672 100% 67
199.169.195.0/24 No ROA RIR databaseARIN, RADB 672 100% 67

AS-SET

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

  • ROA: none11
  • Route object: none2
  • Route object: RIR7
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none199.169.194.0/23No ROA covers it. Add a ROA for AS22906, maxLength 23.672 of 673
Route object: none199.169.194.0/23No route object for it. Add a route object with origin AS22906 in the RIR database for the space.672 of 673
ROA: none2605:3100:fffd::/48No ROA covers it. Add a ROA for AS22906, maxLength 48.2 of 636
Route object: none2605:3100:fffd::/48No route object for it. Add a route object with origin AS22906 in the RIR database for the space.2 of 636
ROA: none199.169.196.0/24No ROA covers it. Add a ROA for AS22906, maxLength 24.672 of 673
Route object: RIR199.169.196.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none199.169.198.0/24No ROA covers it. Add a ROA for AS22906, maxLength 24.672 of 673
Route object: RIR199.169.198.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2605:3100:fffb::/48No ROA covers it. Add a ROA for AS22906, maxLength 48.633 of 636
Route object: RIR2605:3100:fffb::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636
ROA: none2605:3100:fffc::/48No ROA covers it. Add a ROA for AS22906, maxLength 48.633 of 636
Route object: RIR2605:3100:fffc::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636
ROA: none199.169.192.0/23No ROA covers it. Add a ROA for AS22906, maxLength 23.2 of 673
Route object: RIR199.169.192.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none199.169.196.0/23No ROA covers it. Add a ROA for AS22906, maxLength 23.2 of 673
Route object: RIR199.169.196.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none199.169.198.0/23No ROA covers it. Add a ROA for AS22906, maxLength 23.2 of 673
Route object: RIR199.169.198.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none199.169.194.0/24No ROA covers it. Add a ROA for AS22906, maxLength 24.672 of 673
ROA: none199.169.195.0/24No ROA covers it. Add a ROA for AS22906, maxLength 24.672 of 673

Route objects not announced

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

199.169.192.0/24ARINNo ROA
199.169.193.0/24ARINNo ROA
199.169.197.0/24ARIN, RADBNo ROA
199.169.199.0/24ARIN, RADBNo 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.