bgpreport

Network · data from 2026-11-12

AS400072 THUND-20 - THUNDERBOX INC

Registry name: THUND-20 - THUNDERBOX INC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS400072, 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.
212.32.96.0/20 Invalid: origin None 2 0%low visibility 2
212.32.112.0/20 Invalid: origin None 2 0%low visibility 2
166.48.240.0/21 No ROA Other origin only 673 100% 67
62.164.224.0/20 Valid None 673 100% 67
62.164.240.0/20 Valid None 673 100% 67
66.43.4.0/22 Valid RIR databaseARIN 673 100% 67
72.22.32.0/19 Valid RIR databaseARIN 673 100% 67
74.122.56.0/21 Valid RIR databaseARIN 673 100% 67
107.180.128.0/21 Valid RIR databaseARIN 673 100% 67
107.180.160.0/19 Valid RIR databaseARIN 673 100% 67
185.141.116.0/24 Valid RIR databaseRIPE 673 100% 67
192.159.35.0/24 Valid RIR databaseARIN 673 100% 67
199.187.188.0/22 Valid RIR databaseARIN 673 100% 67
204.10.80.0/22 Valid RIR databaseARIN 673 100% 67
205.196.8.0/22 Valid RIR databaseARIN 673 100% 67
206.251.196.0/22 Valid RIR databaseARIN 673 100% 67
206.251.200.0/22 Valid RIR databaseARIN 673 100% 67
207.135.192.0/20 Valid RIR databaseARIN 673 100% 67
207.228.0.0/18 Valid RIR databaseARIN 673 100% 67
208.73.40.0/22 Valid RIR databaseARIN 673 100% 67
45.45.197.0/24 Valid RIR databaseARIN 672 100% 67
45.45.198.0/24 Valid RIR databaseARIN 672 100% 67
2607:52c0::/34 Valid RIR databaseARIN 634 100% 67

AS-SET

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

  • ROA: origin2
  • ROA: none1
  • Route object: none5
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: origin212.32.96.0/20ROAs covering it name AS5650, not AS400072. If AS400072 should announce it, add a ROA for AS400072.2 of 673
Route object: none212.32.96.0/20No route object for it. Add a route object with origin AS400072 in the RIR database for the space.2 of 673
ROA: origin212.32.112.0/20ROAs covering it name AS5650, not AS400072. If AS400072 should announce it, add a ROA for AS400072.2 of 673
Route object: none212.32.112.0/20No route object for it. Add a route object with origin AS400072 in the RIR database for the space.2 of 673
ROA: none166.48.240.0/21No ROA covers it. Add a ROA for AS400072, maxLength 21.673 of 673
Route object: none166.48.240.0/21Route objects for it name AS396338. Add a route object with origin AS400072 in the RIR database for the space.673 of 673
Route object: none62.164.224.0/20No route object for it. Add a route object with origin AS400072 in the RIR database for the space.673 of 673
Route object: none62.164.240.0/20No route object for it. Add a route object with origin AS400072 in the RIR database for the space.673 of 673

Route objects not announced

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

23.229.118.0/24RADBValid
23.229.127.0/24RADBValid
23.236.250.0/24RADBValid
23.236.254.0/24RADBValid
38.154.4.0/22RADBNo ROA
107.180.148.0/22ARINValid

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.