bgpreport

Network · data from 2026-11-12

AS400384 Hostings House

Registry name: HOSTINGS-HOUSE-US - Hostings House, US · PeeringDB

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

Announced routes

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

165.140.92.0/24 Invalid: origin Other origin only 0 0%low visibility 1
216.238.39.0/24 No ROA Other origin only 671 100% 67
162.221.148.0/22 Valid None 670 100% 67
103.181.98.0/24 Valid RIR databaseAPNIC 670 100% 68
103.181.99.0/24 Valid RIR databaseAPNIC 670 100% 68
208.77.164.0/24 Valid RIR databaseARIN 670 100% 68
66.245.164.0/24 Valid RIR databaseARIN 1 0%low visibility 1
66.245.165.0/24 Valid RIR databaseARIN 1 0%low visibility 1

AS-SET

AS400384's PeeringDB record names no 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 12 are in fix.csv.

  • ROA: origin1
  • ROA: none1
  • Route object: none3
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: origin165.140.92.0/24ROAs covering it name AS845, not AS400384. If AS400384 should announce it, add a ROA for AS400384.0 of 673
Route object: none165.140.92.0/24Route objects for it name AS845. Add a route object with origin AS400384 in the RIR database for the space.0 of 673
ROA: none216.238.39.0/24No ROA covers it. Add a ROA for AS400384, maxLength 24.671 of 673
Route object: none216.238.39.0/24Route objects for it name AS834. Add a route object with origin AS400384 in the RIR database for the space.671 of 673
Route object: none162.221.148.0/22No route object for it. Add a route object with origin AS400384 in the RIR database for the space.670 of 673

Route objects not announced

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

63.135.161.0/24ARINInvalid: origin
66.245.167.0/24ARINValid
103.181.98.0/23APNICValid
140.235.65.0/24ARINValid
141.195.127.0/24ARINValid
165.140.94.0/24ARINValid
165.140.95.0/24ARINValid

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.