bgpreport

Network · data from 2026-11-12

AS218919 NETWORK-EXPRESS-TECHNOLOGY-LIMITED NETWORK EXPRESS TECHNOLOGY LIMITED

Registry name: NETWORK-EXPRESS-TECHNOLOGY-LIMITED NETWORK EXPRESS TECHNOLOGY LIMITED, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS218919, 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.
143.14.55.0/24 Invalid: origin Other origin only 2 0%low visibility 1
156.252.204.0/24 Invalid: origin RIR databaseAFRINIC 1 0%low visibility 1

AS-SET

AS218919 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.

  • ROA: origin2
  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin143.14.55.0/24ROAs covering it name AS834, not AS218919. If AS218919 should announce it, add a ROA for AS218919.2 of 673
Route object: none143.14.55.0/24Route objects for it name AS834. Add a route object with origin AS218919 in the RIR database for the space.2 of 673
ROA: origin156.252.204.0/24ROAs covering it name AS17561, not AS218919. If AS218919 should announce it, add a ROA for AS218919.1 of 673

Route objects not announced

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

156.252.155.0/24AFRINICInvalid: origin
156.252.205.0/24AFRINICInvalid: origin
156.252.206.0/24AFRINICInvalid: origin

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.