Network · data from 2026-11-12
AS400039 WT-AUR - Wolverine Trading, LLC
Registry name: WT-AUR - Wolverine Trading, LLC, US · not in PeeringDB
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% |
| 192.109.131.0/24 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 165.254.178.32/28 | Valid | None | 28 4%low visibility |
| 68.67.206.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 85.237.219.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 86.104.209.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 87.248.136.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 94.124.72.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 104.234.210.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 138.99.144.0/24 | Valid | RIR databaseLACNIC, RADB | 673 100% |
| 141.11.4.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 141.98.156.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 146.19.92.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 154.16.37.0/24 | Valid | RIR databaseAFRINIC, RADB | 673 100% |
| 163.5.167.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 181.215.245.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 185.214.109.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 191.96.197.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 191.101.57.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 192.166.83.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 193.31.42.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 193.109.192.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 194.50.4.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 195.20.105.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 199.101.197.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 204.14.78.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 216.185.32.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 2.59.56.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 5.181.129.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 5.181.179.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 45.158.58.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 46.37.106.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 45.95.213.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 85.209.16.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 146.19.237.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.143.242.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.200.245.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.234.23.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 188.93.137.0/24 | Valid | RIR databaseRIPE | 670 100% |
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
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.36.206.0/24 | No ROA covers it. Add a ROA for AS400039, maxLength 24. |
| Route object: none | 185.36.206.0/24 | Route objects for it name AS207326, AS400040. Add a route object with origin AS400039 in the RIR database for the space. |
| ROA: none | 192.109.131.0/24 | No ROA covers it. Add a ROA for AS400039, maxLength 24. |
| Route object: none | 165.254.178.32/28 | No route object for it. Add a route object with origin AS400039 in the RIR database for the space. |
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::/48 | ARIN | Valid |
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.