Network · data from 2026-11-12

AS268973

Not in the RIR AS name list · not in PeeringDB

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

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

2RPKI invalid 2 origin · 0 maxLength

1No ROA 2 with no route object for this origin

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268973, 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.176.253.0/24	Invalid: origin	Other origin only	3 0%low visibility	3
45.176.255.0/24	Invalid: origin	Other origin only	3 0%low visibility	3
2804:5d74::/32	No ROA	Other IRR onlyRADB, TC	1 0%low visibility	1

45.176.253.0/24

Invalid: origin

Other origin only

3 0%low visibility

45.176.255.0/24

Invalid: origin

Other origin only

3 0%low visibility

2804:5d74::/32

No ROA

Other IRR onlyRADB, TC

1 0%low visibility

AS-SET

AS268973 isn't in PeeringDB, where networks name their AS-SET.

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

ROA: origin2
ROA: none1
Route object: none2
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: origin	45.176.253.0/24	ROAs covering it name AS263980, not AS268973. If AS268973 should announce it, add a ROA for AS268973.	3 of 673
Route object: none	45.176.253.0/24	Route objects for it name AS263980. Add a route object with origin AS268973 in the RIR database for the space.	3 of 673
ROA: origin	45.176.255.0/24	ROAs covering it name AS263980, not AS268973. If AS268973 should announce it, add a ROA for AS268973.	3 of 673
Route object: none	45.176.255.0/24	Route objects for it name AS263980. Add a route object with origin AS268973 in the RIR database for the space.	3 of 673
ROA: none	2804:5d74::/32	No ROA covers it. Add a ROA for AS268973, maxLength 32.	1 of 636
Route object: RIR	2804:5d74::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	1 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: origin

45.176.253.0/24

ROAs covering it name AS263980, not AS268973. If AS268973 should announce it, add a ROA for AS268973.

3 of 673

Route object: none

45.176.253.0/24

Route objects for it name AS263980. Add a route object with origin AS268973 in the RIR database for the space.

3 of 673

ROA: origin

45.176.255.0/24

ROAs covering it name AS263980, not AS268973. If AS268973 should announce it, add a ROA for AS268973.

3 of 673

Route object: none

45.176.255.0/24

Route objects for it name AS263980. Add a route object with origin AS268973 in the RIR database for the space.

3 of 673

ROA: none

2804:5d74::/32

No ROA covers it. Add a ROA for AS268973, maxLength 32.

1 of 636

Route object: RIR

2804:5d74::/32

Route object only in RADB, TC. Add it in the RIR database for the space.

1 of 636

Route objects not announced

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