bgpreport

Network · data from 2026-11-12

AS400039 WT-AUR - Wolverine Trading, LLC

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS400039, 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.36.206.0/24 No ROA Other origin only 673 100% 67
192.109.131.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
165.254.178.32/28 Valid None 28 4%low visibility 22
68.67.206.0/24 Valid RIR databaseARIN, RADB 673 100% 67
85.237.219.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
86.104.209.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
87.248.136.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
94.124.72.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
104.234.210.0/24 Valid RIR databaseARIN, RADB 673 100% 67
138.99.144.0/24 Valid RIR databaseLACNIC, RADB 673 100% 67
141.11.4.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
141.98.156.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
146.19.92.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
154.16.37.0/24 Valid RIR databaseAFRINIC, RADB 673 100% 67
163.5.167.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
181.215.245.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.214.109.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
191.96.197.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
191.101.57.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
192.166.83.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
193.31.42.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
193.109.192.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
194.50.4.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
195.20.105.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
199.101.197.0/24 Valid RIR databaseARIN, RADB 673 100% 67
204.14.78.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.185.32.0/24 Valid RIR databaseARIN, RADB 673 100% 67
2.59.56.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
5.181.129.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
5.181.179.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
45.158.58.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
46.37.106.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
45.95.213.0/24 Valid RIR databaseRIPE 670 100% 68
85.209.16.0/24 Valid RIR databaseRIPE 670 100% 68
146.19.237.0/24 Valid RIR databaseRIPE 670 100% 68
185.143.242.0/24 Valid RIR databaseRIPE 670 100% 68
185.200.245.0/24 Valid RIR databaseRIPE 670 100% 68
185.234.23.0/24 Valid RIR databaseRIPE 670 100% 68
188.93.137.0/24 Valid RIR databaseRIPE 670 100% 68

AS-SET

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

  • ROA: none2
  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none185.36.206.0/24No ROA covers it. Add a ROA for AS400039, maxLength 24.673 of 673
Route object: none185.36.206.0/24Route objects for it name AS207326, AS400040. Add a route object with origin AS400039 in the RIR database for the space.673 of 673
ROA: none192.109.131.0/24No ROA covers it. Add a ROA for AS400039, maxLength 24.673 of 673
Route object: none165.254.178.32/28No route object for it. Add a route object with origin AS400039 in the RIR database for the space.28 of 673

Route objects not announced

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

2001:470:1e8::/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.