bgpreport

Network · data from 2026-11-12

AS203206 NetFlash

Registry name: NetFlash-CY-ISP A.C. NetFlash Technologies Ltd, CY · PeeringDB

8IPv4 routes 100.0% RPKI valid · 100.0% with a route object
9IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No 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 AS203206, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS203206, 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.
38.19.168.0/22 Valid RIR databaseARIN 673 100% 67
62.228.231.0/24 Valid RIR databaseRIPE 673 100% 67
185.78.129.0/24 Valid RIR databaseRIPE 673 100% 67
185.204.101.0/24 Valid RIR databaseRIPE 673 100% 67
213.169.150.0/24 Valid RIR databaseRIPE 673 100% 67
213.169.152.0/24 Valid RIR databaseRIPE 673 100% 67
213.169.153.0/24 Valid RIR databaseRIPE 673 100% 67
213.169.155.0/24 Valid RIR databaseRIPE 673 100% 67
2a10:8400::/32 Valid RIR databaseRIPE 635 100% 67
2a10:8401::/32 Valid RIR databaseRIPE 635 100% 67
2a10:8402::/32 Valid RIR databaseRIPE 635 100% 67
2a10:8403::/32 Valid RIR databaseRIPE 635 100% 67
2a10:8404::/32 Valid RIR databaseRIPE 635 100% 67
2a10:8405::/32 Valid RIR databaseRIPE 635 100% 67
2a10:8406::/32 Valid RIR databaseRIPE 635 100% 67
2a10:8407::/32 Valid RIR databaseRIPE 635 100% 67
2a10:8400::/29 Valid RIR databaseRIPE 634 100% 67

AS-SET

AS203206's PeeringDB record names no AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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