bgpreport

Network · data from 2026-11-12

AS396919 Shadow US

Registry name: SHADOW - Shadow, US · PeeringDB

8IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 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
4Route objects not announced registered with origin AS396919, seen from no peer

Announced routes

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

66.51.112.0/22 Valid RIR databaseARIN 669 99% 66
66.51.116.0/22 Valid RIR databaseARIN 669 99% 66
69.58.92.0/23 Valid RIR databaseARIN 669 99% 66
216.180.136.0/24 Valid RIR databaseARIN 669 99% 66
216.180.137.0/24 Valid RIR databaseARIN 669 99% 66
216.180.139.0/24 Valid RIR databaseARIN 669 99% 66
216.180.140.0/24 Valid RIR databaseARIN 669 99% 66
216.180.141.0/24 Valid RIR databaseARIN 669 99% 66
2605:940:510::/44 Valid RIR databaseARIN 631 99% 68
2605:940:610::/44 Valid RIR databaseARIN 631 99% 68
2605:940:710::/44 Valid RIR databaseARIN 631 99% 68

AS-SET

PeeringDB's irr_as_set for AS396919: AS-BLADE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS396919 isn't in the set, or no route object for AS396919 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS396919 in itNot covered
AS-BLADE RIPE 2145 Yes 0

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

  • Route object: not announced4

Route objects not announced

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

216.180.128.0/21ARINValid
216.180.143.0/24ARINValid
2605:940::/40ARINValid
2605:940:400::/40ARINValid

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.