bgpreport

Network · data from 2026-11-12

AS399641 WT-DC2 - Wolverine Trading, LLC

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

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

Announced routes

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

185.214.111.0/24 No ROA RIR databaseRADB, RIPE 673 100% 67
165.254.23.224/28 Valid None 28 4%low visibility 22
185.187.234.0/24 Valid Other IRR onlyRADB 673 100% 67
31.41.248.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
37.140.250.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
89.106.205.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
91.188.253.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
104.234.22.0/24 Valid RIR databaseARIN, RADB 673 100% 67
125.62.78.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
141.11.19.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
141.11.30.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
141.11.176.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
141.11.177.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
154.16.99.0/24 Valid RIR databaseAFRINIC, RADB 673 100% 67
163.5.235.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.194.31.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.218.103.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.220.146.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
193.160.8.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
193.176.55.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
194.50.243.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
194.150.205.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
195.20.98.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
195.206.231.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
213.170.145.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
45.132.26.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
45.155.66.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
45.155.67.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
46.37.102.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
77.81.137.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
163.5.105.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
192.166.115.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
193.57.165.0/24 Valid RIR databaseRADB, RIPE 672 100% 67

AS-SET

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

  • ROA: none1
  • Route object: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none185.214.111.0/24No ROA covers it. Add a ROA for AS399641, maxLength 24.673 of 673
Route object: none165.254.23.224/28No route object for it. Add a route object with origin AS399641 in the RIR database for the space.28 of 673
Route object: RIR185.187.234.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS399641 is announced.

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.