bgpreport

Network · data from 2026-11-12

AS203446 SMARTNET Germany GmbH

Registry name: AS203446 SMARTNET Germany GmbH, DE · PeeringDB

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

Announced routes

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

87.84.224.0/24 Invalid: origin Other origin only 1 0%low visibility 1
2a0e:97c0:472::/48 No ROA RIR databaseRIPE 636 100% 67
2a0e:97c0:473::/48 No ROA RIR databaseRIPE 636 100% 67
2.56.246.0/24 Valid RIR databaseRIPE 672 100% 66
89.213.171.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
91.109.45.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
92.242.166.0/24 Valid RIR databaseRIPE 672 100% 66
93.90.74.0/24 Valid RIR databaseRIPE 672 100% 66
163.5.195.0/24 Valid RIR databaseRIPE 672 100% 66
185.50.255.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
194.62.248.0/24 Valid RIR databaseRIPE 672 100% 66
5.83.141.0/24 Valid RIR databaseRIPE 671 100% 66
37.114.41.0/24 Valid RIR databaseRIPE 671 100% 67
51.241.141.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
64.204.182.0/24 Valid RIR databaseARIN, RADB 671 100% 66
64.204.203.0/24 Valid RIR databaseARIN, RADB 671 100% 66
45.131.65.0/24 Valid RIR databaseRIPE 670 100% 66
45.134.39.0/24 Valid RIR databaseRIPE 670 100% 66
45.137.70.0/24 Valid RIR databaseRIPE 670 100% 66
46.37.101.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
2a02:2fc0:17::/48 Valid RIR databaseRIPE 636 100% 67
2a0e:97c0:3ea::/48 Valid RIR databaseRIPE 636 100% 67
2a0e:97c0:470::/48 Valid RIR databaseRIPE 636 100% 67
2a0f:6282:b000::/36 Valid RIR databaseRIPE 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS203446: AS-ALEX0220. 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 (AS203446 isn't in the set, or no route object for AS203446 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 objectsAS203446 in itNot covered
AS-ALEX0220 RIPElists itself further down9 member sets in no database: AS-PIXOOF, AS-VERSADC, AS198351:AS-SECUREWAN, AS199746:AS-NEXTSERV, AS208191:AS-GOHOST … 1,45718553,077 Yes 1

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

  • ROA: origin1
  • ROA: none2
  • Route object: none1
  • AS-SET: missing member9
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin87.84.224.0/24ROAs covering it name AS834, not AS203446. If AS203446 should announce it, add a ROA for AS203446.1 of 673
Route object: none87.84.224.0/24Route objects for it name AS834, AS3257. Add a route object with origin AS203446 in the RIR database for the space.1 of 673
ROA: none2a0e:97c0:472::/48No ROA covers it. Add a ROA for AS203446, maxLength 48.636 of 636
ROA: none2a0e:97c0:473::/48No ROA covers it. Add a ROA for AS203446, maxLength 48.636 of 636
AS-SET: missing memberAS-ALEX0220AS-ALEX0220 (RIPE) lists AS-PIXOOF; no IRR database read has it.
AS-SET: missing memberAS-ALEX0220AS-ALEX0220 (RIPE) lists AS-VERSADC; no IRR database read has it.
AS-SET: missing memberAS-ALEX0220AS-ALEX0220 (RIPE) lists AS198351:AS-SECUREWAN; no IRR database read has it.
AS-SET: missing memberAS-ALEX0220AS-ALEX0220 (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.
AS-SET: missing memberAS-ALEX0220AS-ALEX0220 (RIPE) lists AS208191:AS-GOHOST; no IRR database read has it.
AS-SET: missing memberAS-ALEX0220AS-ALEX0220 (RIPE) lists AS213465:AS-RAINBOW; no IRR database read has it.
AS-SET: missing memberAS-ALEX0220AS-ALEX0220 (RIPE) lists AS215110:AS-CUSTOMERS; no IRR database read has it.
AS-SET: missing memberAS-ALEX0220AS-ALEX0220 (RIPE) lists AS39753:AS-LIUXYON; no IRR database read has it.
AS-SET: missing memberAS-ALEX0220AS-ALEX0220 (RIPE) lists AS60223:AS-NETIFACE; no IRR database read has it.

Route objects not announced

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

37.114.46.0/24RIPEValid
82.139.239.0/24RIPEInvalid: origin

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.