bgpreport

Network · data from 2026-11-12

AS15866 AS-PEGASUS ITventive AG

Registry name: AS-PEGASUS ITventive AG, DE · not in PeeringDB

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

Announced routes

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

2a00:1920::/48 Valid Nonecovered by 2a00:1920::/32 633 100% 67
94.232.192.0/21 Valid RIR databaseRIPE 671 100% 66
185.45.88.0/22 Valid RIR databaseRIPE 671 100% 66
217.171.240.0/20 Valid RIR databaseRIPE 671 100% 66

AS-SET

AS15866 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 52 are in fix.csv.

  • Route object: none1
  • Route object: not announced51
ChangePrefix or setDetailFull-table peers
Route object: none2a00:1920::/48No route object for it. A route object for 2a00:1920::/32 with origin AS15866 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15866 in the RIR database for the space.633 of 636

Route objects not announced

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

94.232.192.0/22RIPEInvalid: maxLength
94.232.192.0/23RIPEInvalid: maxLength
94.232.192.0/24RIPEInvalid: maxLength
94.232.193.0/24RIPEInvalid: maxLength
94.232.194.0/23RIPEInvalid: maxLength
94.232.194.0/24RIPEInvalid: maxLength
94.232.195.0/24RIPEInvalid: maxLength
94.232.196.0/22RIPEInvalid: maxLength
94.232.196.0/23RIPEInvalid: maxLength
94.232.196.0/24RIPEInvalid: maxLength
94.232.197.0/24RIPEInvalid: maxLength
94.232.198.0/23RIPEInvalid: maxLength
94.232.198.0/24RIPEInvalid: maxLength
94.232.199.0/24RIPEInvalid: maxLength
185.45.88.0/23RIPEInvalid: maxLength
185.45.88.0/24RIPEInvalid: maxLength
185.45.89.0/24RIPEInvalid: maxLength
185.45.90.0/23RIPEInvalid: maxLength
185.45.90.0/24RIPEInvalid: maxLength
185.45.91.0/24RIPEValid
217.171.240.0/21RIPEInvalid: maxLength
217.171.240.0/22RIPEInvalid: maxLength
217.171.240.0/23RIPEInvalid: maxLength
217.171.240.0/24RIPEInvalid: maxLength
217.171.241.0/24RIPEInvalid: maxLength
217.171.242.0/23RIPEInvalid: maxLength
217.171.242.0/24RIPEInvalid: maxLength
217.171.243.0/24RIPEInvalid: maxLength
217.171.244.0/22RIPEInvalid: maxLength
217.171.244.0/23RIPEInvalid: maxLength
217.171.244.0/24RIPEInvalid: maxLength
217.171.245.0/24RIPEInvalid: maxLength
217.171.246.0/23RIPEInvalid: maxLength
217.171.246.0/24RIPEInvalid: maxLength
217.171.247.0/24RIPEInvalid: maxLength
217.171.248.0/21RIPEInvalid: maxLength
217.171.248.0/22RIPEInvalid: maxLength
217.171.248.0/23RIPEInvalid: maxLength
217.171.248.0/24RIPEInvalid: maxLength
217.171.249.0/24RIPEInvalid: maxLength
217.171.250.0/23RIPEInvalid: maxLength
217.171.250.0/24RIPEInvalid: maxLength
217.171.251.0/24RIPEInvalid: maxLength
217.171.252.0/22RIPEInvalid: maxLength
217.171.252.0/23RIPEInvalid: maxLength
217.171.252.0/24RIPEInvalid: maxLength
217.171.253.0/24RIPEInvalid: maxLength
217.171.254.0/23RIPEInvalid: maxLength
217.171.254.0/24RIPEInvalid: maxLength
217.171.255.0/24RIPEInvalid: maxLength
2a00:1920::/32RIPENo 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.