Network · data from 2026-11-12
AS200664 PF-FTNET P/F Net
Registry name: PF-FTNET P/F Net, FO · not in PeeringDB
12IPv4 routes
0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
12RPKI invalid
12 origin · 0 maxLength
0No ROA
12 with no route object for this origin
12Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS200664, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS200664, 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.77.138.0/24 | Invalid: origin | None | 1 0%low visibility |
| 80.77.142.0/24 | Invalid: origin | None | 1 0%low visibility |
| 80.77.143.0/24 | Invalid: origin | None | 1 0%low visibility |
| 81.25.178.0/24 | Invalid: origin | None | 1 0%low visibility |
| 81.25.179.0/24 | Invalid: origin | None | 1 0%low visibility |
| 81.25.180.0/24 | Invalid: origin | None | 1 0%low visibility |
| 81.25.181.0/24 | Invalid: origin | None | 1 0%low visibility |
| 81.25.189.0/24 | Invalid: origin | None | 1 0%low visibility |
| 185.88.228.0/24 | Invalid: origin | None | 1 0%low visibility |
| 185.88.229.0/24 | Invalid: origin | None | 1 0%low visibility |
| 185.88.230.0/24 | Invalid: origin | None | 1 0%low visibility |
| 185.88.231.0/24 | Invalid: origin | None | 1 0%low visibility |
AS-SET
AS200664 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 24 are in fix.csv.
- ROA: origin12
- Route object: none12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 80.77.138.0/24 | ROAs covering it name AS20963, not AS200664. If AS200664 should announce it, add a ROA for AS200664. |
| Route object: none | 80.77.138.0/24 | No route object for it. Add a route object with origin AS200664 in the RIR database for the space. |
| ROA: origin | 80.77.142.0/24 | ROAs covering it name AS20963, not AS200664. If AS200664 should announce it, add a ROA for AS200664. |
| Route object: none | 80.77.142.0/24 | No route object for it. Add a route object with origin AS200664 in the RIR database for the space. |
| ROA: origin | 80.77.143.0/24 | ROAs covering it name AS20963, not AS200664. If AS200664 should announce it, add a ROA for AS200664. |
| Route object: none | 80.77.143.0/24 | No route object for it. Add a route object with origin AS200664 in the RIR database for the space. |
| ROA: origin | 81.25.178.0/24 | ROAs covering it name AS20963, not AS200664. If AS200664 should announce it, add a ROA for AS200664. |
| Route object: none | 81.25.178.0/24 | No route object for it. Add a route object with origin AS200664 in the RIR database for the space. |
| ROA: origin | 81.25.179.0/24 | ROAs covering it name AS20963, not AS200664. If AS200664 should announce it, add a ROA for AS200664. |
| Route object: none | 81.25.179.0/24 | No route object for it. Add a route object with origin AS200664 in the RIR database for the space. |
| ROA: origin | 81.25.180.0/24 | ROAs covering it name AS20963, not AS200664. If AS200664 should announce it, add a ROA for AS200664. |
| Route object: none | 81.25.180.0/24 | No route object for it. Add a route object with origin AS200664 in the RIR database for the space. |
| ROA: origin | 81.25.181.0/24 | ROAs covering it name AS20963, not AS200664. If AS200664 should announce it, add a ROA for AS200664. |
| Route object: none | 81.25.181.0/24 | No route object for it. Add a route object with origin AS200664 in the RIR database for the space. |
| ROA: origin | 81.25.189.0/24 | ROAs covering it name AS20963, not AS200664. If AS200664 should announce it, add a ROA for AS200664. |
| Route object: none | 81.25.189.0/24 | No route object for it. Add a route object with origin AS200664 in the RIR database for the space. |
| ROA: origin | 185.88.228.0/24 | ROAs covering it name AS20963, not AS200664. If AS200664 should announce it, add a ROA for AS200664. |
| Route object: none | 185.88.228.0/24 | No route object for it. Add a route object with origin AS200664 in the RIR database for the space. |
| ROA: origin | 185.88.229.0/24 | ROAs covering it name AS20963, not AS200664. If AS200664 should announce it, add a ROA for AS200664. |
| Route object: none | 185.88.229.0/24 | No route object for it. Add a route object with origin AS200664 in the RIR database for the space. |
| ROA: origin | 185.88.230.0/24 | ROAs covering it name AS20963, not AS200664. If AS200664 should announce it, add a ROA for AS200664. |
| Route object: none | 185.88.230.0/24 | No route object for it. Add a route object with origin AS200664 in the RIR database for the space. |
| ROA: origin | 185.88.231.0/24 | ROAs covering it name AS20963, not AS200664. If AS200664 should announce it, add a ROA for AS200664. |
| Route object: none | 185.88.231.0/24 | No route object for it. Add a route object with origin AS200664 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS200664 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.