bgpreport

Network · data from 2026-11-12

AS400702 Inverdigm Inc.

Registry name: AS-INVERDIGM - Inverdigm Inc., CA · PeeringDB

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

Announced routes

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

74.118.36.0/23 No ROA None 2 0%low visibility 2
2604:6580:2920::/48 Valid Nonecovered by 2604:6580::/32 605 95% 67
74.118.38.0/24 Valid Other IRR onlyRADB 672 100% 67
74.118.39.0/24 Valid Other IRR onlyRADB 672 100% 67
192.81.172.0/22 Valid RIR databaseARIN 673 100% 67
199.127.128.0/24 Valid RIR databaseARIN 673 100% 67

AS-SET

AS400702's PeeringDB record names no 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: none1
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none74.118.36.0/23No ROA covers it. Add a ROA for AS400702, maxLength 23.2 of 673
Route object: none74.118.36.0/23No route object for it. Add a route object with origin AS400702 in the RIR database for the space.2 of 673
Route object: none2604:6580:2920::/48No route object for it. A route object for 2604:6580::/32 with origin AS400702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400702 in the RIR database for the space.605 of 636
Route object: RIR74.118.38.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR74.118.39.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

74.118.38.0/23ARINValid
192.81.172.0/24RADBValid
192.81.173.0/24RADBValid
192.81.174.0/24RADBValid
192.81.175.0/24RADBValid
2604:6580::/32RADBValid

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.