bgpreport

Network · data from 2026-11-12

AS398326 IMINTERNET

Registry name: IMINTERNET - IM Internet LLC, PR · PeeringDB

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

Announced routes

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

2605:db40:8000::/33 No ROA Nonecovered by 2605:db40::/32 635 100% 69
165.140.160.0/24 No ROA Other IRR onlyRADB 671 100% 68
165.140.161.0/24 No ROA Other IRR onlyRADB 671 100% 68
165.140.162.0/24 No ROA Other IRR onlyRADB 667 99% 68
165.140.163.0/24 No ROA Other IRR onlyRADB 667 99% 68
2605:db40::/33 No ROA Other IRR onlyRADB 631 99% 69
23.134.8.0/24 No ROA RIR databaseARIN 671 100% 68
165.140.160.0/22 No ROA RIR databaseARIN 671 100% 68

AS-SET

PeeringDB's irr_as_set for AS398326: RADB::AS398326:AS-ALL RADB::AS398326:AS-ALL-IPV6. 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 (AS398326 isn't in the set, or no route object for AS398326 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 objectsAS398326 in itNot covered
RADB::AS398326:AS-ALL In no IRR database read today.
RADB::AS398326:AS-ALL-IPV6 In no IRR database read today.

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

  • ROA: none8
  • Route object: none1
  • Route object: RIR5
  • AS-SET: not found2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2605:db40:8000::/33No ROA covers it. Add a ROA for AS398326, maxLength 33.635 of 636
Route object: none2605:db40:8000::/33No route object for it. A route object for 2605:db40::/32 with origin AS398326 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398326 in the RIR database for the space.635 of 636
ROA: none165.140.160.0/24No ROA covers it. Add a ROA for AS398326, maxLength 24.671 of 673
Route object: RIR165.140.160.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none165.140.161.0/24No ROA covers it. Add a ROA for AS398326, maxLength 24.671 of 673
Route object: RIR165.140.161.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none165.140.162.0/24No ROA covers it. Add a ROA for AS398326, maxLength 24.667 of 673
Route object: RIR165.140.162.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none165.140.163.0/24No ROA covers it. Add a ROA for AS398326, maxLength 24.667 of 673
Route object: RIR165.140.163.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none2605:db40::/33No ROA covers it. Add a ROA for AS398326, maxLength 33.631 of 636
Route object: RIR2605:db40::/33Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none23.134.8.0/24No ROA covers it. Add a ROA for AS398326, maxLength 24.671 of 673
ROA: none165.140.160.0/22No ROA covers it. Add a ROA for AS398326, maxLength 22.671 of 673
AS-SET: not foundRADB::AS398326:AS-ALLPeeringDB names RADB::AS398326:AS-ALL; no IRR database read has it.
AS-SET: not foundRADB::AS398326:AS-ALL-IPV6PeeringDB names RADB::AS398326:AS-ALL-IPV6; no IRR database read has it.

Route objects not announced

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

165.140.160.0/23RADBNo ROA
2605:db40::/32ARINNo 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.