| # | Date | Res | Prefix(es) | From | To | Units | Nets | Tags | |
|---|---|---|---|---|---|---|---|---|---|
| 1 | 2019-06-25 | IPV4 | 141.105.64.0/21 | RIPEMir Telematiki Ltd | → | RIPELLC "Server v arendy" | 2 048 addr | 1 | PA |
| 2 | 2019-06-25 | IPV4 | 158.255.0.0/21 | RIPEMir Telematiki Ltd | → | RIPELLC "Server v arendy" | 2 048 addr | 1 | PA |
| 3 | 2019-06-25 | IPV4 | 185.70.104.0/22 | RIPEMir Telematiki Ltd | → | RIPELLC "Server v arendy" | 1 024 addr | 1 | PA |
| 4 | 2019-06-25 | IPV4 | 31.192.104.0/21 | RIPEMir Telematiki Ltd | → | RIPELLC "Server v arendy" | 2 048 addr | 1 | PA |
| 5 | 2019-06-25 | IPV4 | 91.210.104.0/22 | RIPEMir Telematiki Ltd | → | RIPELLC "Server v arendy" | 1 024 addr | 1 | PI |
| 6 | 2019-06-25 | IPV4 | 91.218.112.0/22 | RIPEMir Telematiki Ltd | → | RIPELLC "Server v arendy" | 1 024 addr | 1 | PI |
| 7 | 2019-06-25 | IPV4 | 91.218.244.0/22 | RIPEMir Telematiki Ltd | → | RIPELLC "Server v arendy" | 1 024 addr | 1 | PI |
| 8 | 2019-06-25 | IPV4 | 91.237.249.0/24 | RIPEMir Telematiki Ltd | → | RIPELLC "Server v arendy" | 256 addr | 1 | PI |
| 9 | 2019-06-25 | IPV6 | 2a05:b80::/29 | RIPEMir Telematiki Ltd | → | RIPELLC "Server v arendy" | 524 288 /48 | 1 | PA |
| 10 | 2019-06-25 | ASN | AS48211 | RIPEMir Telematiki Ltd | → | RIPELLC "Server v arendy" | 1 ASN | 1 | PI |
| 11 | 2019-06-25 | ASN | AS49335 | RIPEMir Telematiki Ltd | → | RIPELLC "Server v arendy" | 1 ASN | 1 | PI |
| 12 | 2019-07-05 | IPV4 | 46.17.96.0/21 | RIPEMir Telematiki Ltd | → | RIPE HOSTKEY B.V. |
2 048 addr | 1 | PA |
| 13 | 2019-07-05 | IPV4 | 193.109.68.0/23 | RIPEMir Telematiki Ltd | → | RIPEHOSTKEY B.V. |
512 addr | 1 | PI |
| 14 | 2019-07-05 | IPV4 | 195.162.68.0/23 | RIPEMir Telematiki Ltd | → | RIPEHOSTKEY B.V. |
512 addr | 1 | PI |