bgpreport

Network · data from 2026-11-12

AS400040 WT-FRANK - Wolverine Trading, LLC

Registry name: WT-FRANK - Wolverine Trading, LLC, US · not in PeeringDB

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

Announced routes

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

141.11.191.0/24 Valid Other IRR onlyRADB 673 100% 67
68.67.197.0/24 Valid RIR databaseARIN, RADB 673 100% 67
85.237.197.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
87.248.135.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
141.11.6.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
181.214.84.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.138.232.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.194.28.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.228.0.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
191.96.223.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
212.46.46.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
45.8.20.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
45.12.187.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
46.37.105.0/24 Valid RIR databaseRADB, RIPE 672 100% 67

AS-SET

AS400040 isn't in PeeringDB, where networks name their 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 12 are in fix.csv.

  • Route object: RIR1
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
Route object: RIR141.11.191.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

86.104.209.0/24RADB, RIPEValid
138.99.144.0/24LACNIC, RADBValid
146.19.92.0/24RIPEInvalid: origin
154.16.37.0/24AFRINIC, RADBValid
154.16.184.0/24AFRINICInvalid: origin
154.16.237.0/24AFRINICInvalid: origin
181.215.245.0/24RIPEInvalid: origin
185.36.206.0/24RADB, RIPENo ROA
192.109.131.0/24ARIN, RADBNo ROA
193.109.192.0/24RIPEInvalid: origin
193.148.255.0/24ARINInvalid: 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.