DNS response history for m30.coreserver.jp

m30.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 135 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 m30.coreserver.jp.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

135 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.172.26.31

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 m30.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:32 639233403515141099
12 ms 202.172.26.31
33 2026-08-26 10:37 639233370841350248
36 ms 202.172.26.31
32 2026-08-26 10:20 639233360361507238
47 ms 202.172.26.31
31 2026-08-26 10:03 639233350067824371
5 ms 202.172.26.31
30 2026-08-26 09:46 639233339545274518
74 ms 202.172.26.31
29 2026-08-26 09:28 639233329214918079
4 ms 202.172.26.31
28 2026-08-26 09:11 639233318749762337
13 ms 202.172.26.31
27 2026-08-26 08:53 639233308387917838
23 ms 202.172.26.31
26 2026-08-26 08:36 639233297961740122
10 ms 202.172.26.31
25 2026-08-26 08:19 639233287487159094
27 ms 202.172.26.31
24 2026-08-26 08:01 639233276995531707
9 ms 202.172.26.31
23 2026-08-26 07:44 639233266521568229
5 ms 202.172.26.31
22 2026-08-26 07:26 639233256081047431
6 ms 202.172.26.31
21 2026-08-26 06:32 639233223620132921
20 ms 202.172.26.31
20 2026-08-26 06:15 639233213287814244
22 ms 202.172.26.31
19 2026-08-26 05:58 639233202925983161
6 ms 202.172.26.31
18 2026-08-26 05:40 639233192644780696
30 ms 202.172.26.31
17 2026-08-26 05:23 639233182401183833
2018 ms 202.172.26.31
16 2026-08-26 05:06 639233172074181051
8 ms 202.172.26.31
15 2026-08-26 04:49 639233161808421455
10 ms 202.172.26.31
14 2026-08-26 04:32 639233151357344052
67 ms 202.172.26.31
13 2026-08-26 04:15 639233141034116946
26 ms 202.172.26.31
12 2026-08-26 03:57 639233130828334142
19 ms 202.172.26.31
11 2026-08-26 03:40 639233120373450007
4 ms 202.172.26.31
10 2026-08-26 03:23 639233110066216193
8 ms 202.172.26.31
9 2026-08-26 02:30 639233078065410564
4 ms 202.172.26.31
8 2026-08-26 02:12 639233067787457832
2015 ms 202.172.26.31
7 2026-08-26 01:55 639233057501801162
22 ms 202.172.26.31
6 2026-08-26 01:38 639233047089431703
17 ms 202.172.26.31
5 2026-08-26 01:21 639233036754790688
12 ms 202.172.26.31
4 2026-08-26 01:03 639233026412602472
4 ms 202.172.26.31
3 2026-08-26 00:46 639233016064066127
4 ms 202.172.26.31
2 2026-08-26 00:29 639233005922655772
13 ms 202.172.26.31
1 2026-08-26 00:12 639232995672256907
6 ms 202.172.26.31