bgpreport

Network · data from 2026-11-12

AS61205 INFOMIL

Registry name: INFOMIL Infomil S.A.S., FR · PeeringDB

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

Announced routes

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

45.136.92.0/23 No ROA Nonecovered by 45.136.92.0/22 672 100% 66
45.136.94.0/23 No ROA Nonecovered by 45.136.92.0/22 672 100% 66
46.247.144.0/21 No ROA Nonecovered by 46.247.144.0/20 672 100% 66
46.247.144.0/22 No ROA Nonecovered by 46.247.144.0/20 672 100% 66
46.247.144.0/23 No ROA Nonecovered by 46.247.144.0/20 672 100% 66
149.3.160.0/23 No ROA Nonecovered by 149.3.160.0/22 672 100% 66
149.3.162.0/23 No ROA Nonecovered by 149.3.160.0/22 672 100% 66
185.245.196.0/23 No ROA Nonecovered by 185.245.196.0/22 672 100% 66
185.245.196.0/24 No ROA Nonecovered by 185.245.196.0/22 672 100% 66
193.138.168.0/23 No ROA Nonecovered by 193.138.168.0/22 672 100% 66
193.138.170.0/23 No ROA Nonecovered by 193.138.168.0/22 672 100% 66
46.247.144.0/24 No ROA Nonecovered by 46.247.144.0/20 671 100% 66
45.136.92.0/22 No ROA RIR databaseRIPE 672 100% 66
46.247.144.0/20 No ROA RIR databaseRIPE 672 100% 66
149.3.160.0/22 No ROA RIR databaseRIPE 672 100% 66
185.245.196.0/22 No ROA RIR databaseRIPE 672 100% 66
193.138.168.0/22 No ROA RIR databaseRIPE 672 100% 66
94.198.200.0/22 Valid Nonecovered by 94.198.200.0/21 672 100% 66
94.198.204.0/22 Valid Nonecovered by 94.198.200.0/21 672 100% 66
185.117.56.0/23 Valid Nonecovered by 185.117.56.0/22 672 100% 66
185.117.58.0/23 Valid Nonecovered by 185.117.56.0/22 672 100% 66
185.120.112.0/23 Valid Nonecovered by 185.120.112.0/22 672 100% 66
185.120.114.0/23 Valid Nonecovered by 185.120.112.0/22 672 100% 66
185.213.176.0/23 Valid Nonecovered by 185.213.176.0/22 672 100% 66
185.213.178.0/23 Valid Nonecovered by 185.213.176.0/22 672 100% 66
188.213.56.0/22 Valid Nonecovered by 188.213.56.0/21 672 100% 66
94.198.200.0/21 Valid RIR databaseRIPE 672 100% 66
185.117.56.0/22 Valid RIR databaseRIPE 672 100% 66
185.120.112.0/22 Valid RIR databaseRIPE 672 100% 66
185.213.176.0/22 Valid RIR databaseRIPE 672 100% 66
188.213.56.0/21 Valid RIR databaseRIPE 672 100% 66
2a03:c2c0::/32 Valid RIR databaseRIPE 421 66% 65

AS-SET

AS61205'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 40 are in fix.csv.

  • ROA: none17
  • Route object: none21
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none45.136.92.0/23No ROA covers it. Add a ROA for AS61205, maxLength 23.672 of 673
Route object: none45.136.92.0/23No route object for it. A route object for 45.136.92.0/22 with origin AS61205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61205 in the RIR database for the space.672 of 673
ROA: none45.136.94.0/23No ROA covers it. Add a ROA for AS61205, maxLength 23.672 of 673
Route object: none45.136.94.0/23No route object for it. A route object for 45.136.92.0/22 with origin AS61205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61205 in the RIR database for the space.672 of 673
ROA: none46.247.144.0/21No ROA covers it. Add a ROA for AS61205, maxLength 21.672 of 673
Route object: none46.247.144.0/21No route object for it. A route object for 46.247.144.0/20 with origin AS61205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61205 in the RIR database for the space.672 of 673
ROA: none46.247.144.0/22No ROA covers it. Add a ROA for AS61205, maxLength 22.672 of 673
Route object: none46.247.144.0/22No route object for it. A route object for 46.247.144.0/20 with origin AS61205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61205 in the RIR database for the space.672 of 673
ROA: none46.247.144.0/23No ROA covers it. Add a ROA for AS61205, maxLength 23.672 of 673
Route object: none46.247.144.0/23No route object for it. A route object for 46.247.144.0/20 with origin AS61205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61205 in the RIR database for the space.672 of 673
ROA: none149.3.160.0/23No ROA covers it. Add a ROA for AS61205, maxLength 23.672 of 673
Route object: none149.3.160.0/23No route object for it. A route object for 149.3.160.0/22 with origin AS61205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61205 in the RIR database for the space.672 of 673
ROA: none149.3.162.0/23No ROA covers it. Add a ROA for AS61205, maxLength 23.672 of 673
Route object: none149.3.162.0/23No route object for it. A route object for 149.3.160.0/22 with origin AS61205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61205 in the RIR database for the space.672 of 673
ROA: none185.245.196.0/23No ROA covers it. Add a ROA for AS61205, maxLength 23.672 of 673
Route object: none185.245.196.0/23No route object for it. A route object for 185.245.196.0/22 with origin AS61205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61205 in the RIR database for the space.672 of 673
ROA: none185.245.196.0/24No ROA covers it. Add a ROA for AS61205, maxLength 24.672 of 673
Route object: none185.245.196.0/24No route object for it. A route object for 185.245.196.0/22 with origin AS61205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61205 in the RIR database for the space.672 of 673
ROA: none193.138.168.0/23No ROA covers it. Add a ROA for AS61205, maxLength 23.672 of 673
Route object: none193.138.168.0/23No route object for it. A route object for 193.138.168.0/22 with origin AS61205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61205 in the RIR database for the space.672 of 673
ROA: none193.138.170.0/23No ROA covers it. Add a ROA for AS61205, maxLength 23.672 of 673
Route object: none193.138.170.0/23No route object for it. A route object for 193.138.168.0/22 with origin AS61205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61205 in the RIR database for the space.672 of 673
ROA: none46.247.144.0/24No ROA covers it. Add a ROA for AS61205, maxLength 24.671 of 673
Route object: none46.247.144.0/24No route object for it. A route object for 46.247.144.0/20 with origin AS61205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61205 in the RIR database for the space.671 of 673
ROA: none45.136.92.0/22No ROA covers it. Add a ROA for AS61205, maxLength 22.672 of 673
ROA: none46.247.144.0/20No ROA covers it. Add a ROA for AS61205, maxLength 20.672 of 673
ROA: none149.3.160.0/22No ROA covers it. Add a ROA for AS61205, maxLength 22.672 of 673
ROA: none185.245.196.0/22No ROA covers it. Add a ROA for AS61205, maxLength 22.672 of 673
ROA: none193.138.168.0/22No ROA covers it. Add a ROA for AS61205, maxLength 22.672 of 673
Route object: none94.198.200.0/22No route object for it. A route object for 94.198.200.0/21 with origin AS61205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61205 in the RIR database for the space.672 of 673
Route object: none94.198.204.0/22No route object for it. A route object for 94.198.200.0/21 with origin AS61205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61205 in the RIR database for the space.672 of 673
Route object: none185.117.56.0/23No route object for it. A route object for 185.117.56.0/22 with origin AS61205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61205 in the RIR database for the space.672 of 673
Route object: none185.117.58.0/23No route object for it. A route object for 185.117.56.0/22 with origin AS61205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61205 in the RIR database for the space.672 of 673
Route object: none185.120.112.0/23No route object for it. A route object for 185.120.112.0/22 with origin AS61205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61205 in the RIR database for the space.672 of 673
Route object: none185.120.114.0/23No route object for it. A route object for 185.120.112.0/22 with origin AS61205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61205 in the RIR database for the space.672 of 673
Route object: none185.213.176.0/23No route object for it. A route object for 185.213.176.0/22 with origin AS61205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61205 in the RIR database for the space.672 of 673
Route object: none185.213.178.0/23No route object for it. A route object for 185.213.176.0/22 with origin AS61205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61205 in the RIR database for the space.672 of 673
Route object: none188.213.56.0/22No route object for it. A route object for 188.213.56.0/21 with origin AS61205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61205 in the RIR database for the space.672 of 673

Route objects not announced

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

94.198.202.0/24RIPEValid
185.117.56.0/24RIPEValid

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.