bgpreport

Network · data from 2026-11-12

AS396426

Not in the RIR AS name list · not in PeeringDB

7IPv4 routes 42.9% RPKI valid · 85.7% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
3No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS396426, seen from no peer

Announced routes

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

185.101.22.0/24 Invalid: origin Other origin only 0 0%low visibility 1
209.94.190.0/24 No ROA Other IRR onlyRADB 670 100% 68
209.94.191.0/24 No ROA Other IRR onlyRADB 670 100% 68
174.136.229.0/24 No ROA RIR databaseARIN 670 100% 68
47.45.19.0/24 Valid Other IRR onlyRADB 670 100% 68
176.111.219.0/24 Valid RIR databaseRIPE 670 100% 68
45.141.12.0/24 Valid RIR databaseRIPE 664 99% 68

AS-SET

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

  • ROA: origin1
  • ROA: none3
  • Route object: none1
  • Route object: RIR3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin185.101.22.0/24ROAs covering it name AS200823, not AS396426. If AS396426 should announce it, add a ROA for AS396426.0 of 673
Route object: none185.101.22.0/24Route objects for it name AS200823. Add a route object with origin AS396426 in the RIR database for the space.0 of 673
ROA: none209.94.190.0/24No ROA covers it. Add a ROA for AS396426, maxLength 24.670 of 673
Route object: RIR209.94.190.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none209.94.191.0/24No ROA covers it. Add a ROA for AS396426, maxLength 24.670 of 673
Route object: RIR209.94.191.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none174.136.229.0/24No ROA covers it. Add a ROA for AS396426, maxLength 24.670 of 673
Route object: RIR47.45.19.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

209.94.173.0/24RADBNo ROA
2606:6680:39::/48ARINNo ROA
2606:6680:40::/48ARINNo 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.