bgpreport

Network · data from 2026-11-12

AS62300 ASN62300-AS Address Limited

Registry name: ASN62300-AS Address Limited, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS62300, 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.
37.44.199.0/24 Invalid: origin Other origin only 2 0%low visibility 2
194.34.244.0/24 Invalid: origin Other origin only 2 0%low visibility 2
178.212.78.0/24 No ROA None 2 0%low visibility 2
194.32.241.0/24 No ROA None 2 0%low visibility 2
176.100.153.0/24 No ROA RIR databaseRIPE 673 100% 66
185.78.77.0/24 No ROA RIR databaseRIPE 673 100% 66
185.177.237.0/24 No ROA RIR databaseRIPE 673 100% 66
45.93.212.0/24 No ROA RIR databaseRIPE 672 100% 66
45.93.215.0/24 No ROA RIR databaseRIPE 672 100% 66
185.232.17.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

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

  • ROA: origin2
  • ROA: none7
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: origin37.44.199.0/24ROAs covering it name AS43278, not AS62300. If AS62300 should announce it, add a ROA for AS62300.2 of 673
Route object: none37.44.199.0/24Route objects for it name AS43278. Add a route object with origin AS62300 in the RIR database for the space.2 of 673
ROA: origin194.34.244.0/24ROAs covering it name AS43278, not AS62300. If AS62300 should announce it, add a ROA for AS62300.2 of 673
Route object: none194.34.244.0/24Route objects for it name AS43278. Add a route object with origin AS62300 in the RIR database for the space.2 of 673
ROA: none178.212.78.0/24No ROA covers it. Add a ROA for AS62300, maxLength 24.2 of 673
Route object: none178.212.78.0/24No route object for it. Add a route object with origin AS62300 in the RIR database for the space.2 of 673
ROA: none194.32.241.0/24No ROA covers it. Add a ROA for AS62300, maxLength 24.2 of 673
Route object: none194.32.241.0/24No route object for it. Add a route object with origin AS62300 in the RIR database for the space.2 of 673
ROA: none176.100.153.0/24No ROA covers it. Add a ROA for AS62300, maxLength 24.673 of 673
ROA: none185.78.77.0/24No ROA covers it. Add a ROA for AS62300, maxLength 24.673 of 673
ROA: none185.177.237.0/24No ROA covers it. Add a ROA for AS62300, maxLength 24.673 of 673
ROA: none45.93.212.0/24No ROA covers it. Add a ROA for AS62300, maxLength 24.672 of 673
ROA: none45.93.215.0/24No ROA covers it. Add a ROA for AS62300, maxLength 24.672 of 673

Route objects not announced

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