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-28. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 241 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

28

Historical checks stored for this nameserver on selected date

Average Latency

241 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 11:33

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

28

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-28 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
28 2026-08-28 11:33 639235132147470568
15 ms 202.172.26.31
27 2026-08-28 11:16 639235121907744088
7 ms 202.172.26.31
26 2026-08-28 10:59 639235111428014262
49 ms 202.172.26.31
25 2026-08-28 10:41 639235100921813626
12 ms 202.172.26.31
24 2026-08-28 09:47 639235068670703481
10 ms 202.172.26.31
23 2026-08-28 09:30 639235058337459445
18 ms 202.172.26.31
22 2026-08-28 09:12 639235047825109146
29 ms 202.172.26.31
21 2026-08-28 08:55 639235037383229033
30 ms 202.172.26.31
20 2026-08-28 08:02 639235005619242711
2254 ms 202.172.26.31
19 2026-08-28 07:45 639234995310346584
7 ms 202.172.26.31
18 2026-08-28 07:28 639234984946548933
35 ms 202.172.26.31
17 2026-08-28 07:10 639234974608077290
22 ms 202.172.26.31
16 2026-08-28 06:17 639234942529845595
48 ms 202.172.26.31
15 2026-08-28 06:00 639234932259126627
2070 ms 202.172.26.31
14 2026-08-28 05:43 639234921916735988
5 ms 202.172.26.31
13 2026-08-28 05:25 639234911470038027
39 ms 202.172.26.31
12 2026-08-28 04:32 639234879588411654
3 ms 202.172.26.31
11 2026-08-28 04:15 639234869341589104
4 ms 202.172.26.31
10 2026-08-28 03:58 639234859012216675
7 ms 202.172.26.31
9 2026-08-28 03:40 639234848695364934
2013 ms 202.172.26.31
8 2026-08-28 02:48 639234816952458162
4 ms 202.172.26.31
7 2026-08-28 02:31 639234806773081598
6 ms 202.172.26.31
6 2026-08-28 02:13 639234796382955255
4 ms 202.172.26.31
5 2026-08-28 01:56 639234786015782563
36 ms 202.172.26.31
4 2026-08-28 01:02 639234753811917646
7 ms 202.172.26.31
3 2026-08-28 00:46 639234743739767811
4 ms 202.172.26.31
2 2026-08-28 00:28 639234733372362811
4 ms 202.172.26.31
1 2026-08-28 00:11 639234723048550337
9 ms 202.172.26.31