bgpreport

Network · data from 2026-11-12

AS198571 PlainProxies 3xK Tech GmbH

Registry name: PlainProxies 3xK Tech GmbH, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS198571, 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.

2a07:db80::/32 Invalid: origin None 16 3%low visibility 13
2a0c:9240::/29 Invalid: origin Other origin only 2 0%low visibility 2
2a0c:580::/29 Invalid: origin Other origin only 1 0%low visibility 1
2a0c:581::/32 Invalid: origin None 1 0%low visibility 1
2a0c:582::/32 Invalid: origin None 1 0%low visibility 1
2a0c:583::/32 Invalid: origin None 1 0%low visibility 1
2a0d:c980::/29 Invalid: origin Other origin only 1 0%low visibility 1
2a13:3f81::/32 Valid RIR databaseRIPE 629 99% 69
2a13:3f82::/32 Valid RIR databaseRIPE 628 99% 67

AS-SET

AS198571 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 21 are in fix.csv.

  • ROA: origin7
  • Route object: none7
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: origin2a07:db80::/32ROAs covering it name AS200373, not AS198571. If AS198571 should announce it, add a ROA for AS198571.16 of 636
Route object: none2a07:db80::/32No route object for it. Add a route object with origin AS198571 in the RIR database for the space.16 of 636
ROA: origin2a0c:9240::/29ROAs covering it name AS60781, not AS198571. If AS198571 should announce it, add a ROA for AS198571.2 of 636
Route object: none2a0c:9240::/29Route objects for it name AS60781. Add a route object with origin AS198571 in the RIR database for the space.2 of 636
ROA: origin2a0c:580::/29ROAs covering it name AS206119, not AS198571. If AS198571 should announce it, add a ROA for AS198571.1 of 636
Route object: none2a0c:580::/29Route objects for it name AS206119. Add a route object with origin AS198571 in the RIR database for the space.1 of 636
ROA: origin2a0c:581::/32ROAs covering it name AS206119, not AS198571. If AS198571 should announce it, add a ROA for AS198571.1 of 636
Route object: none2a0c:581::/32No route object for it. Add a route object with origin AS198571 in the RIR database for the space.1 of 636
ROA: origin2a0c:582::/32ROAs covering it name AS206119, not AS198571. If AS198571 should announce it, add a ROA for AS198571.1 of 636
Route object: none2a0c:582::/32No route object for it. Add a route object with origin AS198571 in the RIR database for the space.1 of 636
ROA: origin2a0c:583::/32ROAs covering it name AS206119, not AS198571. If AS198571 should announce it, add a ROA for AS198571.1 of 636
Route object: none2a0c:583::/32No route object for it. Add a route object with origin AS198571 in the RIR database for the space.1 of 636
ROA: origin2a0d:c980::/29ROAs covering it name AS7018, not AS198571. If AS198571 should announce it, add a ROA for AS198571.1 of 636
Route object: none2a0d:c980::/29Route objects for it name AS7018. Add a route object with origin AS198571 in the RIR database for the space.1 of 636

Route objects not announced

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

2a0c:9241::/32RIPEInvalid: origin
2a0c:9242::/32RIPEInvalid: origin
2a0c:9243::/32RIPEInvalid: origin
2a0c:9244::/32RIPEInvalid: origin
2a0c:9245::/32RIPEInvalid: origin
2a0c:9246::/32RIPEInvalid: origin
2a0c:9247::/32RIPEInvalid: origin

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.