DNS response history for m22.coreserver.jp

m22.coreserver.jp 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 34 DNS check records, 34 successful responses, 0 failed responses, and 142 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 m22.coreserver.jp.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

142 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.172.26.23

Most recently resolved hosting IP on selected date

Successful Responses

34

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 m22.coreserver.jp

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
34 2026-08-26 11:27 639233403515141099
46 ms 202.172.26.23
33 2026-08-26 10:32 639233370841350248
12 ms 202.172.26.23
32 2026-08-26 10:15 639233360361507238
12 ms 202.172.26.23
31 2026-08-26 09:58 639233350067824371
42 ms 202.172.26.23
30 2026-08-26 09:40 639233339545274518
2034 ms 202.172.26.23
29 2026-08-26 09:23 639233329214918079
18 ms 202.172.26.23
28 2026-08-26 09:06 639233318749762337
27 ms 202.172.26.23
27 2026-08-26 08:48 639233308387917838
20 ms 202.172.26.23
26 2026-08-26 08:31 639233297961740122
20 ms 202.172.26.23
25 2026-08-26 08:13 639233287487159094
13 ms 202.172.26.23
24 2026-08-26 07:56 639233276995531707
48 ms 202.172.26.23
23 2026-08-26 07:38 639233266521568229
2021 ms 202.172.26.23
22 2026-08-26 07:21 639233256081047431
47 ms 202.172.26.23
21 2026-08-26 06:27 639233223620132921
68 ms 202.172.26.23
20 2026-08-26 06:10 639233213287814244
25 ms 202.172.26.23
19 2026-08-26 05:52 639233202925983161
5 ms 202.172.26.23
18 2026-08-26 05:35 639233192644780696
5 ms 202.172.26.23
17 2026-08-26 05:18 639233182401183833
13 ms 202.172.26.23
16 2026-08-26 05:01 639233172074181051
34 ms 202.172.26.23
15 2026-08-26 04:44 639233161808421455
31 ms 202.172.26.23
14 2026-08-26 04:26 639233151357344052
17 ms 202.172.26.23
13 2026-08-26 04:09 639233141034116946
33 ms 202.172.26.23
12 2026-08-26 03:52 639233130828334142
4 ms 202.172.26.23
11 2026-08-26 03:35 639233120373450007
20 ms 202.172.26.23
10 2026-08-26 03:18 639233110066216193
11 ms 202.172.26.23
9 2026-08-26 02:24 639233078065410564
10 ms 202.172.26.23
8 2026-08-26 02:07 639233067787457832
41 ms 202.172.26.23
7 2026-08-26 01:50 639233057501801162
5 ms 202.172.26.23
6 2026-08-26 01:33 639233047089431703
4 ms 202.172.26.23
5 2026-08-26 01:16 639233036754790688
36 ms 202.172.26.23
4 2026-08-26 00:58 639233026412602472
39 ms 202.172.26.23
3 2026-08-26 00:41 639233016064066127
26 ms 202.172.26.23
2 2026-08-26 00:24 639233005922655772
5 ms 202.172.26.23
1 2026-08-26 00:07 639232995672256907
32 ms 202.172.26.23