bgpreport

Network · data from 2026-11-12

AS209710 SNRD Networks Limited (Lumine)

Registry name: LUMINE-AS SNRD NETWORKS LIMITED, GB · PeeringDB

2IPv4 routes 50.0% RPKI valid · 100.0% with a route object
13IPv6 routes 100.0% RPKI valid · 92.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No 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 AS209710, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS209710, 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.
44.30.184.0/24 No ROA Other IRR onlyRADB 671 100% 69
2a14:7580:ff50::/48 Valid Nonecovered by 2a14:7580:ff50::/44 634 100% 69
2a14:7580:ff50::/44 Valid Other IRR onlyRADB 635 100% 69
185.238.241.0/24 Valid RIR databaseRIPE 671 100% 68
2a14:7580:ff5f::/48 Valid RIR databaseRIPE 636 100% 69
2a14:7581:9f70::/48 Valid RIR databaseRIPE 636 100% 69
2a14:7580:500::/40 Valid RIR databaseRADB, RIPE 635 100% 69
2a14:7580:540::/42 Valid RIR databaseRIPE 634 100% 69
2a14:7580:ff51::/48 Valid RIR databaseRIPE 634 100% 69
2a14:7580:ff52::/48 Valid RIR databaseRIPE 634 100% 69
2a14:7580:ff53::/48 Valid RIR databaseRIPE 634 100% 69
2a14:7580:ff54::/48 Valid RIR databaseRIPE 634 100% 69
2a14:7580:ff56::/48 Valid RIR databaseRIPE 634 100% 69
2a14:7580:ff55::/48 Valid RIR databaseRADB, RIPE 633 100% 67
2a14:7581:9f70::/44 Valid RIR databaseRIPE 627 99% 67

AS-SET

PeeringDB's irr_as_set for AS209710: AS209710:AS-SNRD-PEER. 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 (AS209710 isn't in the set, or no route object for AS209710 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 objectsAS209710 in itNot covered
AS209710:AS-SNRD-PEER RIPE 162209 Yes 0

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.

  • ROA: none1
  • Route object: none1
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none44.30.184.0/24No ROA covers it. Add a ROA for AS209710, maxLength 24.671 of 673
Route object: RIR44.30.184.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: none2a14:7580:ff50::/48No route object for it. A route object for 2a14:7580:ff50::/44 with origin AS209710 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209710 in the RIR database for the space.634 of 636
Route object: RIR2a14:7580:ff50::/44Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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