Network · data from 2026-11-12

AS200275 scsynergy-as

Registry name: scsynergy-as sc synergy GmbH, DE · PeeringDB

3IPv4 routes 66.7% RPKI valid · 100.0% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

2No 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 AS200275, seen from no peer

Announced routes

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


80.79.8.0/22	No ROA	RIR databaseRIPE	670 100%	66
2a14:9800::/29	No ROA	RIR databaseRIPE	632 99%	67
5.231.122.0/24	Valid	RIR databaseRIPE	673 100%	66
5.231.127.0/24	Valid	RIR databaseRIPE	673 100%	66

AS-SET

AS200275's PeeringDB record names no 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 2 are in fix.csv.

ROA: none2

Change	Prefix or set	Detail	Full-table peers
ROA: none	80.79.8.0/22	No ROA covers it. Add a ROA for AS200275, maxLength 22.	670 of 673
ROA: none	2a14:9800::/29	No ROA covers it. Add a ROA for AS200275, maxLength 29.	632 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

80.79.8.0/22

No ROA covers it. Add a ROA for AS200275, maxLength 22.

670 of 673

ROA: none

2a14:9800::/29

No ROA covers it. Add a ROA for AS200275, maxLength 29.

632 of 636

Route objects not announced

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