bgpreport

Network · data from 2026-11-12

AS211635 Stefan Nagel Elektrotechnik

Registry name: AS211635-AS Stefan Nagel, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS211635, 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.
167.104.52.0/24 Valid RIR databaseRIPE 671 100% 68
2a0e:8f02:212d::/48 Valid RIR databaseRIPE 636 100% 67
2a0e:8f02:2121::/48 Valid RIR databaseRADB, RIPE 635 100% 69
2a0e:8f02:2122::/48 Valid RIR databaseRADB, RIPE 635 100% 69
2a0e:8f02:212e::/48 Valid RIR databaseRADB, RIPE 635 100% 69
2a0e:8f02:212f::/48 Valid RIR databaseRADB, RIPE 635 100% 69
2a0e:8f02:2120::/48 Valid RIR databaseRADB, RIPE 634 100% 69
2a0e:8f02:2123::/48 Valid RIR databaseRIPE 634 100% 69
2a0e:8f02:2124::/48 Valid RIR databaseRIPE 634 100% 69
2a0e:8f02:2125::/48 Valid RIR databaseRIPE 634 100% 69
2a0e:8f02:2126::/48 Valid RIR databaseRIPE 634 100% 69
2a0e:8f02:2127::/48 Valid RIR databaseRIPE 634 100% 69
2a0e:8f02:212a::/48 Valid RIR databaseRIPE 633 100% 69
2a0e:8f02:212c::/48 Valid RIR databaseRIPE 633 100% 69
2a0e:8f02:2128::/48 Valid RIR databaseRIPE 632 99% 69
2a0e:8f02:2129::/48 Valid RIR databaseRIPE 632 99% 69
2a0e:8f02:212b::/48 Valid RIR databaseRIPE 632 99% 69

AS-SET

PeeringDB's irr_as_set for AS211635: RIPE::AS-211635-SET. 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 (AS211635 isn't in the set, or no route object for AS211635 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 objectsAS211635 in itNot covered
RIPE::AS-211635-SET RIPE 1118 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 1 are in fix.csv.

  • Route object: not announced1

Route objects not announced

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

2a0e:8f02:2120::/44RIPEValid

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.