DNS response history for dns2.xjmu.edu.cn

dns2.xjmu.edu.cn is a DNS nameserver monitored by NameServerHistory. This page provides historical DNS response-time data, nameserver uptime signals, DNS latency observations, resolved IP history, successful response counts, failed response counts, and reliability indicators for this nameserver.

The selected UTC date is 2026-08-26. For this date, NameServerHistory found 27 DNS check records, 27 successful responses, 0 failed responses, and 1687 ms average response time. Current selected-date status: At least one successful DNS response was recorded for the selected date.

  • Use this report to investigate historical DNS uptime and nameserver reliability.
  • Compare DNS latency changes, failed DNS checks, and response behavior over time.
  • Review the latest resolved IP address and raw DNS check history for dns2.xjmu.edu.cn.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

1687 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.26.175.166

Most recently resolved hosting IP on selected date

Successful Responses

27

Checks that returned a measurable response

Failed Responses

0

Checks with no response or no returned latency

Failure Rate

0%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for dns2.xjmu.edu.cn

Showing DNS history for 2026-08-26 UTC. Newest records appear first.

Latency bars are scaled to a maximum of 5000 ms for quick visual comparison.

# Query Time (UTC) Correlation ID Latency Response IP Address
27 2026-08-26 08:46 639233297961740122
1916 ms 210.26.175.166
26 2026-08-26 08:28 639233287487159094
1865 ms 210.26.175.166
25 2026-08-26 08:11 639233276995531707
1640 ms 210.26.175.166
24 2026-08-26 07:53 639233266521568229
1879 ms 210.26.175.166
23 2026-08-26 07:36 639233256081047431
1325 ms 210.26.175.166
22 2026-08-26 06:42 639233223620132921
1892 ms 210.26.175.166
21 2026-08-26 06:24 639233213287814244
308 ms 210.26.175.166
20 2026-08-26 06:07 639233202925983161
1855 ms 210.26.175.166
19 2026-08-26 05:50 639233192644780696
1611 ms 210.26.175.166
18 2026-08-26 05:33 639233182401183833
309 ms 210.26.175.166
17 2026-08-26 05:16 639233172074181051
1614 ms 210.26.175.166
16 2026-08-26 04:58 639233161808421455
1887 ms 210.26.175.166
15 2026-08-26 04:41 639233151357344052
1612 ms 210.26.175.166
14 2026-08-26 04:24 639233141034116946
1878 ms 210.26.175.166
13 2026-08-26 04:07 639233130828334142
1893 ms 210.26.175.166
12 2026-08-26 03:50 639233120373450007
1836 ms 210.26.175.166
11 2026-08-26 03:32 639233110066216193
1895 ms 210.26.175.166
10 2026-08-26 02:39 639233078065410564
1616 ms 210.26.175.166
9 2026-08-26 02:22 639233067787457832
1616 ms 210.26.175.166
8 2026-08-26 02:05 639233057501801162
2355 ms 210.26.175.166
7 2026-08-26 01:47 639233047089431703
1864 ms 210.26.175.166
6 2026-08-26 01:30 639233036754790688
1861 ms 210.26.175.166
5 2026-08-26 01:13 639233026412602472
1532 ms 210.26.175.166
4 2026-08-26 00:56 639233016064066127
1968 ms 210.26.175.166
3 2026-08-26 00:38 639233005922655772
1862 ms 210.26.175.166
2 2026-08-26 00:21 639232995672256907
1829 ms 210.26.175.166
1 2026-08-26 00:04 639232985300872416
1827 ms 210.26.175.166