Notice: data is being updated, so some fields may be inaccurate.
Location
China, Beijing, Beiyuan (Tongzhou)
Correct ASN Owner
DataCenter Beijing Shijihulian Yuntong Network Technology Co., Ltd. . Company
DataCenter Beijing Shijihulian Yuntong Network Technology Co., Ltd. . Loading...
ASN History
Network
AS Organization
Country
First Seen
Last Seen
43.251.103.0/24
DataCenter Beijing Shijihulian Yuntong Network Technology Co., Ltd.
China
2023-03-06 12:45
2026-10-16 00:43
43.251.103.0/24
DataCenter Resisoft, Inc.
United States
2025-11-06 08:58
2025-11-25 10:07
43.251.103.0/24
DataCenter APNIC ASN block
Australia
2025-07-23 07:46
2025-11-06 08:47
43.251.103.0/24
DataCenter RuiShu Network
Hong Kong SAR China
2020-01-03 15:11
2020-01-13 04:28
43.251.103.0/24
DataCenter Shanghai Anchang Network Security Technology
China
2018-04-02 20:52
2018-05-25 23:52
43.251.103.0/24
DataCenter Forewin Telecom Group Limited
Hong Kong SAR China
2018-01-01 08:03
2018-03-07 12:09
Organization registration history
Network
Registered since
Verified / ended
No verified organization registration records
The registered organization can differ from the ASN operator. Current records show the latest verification; past records show when they ended. Unknown start dates are shown as --.
Registration History
Registry
Country
First Seen
Last Seen
--
IP Location History
Location
Time
--
Recent queriesLatest 20 per type IP PING Traceroute DNS MTR HTTP Explore recently queried IP addresses.
Open IP→ Compare round-trip latency and packet loss from different locations.
Open PING→ History opens saved results. Select “Run again” to start a new test.
Inspect route paths, hop addresses and response times from different locations.
Open Traceroute→ History opens saved results. Select “Run again” to start a new test.
Compare DNS records, resolvers and response times across locations.
Open DNS→ History opens saved results. Select “Run again” to start a new test.
Combine route tracing with repeated probes to inspect hop latency and loss. Intermediate hop rate limiting does not establish destination packet loss.
Open MTR→ History opens saved results. Select “Run again” to start a new test.
Inspect HTTP status, response headers and request timings from different locations.
Open HTTP→ History opens saved results. Select “Run again” to start a new test.