bgpreport

Network · data from 2026-11-12

AS48955 IRM-AS Internet Resources Management SRL

Registry name: IRM-AS Internet Resources Management SRL, RO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS48955, 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.13.176.0/23 Valid RIR databaseRIPE 672 100% 66
45.93.128.0/22 Valid RIR databaseRIPE 672 100% 66
45.95.220.0/22 Valid RIR databaseRIPE 672 100% 66
45.131.104.0/23 Valid RIR databaseRIPE 672 100% 66
80.96.18.0/23 Valid RIR databaseRIPE 672 100% 66
80.96.70.0/23 Valid RIR databaseRIPE 672 100% 66
80.96.100.0/23 Valid RIR databaseRIPE 672 100% 66
81.180.108.0/23 Valid RIR databaseRIPE 672 100% 66
81.181.162.0/23 Valid RIR databaseRIPE 672 100% 66
84.54.34.0/24 Valid RIR databaseRIPE 672 100% 66
85.122.60.0/23 Valid RIR databaseRIPE 672 100% 66
86.107.58.0/23 Valid RIR databaseRIPE 672 100% 66
89.35.80.0/23 Valid RIR databaseRIPE 672 100% 66
89.40.222.0/23 Valid RIR databaseRIPE 672 100% 66
89.45.66.0/24 Valid RIR databaseRIPE 672 100% 66
89.45.124.0/23 Valid RIR databaseRIPE 672 100% 66
91.193.24.0/24 Valid RIR databaseRIPE 672 100% 66
91.196.154.0/24 Valid RIR databaseRIPE 672 100% 66
91.211.87.0/24 Valid RIR databaseRIPE 672 100% 66
91.217.226.0/24 Valid RIR databaseRIPE 672 100% 66
91.231.183.0/24 Valid RIR databaseRIPE 672 100% 66
91.235.207.0/24 Valid RIR databaseRIPE 672 100% 66
92.42.0.0/24 Valid RIR databaseRIPE 672 100% 66
93.113.205.0/24 Valid RIR databaseRIPE 672 100% 66
94.154.122.0/24 Valid RIR databaseRIPE 672 100% 66
185.36.230.0/24 Valid RIR databaseRIPE 672 100% 66
185.51.122.0/24 Valid RIR databaseRIPE 672 100% 66
185.98.158.0/24 Valid RIR databaseRIPE 672 100% 66
185.140.251.0/24 Valid RIR databaseRIPE 672 100% 66
188.212.5.0/24 Valid RIR databaseRIPE 672 100% 66
188.213.1.0/24 Valid RIR databaseRIPE 672 100% 66
188.214.227.0/24 Valid RIR databaseRIPE 672 100% 66
193.33.105.0/24 Valid RIR databaseRIPE 672 100% 66
193.176.99.0/24 Valid RIR databaseRIPE 672 100% 66
193.239.176.0/24 Valid RIR databaseRIPE 672 100% 66
194.106.206.0/24 Valid RIR databaseRIPE 672 100% 66
194.169.202.0/24 Valid RIR databaseRIPE 672 100% 66
195.35.100.0/24 Valid RIR databaseRIPE 672 100% 66
195.60.238.0/24 Valid RIR databaseRIPE 672 100% 66
195.189.156.0/24 Valid RIR databaseRIPE 672 100% 66
217.156.32.0/24 Valid RIR databaseRIPE 672 100% 66
2.59.12.0/24 Valid RIR databaseRIPE 671 100% 66
2.59.15.0/24 Valid RIR databaseRIPE 671 100% 66
45.13.178.0/24 Valid RIR databaseRIPE 671 100% 66

AS-SET

AS48955 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS48955 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.