bgpreport

Network · data from 2026-11-12

AS198022 STARFACE STARFACE GmbH

Registry name: STARFACE STARFACE GmbH, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS198022, 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.
45.143.184.0/22 Valid Other origin only 673 100% 66
185.211.223.0/24 Valid Nonecovered by 185.211.220.0/22 673 100% 66
212.79.208.0/22 Valid Nonecovered by 212.79.208.0/21 673 100% 66
37.120.180.0/23 Valid RIR databaseRIPE 673 100% 66
185.145.168.0/22 Valid RIR databaseRIPE 673 100% 66
185.211.220.0/23 Valid RIR databaseRIPE 673 100% 66
185.211.222.0/24 Valid RIR databaseRIPE 673 100% 66
194.36.60.0/22 Valid RIR databaseRIPE 673 100% 66
212.79.200.0/21 Valid RIR databaseRIPE 673 100% 66
2a03:aae0:a0::/48 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS198022 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 5 are in fix.csv.

  • Route object: none3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none45.143.184.0/22Route objects for it name AS197540. Add a route object with origin AS198022 in the RIR database for the space.673 of 673
Route object: none185.211.223.0/24No route object for it. A route object for 185.211.220.0/22 with origin AS198022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198022 in the RIR database for the space.673 of 673
Route object: none212.79.208.0/22No route object for it. A route object for 212.79.208.0/21 with origin AS198022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198022 in the RIR database for the space.673 of 673

Route objects not announced

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

185.211.220.0/22RIPENo ROA
212.79.208.0/21RIPENo 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.