bgpreport

Network · data from 2026-11-12

AS13110 INEA

Registry name: INEA-AS INEA sp. z o.o., PL · PeeringDB

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

Announced routes

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

62.21.52.197/32 Invalid: maxLength Nonecovered by 62.21.0.0/17 2 0%low visibility 6
77.65.19.242/32 Invalid: maxLength Nonecovered by 77.65.0.0/17 2 0%low visibility 6
80.87.36.181/32 Invalid: maxLength Nonecovered by 80.87.32.0/20 2 0%low visibility 6
192.162.176.38/32 No ROA Nonecovered by 192.162.176.0/22 2 0%low visibility 6
192.162.176.151/32 No ROA Nonecovered by 192.162.176.0/22 2 0%low visibility 6
91.230.122.0/24 No ROA RIR databaseRIPE 673 100% 66
194.50.155.0/24 No ROA RIR databaseRIPE 673 100% 66
2a12:2b40::/29 No ROA RIR databaseRIPE 632 99% 67
46.228.80.0/20 Valid RIR databaseRIPE 673 100% 66
46.238.64.0/18 Valid RIR databaseRIPE 673 100% 66
62.21.0.0/17 Valid RIR databaseRIPE 673 100% 66
77.65.0.0/17 Valid RIR databaseRIPE 673 100% 66
80.87.32.0/20 Valid RIR databaseRIPE 673 100% 66
85.221.128.0/17 Valid RIR databaseRIPE 673 100% 66
88.151.136.0/21 Valid RIR databaseRIPE 673 100% 66
91.202.102.0/24 Valid RIR databaseRIPE 673 100% 66
94.127.104.0/21 Valid RIR databaseRIPE 673 100% 66
109.173.128.0/17 Valid RIR databaseRIPE 673 100% 66
151.249.80.0/21 Valid RIR databaseRIPE 673 100% 66
185.14.72.0/22 Valid RIR databaseRIPE 673 100% 66
185.44.172.0/22 Valid RIR databaseRIPE 673 100% 66
193.169.208.0/24 Valid RIR databaseRIPE 673 100% 66
194.114.148.0/22 Valid RIR databaseRIPE 673 100% 66
194.116.138.0/23 Valid RIR databaseRIPE 673 100% 66
194.150.206.0/23 Valid RIR databaseRIPE 673 100% 66
195.160.180.0/23 Valid RIR databaseRIPE 673 100% 66
217.113.128.0/20 Valid RIR databaseRIPE 673 100% 66
2001:4020::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS13110: RIPE::AS-ICPNET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS13110 isn't in the set, or no route object for AS13110 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS13110 in itNot covered
RIPE::AS-ICPNET RIPE1 member set in no database: AS57807:AS-CUSTOMERS 1019593 Yes 5

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

  • ROA: maxLength3
  • ROA: none5
  • Route object: none5
  • AS-SET: missing member1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: maxLength62.21.52.197/32ROA 62.21.0.0/17 AS13110 has maxLength 17; the route is a /32. Raise the maxLength, or add a ROA for 62.21.52.197/32.2 of 673
Route object: none62.21.52.197/32No route object for it. A route object for 62.21.0.0/17 with origin AS13110 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS13110 in the RIR database for the space.2 of 673
ROA: maxLength77.65.19.242/32ROA 77.65.0.0/17 AS13110 has maxLength 17; the route is a /32. Raise the maxLength, or add a ROA for 77.65.19.242/32.2 of 673
Route object: none77.65.19.242/32No route object for it. A route object for 77.65.0.0/17 with origin AS13110 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS13110 in the RIR database for the space.2 of 673
ROA: maxLength80.87.36.181/32ROA 80.87.32.0/20 AS13110 has maxLength 20; the route is a /32. Raise the maxLength, or add a ROA for 80.87.36.181/32.2 of 673
Route object: none80.87.36.181/32No route object for it. A route object for 80.87.32.0/20 with origin AS13110 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS13110 in the RIR database for the space.2 of 673
ROA: none192.162.176.38/32No ROA covers it. Add a ROA for AS13110, maxLength 32.2 of 673
Route object: none192.162.176.38/32No route object for it. A route object for 192.162.176.0/22 with origin AS13110 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS13110 in the RIR database for the space.2 of 673
ROA: none192.162.176.151/32No ROA covers it. Add a ROA for AS13110, maxLength 32.2 of 673
Route object: none192.162.176.151/32No route object for it. A route object for 192.162.176.0/22 with origin AS13110 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS13110 in the RIR database for the space.2 of 673
ROA: none91.230.122.0/24No ROA covers it. Add a ROA for AS13110, maxLength 24.673 of 673
ROA: none194.50.155.0/24No ROA covers it. Add a ROA for AS13110, maxLength 24.673 of 673
ROA: none2a12:2b40::/29No ROA covers it. Add a ROA for AS13110, maxLength 29.632 of 636
AS-SET: missing memberRIPE::AS-ICPNETAS-ICPNET (RIPE) lists AS57807:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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

91.223.196.0/24RIPENo ROA
192.162.176.0/22RIPENo ROA
2a02:78::/32RIPEInvalid: origin

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.