Network · data from 2026-11-12

AS205479 Luke Granger-Brown

Registry name: LGB-AS Luke Eiji Granger-Brown, GB · PeeringDB

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

7IPv6 routes 100.0% RPKI valid · 71.4% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 2 with no route object for this origin

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

2Route objects not announced registered with origin AS205479, seen from no peer

Announced routes

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


2a09:a443::/32	Valid	Nonecovered by 2a09:a440::/29	636 100%	67
2a09:a446:1337::/48	Valid	Other origin onlycovered by 2a09:a440::/29	635 100%	67
92.118.28.0/24	Valid	RIR databaseRIPE	673 100%	67
92.118.30.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
2a09:a440::/48	Valid	RIR databaseRIPE	636 100%	67
2a09:a441::/32	Valid	RIR databaseRIPE	636 100%	67
2a09:a442::/48	Valid	RIR databaseRIPE	636 100%	67
2a09:a442:1000::/48	Valid	RIR databaseRIPE	636 100%	67
2a09:a442:2000::/48	Valid	RIR databaseRIPE	636 100%	67

AS-SET

PeeringDB's irr_as_set for AS205479: AS205479: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 (AS205479 isn't in the set, or no route object for AS205479 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	AS205479 in it	Not covered
AS205479:AS-ALL	RIPE	2	1	10	Yes	0

Name

Database

ASNs

Sets

Route objects

AS205479 in it

Not covered

AS205479:AS-ALL

RIPE

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

Route object: none2
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
Route object: none	2a09:a443::/32	No route object for it. A route object for 2a09:a440::/29 with origin AS205479 covers it (filters allowing more-specifics accept it). Add a route object with origin AS205479 in the RIR database for the space.	636 of 636
Route object: none	2a09:a446:1337::/48	Route objects for it name AS26073. A route object for 2a09:a440::/29 with origin AS205479 covers it (filters allowing more-specifics accept it). Add a route object with origin AS205479 in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2a09:a443::/32

No route object for it. A route object for 2a09:a440::/29 with origin AS205479 covers it (filters allowing more-specifics accept it). Add a route object with origin AS205479 in the RIR database for the space.

636 of 636

Route object: none

2a09:a446:1337::/48

Route objects for it name AS26073. A route object for 2a09:a440::/29 with origin AS205479 covers it (filters allowing more-specifics accept it). Add a route object with origin AS205479 in the RIR database for the space.

635 of 636

Route objects not announced

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


92.118.31.0/24	RIPE	Valid
2a09:a440::/29	RIPE	Valid

92.118.31.0/24

RIPE

Valid

2a09:a440::/29

RIPE

Valid

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.