bgpreport

Network · data from 2026-11-12

AS35207 STELLAR-PCS-AS Stellar PCS GmbH

Registry name: STELLAR-PCS-AS Stellar PCS GmbH, DE · not in PeeringDB

7IPv4 routes 14.3% RPKI valid · 71.4% with a route object
2IPv6 routes 50.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
7No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS35207, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS35207, 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.92.56.0/24 No ROA Nonecovered by 80.92.56.0/22 672 100% 67
80.92.57.0/24 No ROA Nonecovered by 80.92.56.0/22 672 100% 67
80.92.48.0/21 No ROA RIR databaseRIPE 673 100% 67
80.92.61.0/24 No ROA RIR databaseRIPE 672 100% 67
80.92.62.0/24 No ROA RIR databaseRIPE 672 100% 66
80.92.63.0/24 No ROA RIR databaseRIPE 672 100% 66
2a0c:7184::/30 No ROA RIR databaseRIPE 634 100% 67
80.92.60.0/24 Valid RIR databaseRIPE 672 100% 66
2a0c:7180::/30 Valid RIR databaseRIPE 634 100% 67

AS-SET

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

  • ROA: none7
  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none80.92.56.0/24No ROA covers it. Add a ROA for AS35207, maxLength 24.672 of 673
Route object: none80.92.56.0/24No route object for it. A route object for 80.92.56.0/22 with origin AS35207 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35207 in the RIR database for the space.672 of 673
ROA: none80.92.57.0/24No ROA covers it. Add a ROA for AS35207, maxLength 24.672 of 673
Route object: none80.92.57.0/24No route object for it. A route object for 80.92.56.0/22 with origin AS35207 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35207 in the RIR database for the space.672 of 673
ROA: none80.92.48.0/21No ROA covers it. Add a ROA for AS35207, maxLength 21.673 of 673
ROA: none80.92.61.0/24No ROA covers it. Add a ROA for AS35207, maxLength 24.672 of 673
ROA: none80.92.62.0/24No ROA covers it. Add a ROA for AS35207, maxLength 24.672 of 673
ROA: none80.92.63.0/24No ROA covers it. Add a ROA for AS35207, maxLength 24.672 of 673
ROA: none2a0c:7184::/30No ROA covers it. Add a ROA for AS35207, maxLength 30.634 of 636

Route objects not announced

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

80.92.48.0/20RIPENo ROA
80.92.51.0/24RIPENo ROA
80.92.56.0/22RIPENo 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.