bgpreport

Network · data from 2026-11-12

AS401984

Not in the RIR AS name list · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS401984, 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.
164.37.210.0/24 Valid Other IRR onlyRADB 449 67% 66
164.37.211.0/24 Valid Other IRR onlyRADB 449 67% 66
155.254.100.0/22 Valid RIR databaseRADB, RIPE 672 100% 66
103.99.60.0/23 Valid RIR databaseAPNIC, RADB 671 100% 66
164.37.210.0/23 Valid RIR databaseRADB, RIPE 662 98% 66
155.254.100.0/23 Valid RIR databaseRADB, RIPE 449 67% 66
155.254.101.0/24 Valid RIR databaseRADB, RIPE 449 67% 66
155.254.102.0/23 Valid RIR databaseRADB, RIPE 449 67% 66
155.254.100.0/24 Valid RIR databaseRADB, RIPE 405 60% 66
155.254.102.0/24 Valid RIR databaseRADB, RIPE 405 60% 66
155.254.103.0/24 Valid RIR databaseRADB, RIPE 405 60% 66
103.99.60.0/24 Valid RIR databaseAPNIC 160 24% 55

AS-SET

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

  • Route object: RIR2
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
Route object: RIR164.37.210.0/24Route object only in RADB. Add it in the RIR database for the space.449 of 673
Route object: RIR164.37.211.0/24Route object only in RADB. Add it in the RIR database for the space.449 of 673

Route objects not announced

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

77.67.126.0/23RADBValid
77.67.126.0/24RADBValid
77.67.127.0/24RADBValid
82.108.196.0/23RADB, RIPEValid
82.108.196.0/24RADBValid
82.108.197.0/24RADBValid
103.99.61.0/24APNICValid
212.189.100.0/23RADBValid
212.189.100.0/24RADBValid
212.189.101.0/24RADBValid

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.