Network · data from 2026-11-12

AS39618 HostCram AS39618

Registry name: HostCram HostCram LLC, US · PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.0% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

3Route objects not announced registered with origin AS39618, seen from no peer

Announced routes

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


23.160.160.0/24	Valid	RIR databaseARIN	671 100%	68
23.160.161.0/24	Valid	RIR databaseALTDB, ARIN, BBOI, NTTCOM	671 100%	68
2602:fd92::/40	Valid	RIR databaseARIN	634 100%	70

AS-SET

AS39618'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 3 are in fix.csv.

Route object: not announced3

Route objects not announced

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


2602:fd92:100::/40	ALTDB, NTTCOM	Valid
2602:fd92:a00::/40	ARIN, RADB	Valid
2602:fd92:e00::/40	ARIN	Valid

2602:fd92:100::/40

ALTDB, NTTCOM

Valid

2602:fd92:a00::/40

ARIN, RADB

Valid

2602:fd92:e00::/40

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.