bgpreport

Network · data from 2026-11-12

AS39409 MyRootPW.com

Registry name: SWG-MyRootPW Sebastian-Wilhelm Graf, AT · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS39409, 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.
2001:678:d58::/48 No ROA None 2 0%low visibility 2
185.216.8.0/24 Valid RIR databaseRIPE 673 100% 66
37.153.156.0/24 Valid RIR databaseRIPE 672 100% 66
2a10:9906:3020::/48 Valid RIR databaseRIPE 636 100% 69
2a10:9906:3050::/48 Valid RIR databaseRIPE 636 100% 69
2a10:9906::/48 Valid RIR databaseRIPE 3 0%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS39409: AS-SWG-MYROOTPW. 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 (AS39409 isn't in the set, or no route object for AS39409 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 objectsAS39409 in itNot covered
AS-SWG-MYROOTPW RIPE 229 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 4 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2001:678:d58::/48No ROA covers it. Add a ROA for AS39409, maxLength 48.2 of 636
Route object: none2001:678:d58::/48No route object for it. Add a route object with origin AS39409 in the RIR database for the space.2 of 636

Route objects not announced

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

2a10:9906:1001::/48RIPEValid
2a10:9906:1002::/48RIPEValid

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.