bgpreport

Network · data from 2026-11-12

AS51110 idomtechnologies-as Idom Technologies SAS

Registry name: idomtechnologies-as Idom Technologies SAS, MQ · not in PeeringDB

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

Announced routes

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

102.135.225.0/24 No ROA Nonecovered by 102.135.224.0/20 673 100% 67
102.135.226.0/24 No ROA Nonecovered by 102.135.224.0/20 673 100% 67
102.135.227.0/24 No ROA Nonecovered by 102.135.224.0/20 673 100% 67
102.135.228.0/24 No ROA Nonecovered by 102.135.224.0/20 673 100% 67
102.135.229.0/24 No ROA Nonecovered by 102.135.224.0/20 673 100% 67
102.135.230.0/24 No ROA Nonecovered by 102.135.224.0/20 673 100% 67
102.135.231.0/24 No ROA Nonecovered by 102.135.224.0/20 673 100% 67
102.135.232.0/24 No ROA Nonecovered by 102.135.224.0/20 673 100% 67
102.135.233.0/24 No ROA Nonecovered by 102.135.224.0/20 672 100% 67
2c0f:6c00::/40 No ROA Nonecovered by 2c0f:6c00::/32 636 100% 70
2c0f:6c00:fff0::/48 No ROA Nonecovered by 2c0f:6c00:fff0::/44 636 100% 70
2c0f:6c00:3fff::/48 No ROA Nonecovered by 2c0f:6c00::/32 605 95% 67
102.135.224.0/24 No ROA Other IRR onlyRIPE-NONAUTH 673 100% 67
154.49.224.0/24 No ROA Other IRR onlyRADB 672 100% 67
154.49.225.0/24 No ROA Other IRR onlyRADB 672 100% 67
154.49.226.0/24 No ROA Other IRR onlyRADB 672 100% 67
193.56.203.0/24 No ROA RIR databaseRIPE 673 100% 66
5.102.78.0/24 Valid Other IRR onlyRADB 672 100% 67
94.124.152.0/24 Valid Other IRR onlyRADB 672 100% 67
94.124.155.0/24 Valid Other IRR onlyRADB 672 100% 67
185.91.234.0/24 Valid Other IRR onlyRADB 672 100% 67
5.102.72.0/24 Valid RIR databaseRIPE 673 100% 66
94.124.153.0/24 Valid RIR databaseRIPE 673 100% 66
94.124.154.0/24 Valid RIR databaseRIPE 673 100% 66
94.124.157.0/24 Valid RIR databaseRIPE 673 100% 66
94.124.158.0/24 Valid RIR databaseRIPE 673 100% 66
94.124.159.0/24 Valid RIR databaseRIPE 673 100% 66
185.91.232.0/24 Valid RIR databaseRIPE 673 100% 66
5.102.73.0/24 Valid RIR databaseRIPE 672 100% 67
5.102.76.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
5.102.77.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
5.102.79.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
94.124.156.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
185.91.233.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
5.102.75.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

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

  • ROA: none17
  • Route object: none12
  • Route object: RIR8
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none102.135.225.0/24No ROA covers it. Add a ROA for AS51110, maxLength 24.673 of 673
Route object: none102.135.225.0/24No route object for it. A route object for 102.135.224.0/20 with origin AS51110 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51110 in the RIR database for the space.673 of 673
ROA: none102.135.226.0/24No ROA covers it. Add a ROA for AS51110, maxLength 24.673 of 673
Route object: none102.135.226.0/24No route object for it. A route object for 102.135.224.0/20 with origin AS51110 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51110 in the RIR database for the space.673 of 673
ROA: none102.135.227.0/24No ROA covers it. Add a ROA for AS51110, maxLength 24.673 of 673
Route object: none102.135.227.0/24No route object for it. A route object for 102.135.224.0/20 with origin AS51110 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51110 in the RIR database for the space.673 of 673
ROA: none102.135.228.0/24No ROA covers it. Add a ROA for AS51110, maxLength 24.673 of 673
Route object: none102.135.228.0/24No route object for it. A route object for 102.135.224.0/20 with origin AS51110 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51110 in the RIR database for the space.673 of 673
ROA: none102.135.229.0/24No ROA covers it. Add a ROA for AS51110, maxLength 24.673 of 673
Route object: none102.135.229.0/24No route object for it. A route object for 102.135.224.0/20 with origin AS51110 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51110 in the RIR database for the space.673 of 673
ROA: none102.135.230.0/24No ROA covers it. Add a ROA for AS51110, maxLength 24.673 of 673
Route object: none102.135.230.0/24No route object for it. A route object for 102.135.224.0/20 with origin AS51110 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51110 in the RIR database for the space.673 of 673
ROA: none102.135.231.0/24No ROA covers it. Add a ROA for AS51110, maxLength 24.673 of 673
Route object: none102.135.231.0/24No route object for it. A route object for 102.135.224.0/20 with origin AS51110 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51110 in the RIR database for the space.673 of 673
ROA: none102.135.232.0/24No ROA covers it. Add a ROA for AS51110, maxLength 24.673 of 673
Route object: none102.135.232.0/24No route object for it. A route object for 102.135.224.0/20 with origin AS51110 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51110 in the RIR database for the space.673 of 673
ROA: none102.135.233.0/24No ROA covers it. Add a ROA for AS51110, maxLength 24.672 of 673
Route object: none102.135.233.0/24No route object for it. A route object for 102.135.224.0/20 with origin AS51110 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51110 in the RIR database for the space.672 of 673
ROA: none2c0f:6c00::/40No ROA covers it. Add a ROA for AS51110, maxLength 40.636 of 636
Route object: none2c0f:6c00::/40No route object for it. A route object for 2c0f:6c00::/32 with origin AS51110 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51110 in the RIR database for the space.636 of 636
ROA: none2c0f:6c00:fff0::/48No ROA covers it. Add a ROA for AS51110, maxLength 48.636 of 636
Route object: none2c0f:6c00:fff0::/48No route object for it. A route object for 2c0f:6c00:fff0::/44 with origin AS51110 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51110 in the RIR database for the space.636 of 636
ROA: none2c0f:6c00:3fff::/48No ROA covers it. Add a ROA for AS51110, maxLength 48.605 of 636
Route object: none2c0f:6c00:3fff::/48No route object for it. A route object for 2c0f:6c00::/32 with origin AS51110 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51110 in the RIR database for the space.605 of 636
ROA: none102.135.224.0/24No ROA covers it. Add a ROA for AS51110, maxLength 24.673 of 673
Route object: RIR102.135.224.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
ROA: none154.49.224.0/24No ROA covers it. Add a ROA for AS51110, maxLength 24.672 of 673
Route object: RIR154.49.224.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none154.49.225.0/24No ROA covers it. Add a ROA for AS51110, maxLength 24.672 of 673
Route object: RIR154.49.225.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none154.49.226.0/24No ROA covers it. Add a ROA for AS51110, maxLength 24.672 of 673
Route object: RIR154.49.226.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none193.56.203.0/24No ROA covers it. Add a ROA for AS51110, maxLength 24.673 of 673
Route object: RIR5.102.78.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR94.124.152.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR94.124.155.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR185.91.234.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 AS51110 whose prefix no peer sees AS51110 announce. Many are kept on purpose (backup routes, space announced only in some places).

5.102.74.0/24RIPEValid
102.135.224.0/20RIPE-NONAUTHNo ROA
154.41.244.0/22RADBNo ROA
154.49.224.0/22RADBNo ROA
154.49.227.0/24RADBNo ROA
2c0f:6c00::/32AFRINICNo ROA
2c0f:6c00:fff0::/44AFRINICNo 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.