DNS response history for ns1.m-wife.jp

ns1.m-wife.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 22 DNS check records, 22 successful responses, 0 failed responses, and 396 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 ns1.m-wife.jp.
Records on Selected Date

22

Historical checks stored for this nameserver on selected date

Average Latency

396 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 06:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

133.167.111.244

Most recently resolved hosting IP on selected date

Successful Responses

22

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 ns1.m-wife.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
22 2026-08-26 06:39 639233223620132921
525 ms 133.167.111.244
21 2026-08-26 06:22 639233213287814244
3 ms 133.167.111.244
20 2026-08-26 06:05 639233202925983161
502 ms 133.167.111.244
19 2026-08-26 05:48 639233192644780696
493 ms 133.167.111.244
18 2026-08-26 05:30 639233182401183833
515 ms 133.167.111.244
17 2026-08-26 05:13 639233172074181051
13 ms 133.167.111.244
16 2026-08-26 04:56 639233161808421455
494 ms 133.167.111.244
15 2026-08-26 04:39 639233151357344052
2 ms 133.167.111.244
14 2026-08-26 04:22 639233141034116946
498 ms 133.167.111.244
13 2026-08-26 04:04 639233130828334142
493 ms 133.167.111.244
12 2026-08-26 03:47 639233120373450007
501 ms 133.167.111.244
11 2026-08-26 03:30 639233110066216193
492 ms 133.167.111.244
10 2026-08-26 02:37 639233078065410564
298 ms 133.167.111.244
9 2026-08-26 02:20 639233067787457832
489 ms 133.167.111.244
8 2026-08-26 02:02 639233057501801162
495 ms 133.167.111.244
7 2026-08-26 01:45 639233047089431703
498 ms 133.167.111.244
6 2026-08-26 01:28 639233036754790688
9 ms 133.167.111.244
5 2026-08-26 01:11 639233026412602472
307 ms 133.167.111.244
4 2026-08-26 00:53 639233016064066127
366 ms 133.167.111.244
3 2026-08-26 00:36 639233005922655772
488 ms 133.167.111.244
2 2026-08-26 00:19 639232995672256907
755 ms 133.167.111.244
1 2026-08-26 00:02 639232985300872416
485 ms 133.167.111.244