bgpreport

Network · data from 2026-11-12

AS151419 LINKLESS-AS-AP - LINKLESS COMMUNICATIONS LIMITED

Registry name: LINKLESS-AS-AP - LINKLESS COMMUNICATIONS LIMITED, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS151419, 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.
178.83.206.0/24 Valid Nonecovered by 178.83.206.0/23 175 26% 55
178.83.207.0/24 Valid Nonecovered by 178.83.206.0/23 175 26% 55
103.158.117.0/24 Valid RIR databaseAPNIC 670 100% 67
178.83.206.0/23 Valid RIR databaseRADB, RIPE 670 100% 67
2602:fa4f:100::/48 Valid RIR databaseARIN 636 100% 69

AS-SET

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

  • Route object: none2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none178.83.206.0/24No route object for it. A route object for 178.83.206.0/23 with origin AS151419 covers it (filters allowing more-specifics accept it). Add a route object with origin AS151419 in the RIR database for the space.175 of 673
Route object: none178.83.207.0/24No route object for it. A route object for 178.83.206.0/23 with origin AS151419 covers it (filters allowing more-specifics accept it). Add a route object with origin AS151419 in the RIR database for the space.175 of 673

Route objects not announced

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

154.88.66.0/23RADBValid
2401:e60:1::/48APNICValid
2401:e60:2::/48APNICValid
2401:e60:3::/48APNICValid

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.