bgpreport

Network · data from 2026-11-12

AS135067 LOGICOM

Registry name: LOGICOM-AS-AP - LOGICOM TECHNOLOGY CO.,LIMITED, HK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS135067, 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.
134.168.239.0/24 Valid RIR databaseRIPE 670 100% 67

AS-SET

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

  • Route object: not announced13

Route objects not announced

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

27.254.8.0/24APNICValid
27.254.14.0/24APNICValid
27.254.229.0/24APNICValid
103.207.93.0/24NTTCOM, RADBNo ROA
103.208.1.0/24RADBNo ROA
203.172.68.0/24APNICValid
2001:df3:bc80::/48RADBNo ROA
2001:df3:bc81::/48RADBNo ROA
2001:df6:3100::/48RADBNo ROA
2405:9800:ca06::/48APNICValid
2405:9800:ca07::/48APNICValid
2405:9800:ca08::/48APNICValid
2405:9800:ca09::/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.