bgpreport

Network · data from 2026-11-12

AS208545 sector7 sector7 GmbH

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS208545, 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.
82.215.65.0/24 Valid RIR databaseRIPE 673 100% 66
178.175.180.0/23 Valid RIR databaseRIPE 673 100% 66
178.175.180.0/24 Valid RIR databaseRIPE 673 100% 66
178.175.181.0/24 Valid RIR databaseRIPE 673 100% 66
2a12:be40::/48 Valid RIR databaseRIPE 633 100% 67
2a12:be40:1::/48 Valid RIR databaseRIPE 633 100% 67
2a12:be40:2::/48 Valid RIR databaseRIPE 633 100% 67
2a12:be40::/29 Valid RIR databaseRIPE 632 99% 67

AS-SET

AS208545 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 14 are in fix.csv.

  • Route object: not announced14

Route objects not announced

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

2a01:170:1050::/48RIPEValid
2a12:be40:3::/48RIPEValid
2a12:be40:4::/48RIPEValid
2a12:be40:5::/48RIPEValid
2a12:be40:6::/48RIPEValid
2a12:be40:7::/48RIPEValid
2a12:be40:8::/48RIPEValid
2a12:be40:9::/48RIPEValid
2a12:be40:a::/48RIPEValid
2a12:be40:b::/48RIPEValid
2a12:be40:c::/48RIPEValid
2a12:be40:d::/48RIPEValid
2a12:be40:e::/48RIPEValid
2a12:be40:f::/48RIPEValid

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.