bgpreport

Network · data from 2026-11-12

AS48646 Stefan Dunkel

Registry name: STEFAN6 SDRmedia Verwaltungs GmbH, DE · PeeringDB

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

Announced routes

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

2a07:59c6:eed3::/48 Invalid: origin None 1 0%low visibility 1
2a07:59c6:eed8::/48 Invalid: origin None 1 0%low visibility 1
2a0e:fd45:40f1::/48 No ROA None 4 1%low visibility 4
2a0f:5707:ab23::/48 No ROA None 4 1%low visibility 4
2a0c:9a40:808a::/48 Valid None 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS48646: AS-STEFANDUNKEL. 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 (AS48646 isn't in the set, or no route object for AS48646 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 objectsAS48646 in itNot covered
AS-STEFANDUNKEL RIPElists itself further down6 member sets in no database: AS-IPV6GO, AS-ROUTE48, AS-SHIZUKUGLOBAL-EUROPE, AS-SVINE, AS-ZH-NET … 233656,780 Yes 5

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

  • ROA: origin2
  • ROA: none2
  • Route object: none5
  • AS-SET: missing member6
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: origin2a07:59c6:eed3::/48ROAs covering it name AS44652, not AS48646. If AS48646 should announce it, add a ROA for AS48646.1 of 636
Route object: none2a07:59c6:eed3::/48No route object for it. Add a route object with origin AS48646 in the RIR database for the space.1 of 636
ROA: origin2a07:59c6:eed8::/48ROAs covering it name AS44652, not AS48646. If AS48646 should announce it, add a ROA for AS48646.1 of 636
Route object: none2a07:59c6:eed8::/48No route object for it. Add a route object with origin AS48646 in the RIR database for the space.1 of 636
ROA: none2a0e:fd45:40f1::/48No ROA covers it. Add a ROA for AS48646, maxLength 48.4 of 636
Route object: none2a0e:fd45:40f1::/48No route object for it. Add a route object with origin AS48646 in the RIR database for the space.4 of 636
ROA: none2a0f:5707:ab23::/48No ROA covers it. Add a ROA for AS48646, maxLength 48.4 of 636
Route object: none2a0f:5707:ab23::/48No route object for it. Add a route object with origin AS48646 in the RIR database for the space.4 of 636
Route object: none2a0c:9a40:808a::/48No route object for it. Add a route object with origin AS48646 in the RIR database for the space.634 of 636
AS-SET: missing memberAS-STEFANDUNKELAS-STEFANDUNKEL (RIPE) lists AS-IPV6GO; no IRR database read has it.
AS-SET: missing memberAS-STEFANDUNKELAS-STEFANDUNKEL (RIPE) lists AS-ROUTE48; no IRR database read has it.
AS-SET: missing memberAS-STEFANDUNKELAS-STEFANDUNKEL (RIPE) lists AS-SHIZUKUGLOBAL-EUROPE; no IRR database read has it.
AS-SET: missing memberAS-STEFANDUNKELAS-STEFANDUNKEL (RIPE) lists AS-SVINE; no IRR database read has it.
AS-SET: missing memberAS-STEFANDUNKELAS-STEFANDUNKEL (RIPE) lists AS-ZH-NET; no IRR database read has it.
AS-SET: missing memberAS-STEFANDUNKELAS-STEFANDUNKEL (RIPE) lists AS200372:AS-DORFHOSTER-SET; no IRR database read has it.

Route objects not announced

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

94.247.45.0/24RIPEValid
178.251.226.0/24RIPEValid
194.5.99.0/24RIPEValid
2a0e:aa01:ab02::/48RIPEValid
2a0f:5707:aac0::/44RIPEValid
2a0f:5707:ac80::/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.