bgpreport

Network · data from 2026-11-12

AS395214 MICROCOM TECHNOLOGIES

Registry name: MICROCOM - Microcom Informatique, Inc., CA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS395214, 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.
172.82.110.0/24 Valid Nonecovered by 172.82.108.0/22 672 100% 67
172.82.109.0/24 Valid Nonecovered by 172.82.108.0/22 2 0%low visibility 2
23.137.0.0/24 Valid RIR databaseARIN 672 100% 67
172.82.108.0/24 Valid RIR databaseARIN 672 100% 67
172.82.111.0/24 Valid RIR databaseARIN 672 100% 67

AS-SET

AS395214'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 4 are in fix.csv.

  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none172.82.110.0/24No route object for it. A route object for 172.82.108.0/22 with origin AS395214 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395214 in the RIR database for the space.672 of 673
Route object: none172.82.109.0/24No route object for it. A route object for 172.82.108.0/22 with origin AS395214 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395214 in the RIR database for the space.2 of 673

Route objects not announced

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

172.82.108.0/22ARINValid
2602:ff3d::/36ARINValid

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.