bgpreport

Network · data from 2026-11-12

AS142270 PSICL-AS-AP - ohae/posinet

Registry name: PSICL-AS-AP - ohae/posinet, HK · not in PeeringDB

5IPv4 routes 80.0% RPKI valid · 80.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
2Route objects not announced registered with origin AS142270, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS142270, 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.
199.178.127.0/24 Invalid: origin Nonecovered by 199.178.126.0/23 33 5%low visibility 22
202.71.9.0/24 Valid RIR databaseRIPE 673 100% 67
203.76.253.0/24 Valid RIR databaseAPNIC 673 100% 67
203.76.254.0/24 Valid RIR databaseAPNIC 673 100% 67
203.76.255.0/24 Valid RIR databaseAPNIC 673 100% 67

AS-SET

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

  • ROA: origin1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin199.178.127.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS142270 should announce it, add a ROA for AS142270.33 of 673
Route object: none199.178.127.0/24No route object for it. A route object for 199.178.126.0/23 with origin AS142270 covers it (filters allowing more-specifics accept it). Add a route object with origin AS142270 in the RIR database for the space.33 of 673

Route objects not announced

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

199.178.126.0/23ALTDBNo ROA
199.178.128.0/24ALTDBNo 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.