bgpreport

Network · data from 2026-11-12

AS399461 HOSTSNAP-NETWORK - HostSNAP LLC

Registry name: HOSTSNAP-NETWORK - HostSNAP LLC, US · not in PeeringDB

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

Announced routes

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

142.248.184.0/22 Invalid: origin Other origin only 30 4%low visibility 22
142.249.104.0/22 Invalid: origin Other origin only 30 4%low visibility 22
43.252.56.0/24 No ROA None 11 2%low visibility 7
43.252.57.0/24 No ROA None 11 2%low visibility 7
43.252.58.0/24 No ROA None 11 2%low visibility 7
43.252.59.0/24 No ROA None 11 2%low visibility 7
103.233.44.0/24 No ROA None 11 2%low visibility 7
103.233.45.0/24 No ROA None 11 2%low visibility 7
103.233.46.0/24 No ROA None 11 2%low visibility 7
103.233.47.0/24 No ROA None 11 2%low visibility 7
103.171.136.0/23 Valid RIR databaseAPNIC 673 100% 66
122.8.0.0/24 Valid RIR databaseAPNIC 673 100% 66
122.8.22.0/24 Valid RIR databaseAPNIC 673 100% 66
204.147.232.0/22 Valid RIR databaseARIN 638 95% 66

AS-SET

AS399461 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 22 are in fix.csv.

  • ROA: origin2
  • ROA: none8
  • Route object: none10
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin142.248.184.0/22ROAs covering it name AS19695, not AS399461. If AS399461 should announce it, add a ROA for AS399461.30 of 673
Route object: none142.248.184.0/22Route objects for it name AS19695. Add a route object with origin AS399461 in the RIR database for the space.30 of 673
ROA: origin142.249.104.0/22ROAs covering it name AS19695, not AS399461. If AS399461 should announce it, add a ROA for AS399461.30 of 673
Route object: none142.249.104.0/22Route objects for it name AS19695. Add a route object with origin AS399461 in the RIR database for the space.30 of 673
ROA: none43.252.56.0/24No ROA covers it. Add a ROA for AS399461, maxLength 24.11 of 673
Route object: none43.252.56.0/24No route object for it. Add a route object with origin AS399461 in the RIR database for the space.11 of 673
ROA: none43.252.57.0/24No ROA covers it. Add a ROA for AS399461, maxLength 24.11 of 673
Route object: none43.252.57.0/24No route object for it. Add a route object with origin AS399461 in the RIR database for the space.11 of 673
ROA: none43.252.58.0/24No ROA covers it. Add a ROA for AS399461, maxLength 24.11 of 673
Route object: none43.252.58.0/24No route object for it. Add a route object with origin AS399461 in the RIR database for the space.11 of 673
ROA: none43.252.59.0/24No ROA covers it. Add a ROA for AS399461, maxLength 24.11 of 673
Route object: none43.252.59.0/24No route object for it. Add a route object with origin AS399461 in the RIR database for the space.11 of 673
ROA: none103.233.44.0/24No ROA covers it. Add a ROA for AS399461, maxLength 24.11 of 673
Route object: none103.233.44.0/24No route object for it. Add a route object with origin AS399461 in the RIR database for the space.11 of 673
ROA: none103.233.45.0/24No ROA covers it. Add a ROA for AS399461, maxLength 24.11 of 673
Route object: none103.233.45.0/24No route object for it. Add a route object with origin AS399461 in the RIR database for the space.11 of 673
ROA: none103.233.46.0/24No ROA covers it. Add a ROA for AS399461, maxLength 24.11 of 673
Route object: none103.233.46.0/24No route object for it. Add a route object with origin AS399461 in the RIR database for the space.11 of 673
ROA: none103.233.47.0/24No ROA covers it. Add a ROA for AS399461, maxLength 24.11 of 673
Route object: none103.233.47.0/24No route object for it. Add a route object with origin AS399461 in the RIR database for the space.11 of 673

Route objects not announced

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

185.141.82.0/24RIPEValid
185.141.83.0/24RIPEValid

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.