Network · data from 2026-11-12

AS219302 seally-AS SEALLY LTD

Registry name: seally-AS SEALLY LTD, GB · not in PeeringDB

8IPv4 routes 100.0% RPKI valid · 100.0% with a route object

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

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 AS219302, seen from no peer

Announced routes

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


31.77.65.0/24	Valid	RIR databaseRIPE	673 100%	67
13.143.215.0/24	Valid	RIR databaseRIPE	672 100%	67
13.143.216.0/24	Valid	RIR databaseRIPE	672 100%	67
13.143.214.0/24	Valid	RIR databaseRIPE	671 100%	68
13.143.217.0/24	Valid	RIR databaseRIPE	671 100%	67
13.143.242.0/24	Valid	RIR databaseRIPE	671 100%	67
13.143.253.0/24	Valid	RIR databaseRIPE	671 100%	67
13.143.252.0/24	Valid	RIR databaseRIPE	670 100%	67
2a0d:d940:a014::/48	Valid	RIR databaseRIPE	636 100%	67
2a0d:d940:a010::/48	Valid	RIR databaseRIPE	635 100%	69
2a0d:d940:a011::/48	Valid	RIR databaseRIPE	635 100%	67
2a0d:d940:a012::/48	Valid	RIR databaseRIPE	635 100%	67
2a0d:d940:a013::/48	Valid	RIR databaseRIPE	635 100%	67

AS-SET

AS219302 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 AS219302 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.