DNS response history for ns2.mserver.jp

ns2.mserver.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 38 DNS check records, 38 successful responses, 0 failed responses, and 528 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 ns2.mserver.jp.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

528 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.122.54.58

Most recently resolved hosting IP on selected date

Successful Responses

38

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 ns2.mserver.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
38 2026-08-26 12:31 639233434974187439
549 ms 153.122.54.58
37 2026-08-26 12:14 639233424567558554
545 ms 153.122.54.58
36 2026-08-26 11:57 639233414056832719
530 ms 153.122.54.58
35 2026-08-26 11:39 639233403515141099
551 ms 153.122.54.58
34 2026-08-26 10:44 639233370841350248
532 ms 153.122.54.58
33 2026-08-26 10:27 639233360361507238
567 ms 153.122.54.58
32 2026-08-26 10:10 639233350067824371
548 ms 153.122.54.58
31 2026-08-26 09:53 639233339545274518
537 ms 153.122.54.58
30 2026-08-26 09:35 639233329214918079
540 ms 153.122.54.58
29 2026-08-26 09:18 639233318749762337
574 ms 153.122.54.58
28 2026-08-26 09:00 639233308387917838
543 ms 153.122.54.58
27 2026-08-26 08:43 639233297961740122
576 ms 153.122.54.58
26 2026-08-26 08:26 639233287487159094
354 ms 153.122.54.58
25 2026-08-26 08:08 639233276995531707
564 ms 153.122.54.58
24 2026-08-26 07:51 639233266521568229
584 ms 153.122.54.58
23 2026-08-26 07:33 639233256081047431
564 ms 153.122.54.58
22 2026-08-26 06:39 639233223620132921
546 ms 153.122.54.58
21 2026-08-26 06:22 639233213287814244
558 ms 153.122.54.58
20 2026-08-26 06:05 639233202925983161
586 ms 153.122.54.58
19 2026-08-26 05:47 639233192644780696
574 ms 153.122.54.58
18 2026-08-26 05:30 639233182401183833
572 ms 153.122.54.58
17 2026-08-26 05:13 639233172074181051
552 ms 153.122.54.58
16 2026-08-26 04:56 639233161808421455
278 ms 153.122.54.58
15 2026-08-26 04:39 639233151357344052
555 ms 153.122.54.58
14 2026-08-26 04:21 639233141034116946
11 ms 153.122.54.58
13 2026-08-26 04:04 639233130828334142
561 ms 153.122.54.58
12 2026-08-26 03:47 639233120373450007
597 ms 153.122.54.58
11 2026-08-26 03:30 639233110066216193
552 ms 153.122.54.58
10 2026-08-26 02:37 639233078065410564
563 ms 153.122.54.58
9 2026-08-26 02:19 639233067787457832
522 ms 153.122.54.58
8 2026-08-26 02:02 639233057501801162
543 ms 153.122.54.58
7 2026-08-26 01:45 639233047089431703
555 ms 153.122.54.58
6 2026-08-26 01:28 639233036754790688
555 ms 153.122.54.58
5 2026-08-26 01:11 639233026412602472
520 ms 153.122.54.58
4 2026-08-26 00:53 639233016064066127
548 ms 153.122.54.58
3 2026-08-26 00:36 639233005922655772
556 ms 153.122.54.58
2 2026-08-26 00:19 639232995672256907
563 ms 153.122.54.58
1 2026-08-26 00:02 639232985300872416
552 ms 153.122.54.58