bgpreport

Network · data from 2026-11-12

AS200908 intermanaged Invermae Solutions SL

Registry name: intermanaged Invermae Solutions SL, ES · not in PeeringDB

14IPv4 routes 85.7% RPKI valid · 71.4% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
2No ROA 4 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS200908, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS200908, 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.150.193.0/24 No ROA RIR databaseRIPE 672 100% 67
45.150.194.0/24 No ROA RIR databaseRIPE 672 100% 67
170.150.88.0/22 Valid None 673 100% 67
185.224.36.0/22 Valid None 673 100% 67
193.163.117.0/24 Valid None 673 100% 67
195.28.178.0/24 Valid None 673 100% 67
45.131.80.0/22 Valid RIR databaseRIPE 673 100% 67
45.137.162.0/23 Valid RIR databaseRIPE 673 100% 67
69.40.204.0/22 Valid RIR databaseRIPE 673 100% 67
103.80.84.0/23 Valid RIR databaseAPNIC 673 100% 67
185.254.156.0/24 Valid RIR databaseRIPE 673 100% 67
194.41.118.0/24 Valid RIR databaseRIPE 673 100% 67
195.28.179.0/24 Valid RIR databaseRIPE 673 100% 67
195.34.66.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

AS200908 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 12 are in fix.csv.

  • ROA: none2
  • Route object: none4
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none45.150.193.0/24No ROA covers it. Add a ROA for AS200908, maxLength 24.672 of 673
ROA: none45.150.194.0/24No ROA covers it. Add a ROA for AS200908, maxLength 24.672 of 673
Route object: none170.150.88.0/22No route object for it. Add a route object with origin AS200908 in the RIR database for the space.673 of 673
Route object: none185.224.36.0/22No route object for it. Add a route object with origin AS200908 in the RIR database for the space.673 of 673
Route object: none193.163.117.0/24No route object for it. Add a route object with origin AS200908 in the RIR database for the space.673 of 673
Route object: none195.28.178.0/24No route object for it. Add a route object with origin AS200908 in the RIR database for the space.673 of 673

Route objects not announced

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

45.144.229.0/24RIPENo ROA
45.150.192.0/22RIPENo ROA
103.80.84.0/24APNICValid
103.80.85.0/24APNICValid
185.224.36.0/24RIPEValid
188.93.117.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.