bgpreport

Network · data from 2026-11-12

AS149662 Hostnet Data Global

Registry name: IDNIC-HOSTNETGLOBAL-AS-ID - PT Hostnet Data Global, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS149662, 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.
2400:f220::/32 No ROA Other IRR onlyRADB 635 100% 70
103.184.178.0/24 Valid None 673 100% 69
103.184.179.0/24 Valid None 673 100% 69
103.188.254.0/24 Valid None 673 100% 69
114.199.80.0/24 Valid Other IRR onlyRADB 673 100% 69
160.25.162.0/23 Valid Other IRR onlyRADB 673 100% 68
160.25.162.0/24 Valid Other IRR onlyRADB 673 100% 69
160.25.163.0/24 Valid Other IRR onlyRADB 673 100% 69

AS-SET

PeeringDB's irr_as_set for AS149662: AS149662:AS-HOSTNET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS149662 isn't in the set, or no route object for AS149662 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS149662 in itNot covered
AS149662:AS-HOSTNET In no IRR database read today.

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

  • ROA: none1
  • Route object: none3
  • Route object: RIR5
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: none2400:f220::/32No ROA covers it. Add a ROA for AS149662, maxLength 32.635 of 636
Route object: RIR2400:f220::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: none103.184.178.0/24No route object for it. Add a route object with origin AS149662 in the RIR database for the space.673 of 673
Route object: none103.184.179.0/24No route object for it. Add a route object with origin AS149662 in the RIR database for the space.673 of 673
Route object: none103.188.254.0/24No route object for it. Add a route object with origin AS149662 in the RIR database for the space.673 of 673
Route object: RIR114.199.80.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR160.25.162.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR160.25.162.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR160.25.163.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
AS-SET: not foundAS149662:AS-HOSTNETPeeringDB names AS149662:AS-HOSTNET; no IRR database read has it.

Route objects not announced

Every route object with origin AS149662 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.