bgpreport

Network · data from 2026-11-12

AS393960 HOST4GEEKS-LLC

Registry name: HOST4GEEKS-LLC - Host4Geeks LLC, US · PeeringDB

10IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
7Route objects not announced registered with origin AS393960, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS393960, 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.
139.60.236.0/22 Valid Other IRR onlyRADB 671 100% 69
103.83.194.0/24 Valid RIR databaseAPNIC 672 100% 67
139.60.232.0/22 Valid RIR databaseARIN 672 100% 67
172.93.121.0/24 Valid RIR databaseARIN 672 100% 67
172.93.123.0/24 Valid RIR databaseARIN 672 100% 67
185.221.216.0/24 Valid RIR databaseRIPE 672 100% 67
213.178.142.0/24 Valid RIR databaseRIPE 664 99% 67
66.85.46.0/24 Valid RIR databaseARIN, RADB 658 98% 69
66.85.47.0/24 Valid RIR databaseARIN, RADB 658 98% 69
172.93.120.0/24 Valid RIR databaseARIN, RADB, RIPE-NONAUTH 658 98% 69

AS-SET

AS393960'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 8 are in fix.csv.

  • Route object: RIR1
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
Route object: RIR139.60.236.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

66.85.45.0/24RADBNo ROA
103.83.192.0/22RADBNo ROA
104.194.218.0/24RADBNo ROA
181.215.52.0/22RADBNo ROA
185.172.36.0/22RADBNo ROA
191.96.76.0/22RADBNo ROA
191.96.124.0/22RADBNo ROA

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.