bgpreport

Network · data from 2026-11-12

AS393941 AS393941, LLC

Registry name: PRIMARY-AS393941 - Flying Man Studio, LLC., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS393941, 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.
2602:80b:4000::/44 No ROA Nonecovered by 2602:80b:4000::/40 632 99% 69
2602:80b:4000::/48 No ROA Nonecovered by 2602:80b:4000::/40 632 99% 69
2620:11f:d00a::/48 Valid Other origin onlycovered by 2620:11f:d000::/44 632 99% 69
2620:11f:d00b::/48 Valid Nonecovered by 2620:11f:d000::/44 632 99% 69
2620:11f:d00c::/48 Valid Nonecovered by 2620:11f:d000::/44 632 99% 69
2620:11f:d00f::/48 Valid Nonecovered by 2620:11f:d000::/44 632 99% 69
198.29.64.0/24 Valid RIR databaseARIN, RADB 669 99% 68
198.29.65.0/24 Valid RIR databaseARIN, RADB 669 99% 68
2620:11f:d001::/48 Valid RIR databaseARIN 632 99% 69
2620:11f:d002::/48 Valid RIR databaseARIN 632 99% 69
2620:11f:d003::/48 Valid RIR databaseARIN 632 99% 69
2620:11f:d00e::/48 Valid RIR databaseARIN 632 99% 69

AS-SET

AS393941's PeeringDB record names no AS-SET.

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

  • ROA: none2
  • Route object: none6
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none2602:80b:4000::/44No ROA covers it. Add a ROA for AS393941, maxLength 44.632 of 636
Route object: none2602:80b:4000::/44No route object for it. A route object for 2602:80b:4000::/40 with origin AS393941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393941 in the RIR database for the space.632 of 636
ROA: none2602:80b:4000::/48No ROA covers it. Add a ROA for AS393941, maxLength 48.632 of 636
Route object: none2602:80b:4000::/48No route object for it. A route object for 2602:80b:4000::/40 with origin AS393941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393941 in the RIR database for the space.632 of 636
Route object: none2620:11f:d00a::/48Route objects for it name AS16866. A route object for 2620:11f:d000::/44 with origin AS393941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393941 in the RIR database for the space.632 of 636
Route object: none2620:11f:d00b::/48No route object for it. A route object for 2620:11f:d000::/44 with origin AS393941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393941 in the RIR database for the space.632 of 636
Route object: none2620:11f:d00c::/48No route object for it. A route object for 2620:11f:d000::/44 with origin AS393941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393941 in the RIR database for the space.632 of 636
Route object: none2620:11f:d00f::/48No route object for it. A route object for 2620:11f:d000::/44 with origin AS393941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393941 in the RIR database for the space.632 of 636

Route objects not announced

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

198.29.64.0/23ARIN, RADBValid
2602:80b:4000::/40ARINNo ROA
2620:11f:d000::/44ARINValid
2620:11f:d004::/48ARINValid
2620:11f:d005::/48ARINValid
2620:11f:d006::/48ARINValid

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.