bgpreport

Network · data from 2026-11-12

AS42882 SYSUP-AT SysUP IT GmbH & Co KG

Registry name: SYSUP-AT SysUP IT GmbH & Co KG, AT · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS42882, 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.
195.43.139.0/24 No ROA Other origin only 668 99% 67
185.169.8.0/22 No ROA RIR databaseRIPE 668 99% 67
77.75.16.0/24 No ROA RIR databaseRIPE 667 99% 67
77.75.17.0/24 No ROA RIR databaseRIPE 667 99% 67
77.75.18.0/24 No ROA RIR databaseRIPE 667 99% 67
77.75.19.0/24 No ROA RIR databaseRIPE 667 99% 67
77.75.20.0/24 No ROA RIR databaseRIPE 667 99% 67
77.75.21.0/24 No ROA RIR databaseRIPE 667 99% 67
77.75.22.0/24 No ROA RIR databaseRIPE 667 99% 67
2a00:1510::/32 No ROA RIR databaseRIPE 635 100% 67

AS-SET

AS42882 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: none10
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none195.43.139.0/24No ROA covers it. Add a ROA for AS42882, maxLength 24.668 of 673
Route object: none195.43.139.0/24Route objects for it name AS8412. Add a route object with origin AS42882 in the RIR database for the space.668 of 673
ROA: none185.169.8.0/22No ROA covers it. Add a ROA for AS42882, maxLength 22.668 of 673
ROA: none77.75.16.0/24No ROA covers it. Add a ROA for AS42882, maxLength 24.667 of 673
ROA: none77.75.17.0/24No ROA covers it. Add a ROA for AS42882, maxLength 24.667 of 673
ROA: none77.75.18.0/24No ROA covers it. Add a ROA for AS42882, maxLength 24.667 of 673
ROA: none77.75.19.0/24No ROA covers it. Add a ROA for AS42882, maxLength 24.667 of 673
ROA: none77.75.20.0/24No ROA covers it. Add a ROA for AS42882, maxLength 24.667 of 673
ROA: none77.75.21.0/24No ROA covers it. Add a ROA for AS42882, maxLength 24.667 of 673
ROA: none77.75.22.0/24No ROA covers it. Add a ROA for AS42882, maxLength 24.667 of 673
ROA: none2a00:1510::/32No ROA covers it. Add a ROA for AS42882, maxLength 32.635 of 636

Route objects not announced

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

77.75.16.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.