Summary

  • AS142207 remains registered in the APNIC region under WJY (Shanghai) Technology Co., Ltd., with an active registration role object at a Pudong New Area address in Shanghai; the word "administrator" in the organisation's directory entry refers to that registration role, not to insolvency proceedings. https://whois.ipip.net/AS142207
  • Per BTW Media's own editorial account, RIPEstat showed no announced prefixes, no visible neighbours and no RIS-peer visibility for AS142207 as of 2 August 2026, with a last-seen timestamp of 8 July 2026 and a last prefix of 151.158.14.0/23; those figures are attributed to that editorial, not independently re-observed for this briefing. https://btw.media/en/as142207-keeps-wjy-visible-in-the-registry-after-its-public-route-goes-quiet
  • The network's PeeringDB record links to wjy.me, a site whose own legal notice names WJY (Hong Kong) Limited — a different legal entity from the Shanghai registrant, and one whose relationship to it no inspected public record establishes. https://wjy.me/

What the registry layer establishes

The APNIC registration data for AS142207 lists the network name WJY-AS-AP, country CN, and the registrant WJY (Shanghai) Technology Co., Ltd., with organisation handle ORG-WTCL6-AP and administrative and technical contact handle WSTC2-AP. https://whois.ipip.net/AS142207 The registry role object carries the name "WJY Shanghai Technology Co Ltd administrator" at 5th Floor, 310 Jingao Road, Pudong New Area, Shanghai 200000. https://whois.ipip.net/AS142207

That role-object naming is the origin of the "administrator" in BTW's directory slug for the organisation https://btw.media/en/directory/wjy-shanghai-technology-co-ltd-administrator, and it has a mundane meaning: in RIR database conventions, an "administrator" is the designated administrative contact role for a registered object. No public insolvency, receivership or administrative notice concerning the company appeared in any source inspected for this briefing. https://whois.ipip.net/AS142207

What the routing layer shows — and who is reporting it

The strongest routing signal in the public record comes through BTW Media's earlier editorial on the autonomous system, which reports that RIPEstat showed announced=false for AS142207 at 08:00 UTC on 2 August 2026: zero visible IPv4 and IPv6 prefixes, zero observed neighbours, and no visibility among RIPE RIS peers (0 of 327 IPv4 peers, 0 of 321 IPv6 peers). The same account cites RIPEstat first-seen of 2 February 2026 and last-seen of 8 July 2026, with the last observed prefix 151.158.14.0/23. https://btw.media/en/as142207-keeps-wjy-visible-in-the-registry-after-its-public-route-goes-quiet

The evidentiary boundary matters: these RIPEstat figures are known here only through that editorial's account. The underlying queries were not re-run for this briefing, and "no announced prefixes" in a measurement view is not the same fact as "routes withdrawn everywhere" — it is consistent with withdrawal, with changes in measurement visibility, or with a network simply not originating routes in observed windows. The editorial itself stops short of resolving which. https://btw.media/en/as142207-keeps-wjy-visible-in-the-registry-after-its-public-route-goes-quiet

What the operator declares about itself

PeeringDB network record 41314 ties AS142207 to WJY (Shanghai) Technology Co., Ltd., lists the IRR as-set AS-WJY, classifies the network as Cable/DSL/ISP with global scope and an open peering policy, and carries self-declared traffic of 5-10Gbps, 100 listed IPv4 prefixes and 1,000 listed IPv6 prefixes, with a website link to wjy.me and a last-update date of 25 January 2026. https://www.peeringdb.com/net/41314 The matching PeeringDB organisation record 43054 lists the company website as wjy.me and the address as 5th Floor, 310 Jinhao Road, Pudong New Area, Shanghai 200000 — spelling the street "Jinhao Road" where the APNIC objects spell "Jingao Road". https://www.peeringdb.com/org/43054

All of this is operator-declared and unverified. It is also in tension with the observed routing history: a network claiming roughly 100 IPv4 prefixes had exactly one /23 — 151.158.14.0/23 — as its last observed prefix in the reported RIPEstat history. https://btw.media/en/as142207-keeps-wjy-visible-in-the-registry-after-its-public-route-goes-quiet

The name that does not resolve

The website wjy.me, linked from the network's own PeeringDB records, names the legal entity WJY (Hong Kong) Limited and offers LIR services, cloud services, server colocation and hosting, and IaaS. https://wjy.me/ The relationship between that Hong Kong entity and the Shanghai registrant of AS142207 is not established by any public record inspected for this briefing. https://wjy.me/ Until a corporate filing or an operator statement connects the two, the registry name and the website's legal name remain an unresolved split — a gap that matters for anyone relying on the registry entry to attribute responsibility for the ASN's resources or conduct.

One disambiguation note: a similarly named but apparently unrelated Shenzhen firm, 深圳万佳怡科技有限公司 (Shenzhen Wanjayi Technology Co., Ltd., wjytech.com), offers IT security, storage, operations and cloud solutions and lists a Shanghai branch in Xuhui District; nothing inspected links it to the AS142207 registrant. https://btw.media/zh/as142207-keeps-wjy-visible-in-the-registry-after-its-public-route-goes-quiet-zh

Where the picture stands

Three layers, three different states: the registry record is present and active; the public routing view is quiet since at least 8 July 2026 as reported; and the operator's own web presence names a different legal entity. None of these observations alone answers why the routes went quiet or who ultimately stands behind AS142207, and this briefing deliberately does not guess. What the record does support is narrower: an active APNIC registration https://whois.ipip.net/AS142207, a routing view whose silence is documented in BTW's editorial https://btw.media/en/as142207-keeps-wjy-visible-in-the-registry-after-its-public-route-goes-quiet, and operator declarations that fit the observed routing history imperfectly https://www.peeringdb.com/net/41314. Watchers of Asia-Pacific routing should treat the registry entry as evidence of registration, not of operation.