Network · data from 2026-11-12

AS207960 AS207960 Cyfyngedig

Registry name: AS-TRANSRIGHTS AS207960 Cyfyngedig, GB · PeeringDB

1IPv4 routes 0.0% RPKI valid · 100.0% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

1No ROA 0 with no route object for this origin

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

3Route objects not announced registered with origin AS207960, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS207960, 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.129.95.0/24	No ROA	RIR databaseRIPE	672 100%	66
2001:678:fc8::/48	Valid	RIR databaseRIPE	635 100%	69
2a0d:1a40:7900::/48	Valid	RIR databaseRIPE	635 100%	69
2a0d:1a40:7901::/48	Valid	RIR databaseRIPE	635 100%	69
2a0e:1cc1::/48	Valid	RIR databaseRIPE	635 100%	69
2a0e:1cc1:1::/48	Valid	RIR databaseRIPE	635 100%	69
2a11:f2c0::/48	Valid	RIR databaseRIPE	635 100%	69
2a11:f2c0:ff00::/48	Valid	RIR databaseRIPE	635 100%	69

AS-SET

PeeringDB's irr_as_set for AS207960: AS-207960-OUT. 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 (AS207960 isn't in the set, or no route object for AS207960 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	AS207960 in it	Not covered
AS-207960-OUT	RIPElists itself further down3 member sets in no database: AS-202076-OUT, AS-PBB, AS203105:AS-FLIMPIE	25	13	146	Yes	0

Name

Database

ASNs

Sets

Route objects

AS207960 in it

Not covered

AS-207960-OUT

RIPElists itself further down3 member sets in no database: AS-202076-OUT, AS-PBB, AS203105:AS-FLIMPIE

146

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

ROA: none1
AS-SET: missing member3
Route object: not announced3

Change	Prefix or set	Detail	Full-table peers
ROA: none	45.129.95.0/24	No ROA covers it. Add a ROA for AS207960, maxLength 24.	672 of 673
AS-SET: missing member	AS-207960-OUT	AS-207960-OUT (RIPE) lists AS-202076-OUT; no IRR database read has it.
AS-SET: missing member	AS-207960-OUT	AS-207960-OUT (RIPE) lists AS-PBB; no IRR database read has it.
AS-SET: missing member	AS-207960-OUT	AS-207960-OUT (RIPE) lists AS203105:AS-FLIMPIE; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

ROA: none

45.129.95.0/24

No ROA covers it. Add a ROA for AS207960, maxLength 24.

672 of 673

AS-SET: missing member

AS-207960-OUT

AS-207960-OUT (RIPE) lists AS-202076-OUT; no IRR database read has it.

AS-SET: missing member

AS-207960-OUT

AS-207960-OUT (RIPE) lists AS-PBB; no IRR database read has it.

AS-SET: missing member

AS-207960-OUT

AS-207960-OUT (RIPE) lists AS203105:AS-FLIMPIE; no IRR database read has it.

Route objects not announced

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


2a0d:1a40:7900::/40	RIPE	Valid
2a0d:1a40:79ff::/48	RIPE	Valid
2a0e:1cc1::/40	RIPE	Valid

2a0d:1a40:7900::/40

RIPE

Valid

2a0d:1a40:79ff::/48

RIPE

Valid

2a0e:1cc1::/40

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.