bgpreport

Network · data from 2026-11-12

AS393498 LUNAR-CORE - Moonlesshosting

Registry name: LUNAR-CORE - Moonlesshosting, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS393498, 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.
181.214.164.0/24 Invalid: origin Other origin only 1 0%low visibility 1
192.187.131.0/24 Valid RIR databaseARIN 673 100% 66

AS-SET

AS393498 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 2 are in fix.csv.

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin181.214.164.0/24ROAs covering it name AS834, not AS393498. If AS393498 should announce it, add a ROA for AS393498.1 of 673
Route object: none181.214.164.0/24Route objects for it name AS834. Add a route object with origin AS393498 in the RIR database for the space.1 of 673

Route objects not announced

Every route object with origin AS393498 is announced.

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.