bgpreport

Network · data from 2026-11-12

AS60016 ASFS3 Fiberstream 87 AG

Registry name: ASFS3 Fiberstream 87 AG, CH · not in PeeringDB

13IPv4 routes 7.7% RPKI valid · 84.6% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
12No ROA 2 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS60016, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS60016, 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.
185.62.81.2/32 No ROA Nonecovered by 185.62.80.0/22 2 0%low visibility 2
185.62.81.3/32 No ROA Nonecovered by 185.62.80.0/22 2 0%low visibility 2
93.188.78.0/24 No ROA RIR databaseRIPE 671 100% 67
185.62.80.0/22 No ROA RIR databaseRIPE 668 99% 67
185.169.240.0/22 No ROA RIR databaseRIPE 668 99% 67
185.199.176.0/22 No ROA RIR databaseRIPE 668 99% 67
185.227.56.0/22 No ROA RIR databaseRIPE 668 99% 67
194.5.220.0/22 No ROA RIR databaseRIPE 668 99% 67
213.173.40.0/23 No ROA RIR databaseRIPE 668 99% 67
213.173.42.0/23 No ROA RIR databaseRIPE 668 99% 67
213.173.44.0/23 No ROA RIR databaseRIPE 668 99% 67
213.173.46.0/24 No ROA RIR databaseRIPE 668 99% 67
185.244.252.0/22 Valid RIR databaseRIPE 668 99% 67

AS-SET

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

  • ROA: none12
  • Route object: none2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none185.62.81.2/32No ROA covers it. Add a ROA for AS60016, maxLength 32.2 of 673
Route object: none185.62.81.2/32No route object for it. A route object for 185.62.80.0/22 with origin AS60016 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS60016 in the RIR database for the space.2 of 673
ROA: none185.62.81.3/32No ROA covers it. Add a ROA for AS60016, maxLength 32.2 of 673
Route object: none185.62.81.3/32No route object for it. A route object for 185.62.80.0/22 with origin AS60016 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS60016 in the RIR database for the space.2 of 673
ROA: none93.188.78.0/24No ROA covers it. Add a ROA for AS60016, maxLength 24.671 of 673
ROA: none185.62.80.0/22No ROA covers it. Add a ROA for AS60016, maxLength 22.668 of 673
ROA: none185.169.240.0/22No ROA covers it. Add a ROA for AS60016, maxLength 22.668 of 673
ROA: none185.199.176.0/22No ROA covers it. Add a ROA for AS60016, maxLength 22.668 of 673
ROA: none185.227.56.0/22No ROA covers it. Add a ROA for AS60016, maxLength 22.668 of 673
ROA: none194.5.220.0/22No ROA covers it. Add a ROA for AS60016, maxLength 22.668 of 673
ROA: none213.173.40.0/23No ROA covers it. Add a ROA for AS60016, maxLength 23.668 of 673
ROA: none213.173.42.0/23No ROA covers it. Add a ROA for AS60016, maxLength 23.668 of 673
ROA: none213.173.44.0/23No ROA covers it. Add a ROA for AS60016, maxLength 23.668 of 673
ROA: none213.173.46.0/24No ROA covers it. Add a ROA for AS60016, maxLength 24.668 of 673

Route objects not announced

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

213.173.44.0/22RIPENo ROA
213.173.47.0/24RIPENo ROA
2a04:f000::/29RIPENo ROA
2a0a:9340::/48RIPENo ROA
2a0d:7b40::/29RIPENo ROA

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.