bgpreport

Network · data from 2026-11-12

AS132499 HKCOLO.NET-Telehouse Hong Kong CCC

Registry name: HKCOLONETLIMITED-AS-AP - HKCOLO.NET LIMITED, HK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS132499, 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.
112.213.70.0/24 Invalid: origin Other origin onlycovered by 112.213.64.0/20 68 10% 36
202.122.111.0/24 No ROA Other origin onlycovered by 202.122.96.0/20 172 26% 55
103.31.136.0/24 Valid RIR databaseAPNIC 673 100% 67
103.31.137.0/24 Valid RIR databaseAPNIC 673 100% 67
103.31.138.0/24 Valid RIR databaseAPNIC 673 100% 67
183.78.176.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.31.136.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 66
183.78.176.0/24 Valid RIR databaseAPNIC 670 100% 66
183.78.177.0/24 Valid RIR databaseAPNIC 670 100% 66
183.78.178.0/24 Valid RIR databaseAPNIC 670 100% 66

AS-SET

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

  • ROA: origin1
  • ROA: none1
  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin112.213.70.0/24ROAs covering it name AS23749, not AS132499. If AS132499 should announce it, add a ROA for AS132499.68 of 673
Route object: none112.213.70.0/24Route objects for it name AS23749. A route object for 112.213.64.0/20 with origin AS132499 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132499 in the RIR database for the space.68 of 673
ROA: none202.122.111.0/24No ROA covers it. Add a ROA for AS132499, maxLength 24.172 of 673
Route object: none202.122.111.0/24Route objects for it name AS4637, AS23749. A route object for 202.122.96.0/20 with origin AS132499 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132499 in the RIR database for the space.172 of 673

Route objects not announced

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

103.31.139.0/24APNICValid
112.213.64.0/20NTTCOM, RADBNo ROA
202.122.96.0/20NTTCOM, RADBNo 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.