Network · data from 2026-11-12

AS56410 Host Ireland

Registry name: HOST-IRELAND-AS Leeson Telecom Holdings Ltd, IE · PeeringDB

22IPv4 routes 100.0% RPKI valid · 95.5% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS56410, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS56410, 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.158.112.0/24	Valid	Nonecovered by 45.158.112.0/22	671 100%	66
5.149.168.0/21	Valid	RIR databaseRIPE	673 100%	67
45.137.184.0/22	Valid	RIR databaseRIPE	673 100%	67
45.158.112.0/22	Valid	RIR databaseRIPE	673 100%	67
62.146.164.0/22	Valid	RIR databaseRIPE	673 100%	67
80.190.0.0/22	Valid	RIR databaseRIPE	673 100%	67
81.173.12.0/22	Valid	RIR databaseRIPE	673 100%	67
91.216.236.0/24	Valid	RIR databaseRIPE	673 100%	67
91.216.241.0/24	Valid	RIR databaseRIPE	673 100%	67
93.119.24.0/22	Valid	RIR databaseRIPE	673 100%	67
144.2.240.0/21	Valid	RIR databaseRIPE	673 100%	67
159.253.224.0/22	Valid	RIR databaseRIPE	673 100%	67
185.32.152.0/22	Valid	RIR databaseRIPE	673 100%	67
185.57.100.0/22	Valid	RIR databaseRIPE	673 100%	67
185.122.132.0/22	Valid	RIR databaseRIPE	673 100%	67
185.156.196.0/22	Valid	RIR databaseRIPE	673 100%	67
193.120.22.0/24	Valid	RIR databaseRIPE	673 100%	67
193.120.40.0/23	Valid	RIR databaseRIPE	673 100%	67
193.120.55.0/24	Valid	RIR databaseRIPE	673 100%	67
193.120.164.0/23	Valid	RIR databaseRIPE	673 100%	67
217.115.121.0/24	Valid	RIR databaseRIPE	673 100%	67
217.115.124.0/24	Valid	RIR databaseRIPE	673 100%	67
2a04:b00::/29	Valid	RIR databaseRIPE	634 100%	68

AS-SET

PeeringDB's irr_as_set for AS56410: AS56410:AS-ALL. 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 (AS56410 isn't in the set, or no route object for AS56410 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.

Name	Database	ASNs	Sets	Route objects	AS56410 in it	Not covered
AS56410:AS-ALL	RIPE	11	1	2,804	Yes	0

Name

Database

ASNs

Sets

Route objects

AS56410 in it

Not covered

AS56410:AS-ALL

RIPE

2,804

Yes

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

Route object: none1

Change	Prefix or set	Detail	Full-table peers
Route object: none	45.158.112.0/24	No route object for it. A route object for 45.158.112.0/22 with origin AS56410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56410 in the RIR database for the space.	671 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

45.158.112.0/24

No route object for it. A route object for 45.158.112.0/22 with origin AS56410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56410 in the RIR database for the space.

671 of 673

Route objects not announced

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