bgpreport

Network · data from 2026-11-12

AS35007 Miconet

Registry name: MICONET-AS Miconet Sp. z o.o., PL · PeeringDB

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

Announced routes

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

2a00:1ea0::/47 No ROA None 634 100% 67
2.58.218.0/23 No ROA RIR databaseRIPE 671 100% 68
5.252.213.0/24 No ROA RIR databaseRIPE 671 100% 68
81.30.128.0/23 No ROA RIR databaseRIPE 671 100% 68
185.253.232.0/24 No ROA RIR databaseRIPE 671 100% 68
193.22.22.0/24 No ROA RIR databaseRIPE 671 100% 68
193.56.208.0/24 No ROA RIR databaseRIPE 671 100% 68
193.56.224.0/24 No ROA RIR databaseRIPE 671 100% 68
193.163.202.0/24 No ROA RIR databaseRIPE 671 100% 68
195.22.118.0/24 No ROA RIR databaseRIPE 671 100% 68
2.58.218.0/24 No ROA RIR databaseRIPE 78 12% 32
2.58.219.0/24 No ROA RIR databaseRIPE 78 12% 32
81.30.128.0/24 No ROA RIR databaseRIPE 78 12% 32
81.30.129.0/24 No ROA RIR databaseRIPE 78 12% 32
81.30.138.0/23 Valid RIR databaseRIPE 671 100% 68
83.168.118.0/24 Valid RIR databaseRIPE 671 100% 68
83.168.119.0/24 Valid RIR databaseRIPE 671 100% 68
91.201.120.0/22 Valid RIR databaseRIPE 671 100% 68
185.6.112.0/22 Valid RIR databaseRIPE 671 100% 68
185.221.80.0/22 Valid RIR databaseRIPE 671 100% 68
195.160.184.0/23 Valid RIR databaseRIPE 671 100% 68
195.225.36.0/23 Valid RIR databaseRIPE 671 100% 68
93.157.112.0/21 Valid RIR databaseRIPE 669 99% 68
81.30.138.0/24 Valid RIR databaseRIPE 78 12% 32
81.30.139.0/24 Valid RIR databaseRIPE 78 12% 32
91.201.120.0/24 Valid RIR databaseRIPE 78 12% 32
91.201.121.0/24 Valid RIR databaseRIPE 78 12% 32
91.201.122.0/24 Valid RIR databaseRIPE 78 12% 32
91.201.123.0/24 Valid RIR databaseRIPE 78 12% 32
93.157.112.0/24 Valid RIR databaseRIPE 78 12% 32
93.157.113.0/24 Valid RIR databaseRIPE 78 12% 32
93.157.114.0/24 Valid RIR databaseRIPE 78 12% 32
93.157.115.0/24 Valid RIR databaseRIPE 78 12% 32
93.157.116.0/24 Valid RIR databaseRIPE 78 12% 32
93.157.117.0/24 Valid RIR databaseRIPE 78 12% 32
93.157.118.0/24 Valid RIR databaseRIPE 78 12% 32
93.157.119.0/24 Valid RIR databaseRIPE 78 12% 32
185.6.112.0/24 Valid RIR databaseRIPE 78 12% 32
185.6.113.0/24 Valid RIR databaseRIPE 78 12% 32
185.6.114.0/24 Valid RIR databaseRIPE 78 12% 32
185.6.115.0/24 Valid RIR databaseRIPE 78 12% 32
185.221.80.0/24 Valid RIR databaseRIPE 78 12% 32
185.221.81.0/24 Valid RIR databaseRIPE 78 12% 32
185.221.82.0/24 Valid RIR databaseRIPE 78 12% 32
185.221.83.0/24 Valid RIR databaseRIPE 78 12% 32
195.160.184.0/24 Valid RIR databaseRIPE 78 12% 32
195.160.185.0/24 Valid RIR databaseRIPE 78 12% 32
195.225.36.0/24 Valid RIR databaseRIPE 78 12% 32
195.225.37.0/24 Valid RIR databaseRIPE 78 12% 32

AS-SET

AS35007'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 18 are in fix.csv.

  • ROA: none14
  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2a00:1ea0::/47No ROA covers it. Add a ROA for AS35007, maxLength 47.634 of 636
Route object: none2a00:1ea0::/47No route object for it. Add a route object with origin AS35007 in the RIR database for the space.634 of 636
ROA: none2.58.218.0/23No ROA covers it. Add a ROA for AS35007, maxLength 23.671 of 673
ROA: none5.252.213.0/24No ROA covers it. Add a ROA for AS35007, maxLength 24.671 of 673
ROA: none81.30.128.0/23No ROA covers it. Add a ROA for AS35007, maxLength 23.671 of 673
ROA: none185.253.232.0/24No ROA covers it. Add a ROA for AS35007, maxLength 24.671 of 673
ROA: none193.22.22.0/24No ROA covers it. Add a ROA for AS35007, maxLength 24.671 of 673
ROA: none193.56.208.0/24No ROA covers it. Add a ROA for AS35007, maxLength 24.671 of 673
ROA: none193.56.224.0/24No ROA covers it. Add a ROA for AS35007, maxLength 24.671 of 673
ROA: none193.163.202.0/24No ROA covers it. Add a ROA for AS35007, maxLength 24.671 of 673
ROA: none195.22.118.0/24No ROA covers it. Add a ROA for AS35007, maxLength 24.671 of 673
ROA: none2.58.218.0/24No ROA covers it. Add a ROA for AS35007, maxLength 24.78 of 673
ROA: none2.58.219.0/24No ROA covers it. Add a ROA for AS35007, maxLength 24.78 of 673
ROA: none81.30.128.0/24No ROA covers it. Add a ROA for AS35007, maxLength 24.78 of 673
ROA: none81.30.129.0/24No ROA covers it. Add a ROA for AS35007, maxLength 24.78 of 673

Route objects not announced

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

2a00:1ea0::/48RIPENo ROA
2a00:1ea0:1::/48RIPENo ROA
2a10:f781:10:14f3::/64RIPENo 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.