bgpreport

Network · data from 2026-11-12

AS53863 IDLOGIC-MTL - I.D. Logique

Registry name: IDLOGIC-MTL - I.D. Logique, CA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53863, 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.
23.247.164.0/24 Valid Nonecovered by 23.247.164.0/22 673 100% 67
23.247.165.0/24 Valid Nonecovered by 23.247.164.0/22 673 100% 67
23.247.166.0/24 Valid Nonecovered by 23.247.164.0/22 673 100% 67
23.247.167.0/24 Valid Nonecovered by 23.247.164.0/22 671 100% 68
38.108.72.0/23 Valid RIR databaseARIN 673 100% 67
38.128.238.0/23 Valid RIR databaseARIN 673 100% 67
64.49.24.0/22 Valid RIR databaseARIN 673 100% 67
23.247.164.0/22 Valid RIR databaseARIN 671 100% 68
142.202.212.0/22 Valid RIR databaseARIN 671 100% 68
38.69.208.0/21 Valid RIR databaseARIN 670 100% 67
208.73.156.0/22 Valid RIR databaseARIN 1 0%low visibility 1

AS-SET

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

  • Route object: none4
ChangePrefix or setDetailFull-table peers
Route object: none23.247.164.0/24No route object for it. A route object for 23.247.164.0/22 with origin AS53863 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53863 in the RIR database for the space.673 of 673
Route object: none23.247.165.0/24No route object for it. A route object for 23.247.164.0/22 with origin AS53863 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53863 in the RIR database for the space.673 of 673
Route object: none23.247.166.0/24No route object for it. A route object for 23.247.164.0/22 with origin AS53863 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53863 in the RIR database for the space.673 of 673
Route object: none23.247.167.0/24No route object for it. A route object for 23.247.164.0/22 with origin AS53863 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53863 in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS53863 is announced.

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.