DNS response history for ns2.m-edge.co.jp

ns2.m-edge.co.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 39 DNS check records, 39 successful responses, 0 failed responses, and 442 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.m-edge.co.jp.
Records on Selected Date

39

Historical checks stored for this nameserver on selected date

Average Latency

442 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:49

All timestamps shown in UTC

Latest Resolved IP on Selected Date

172.104.77.64

Most recently resolved hosting IP on selected date

Successful Responses

39

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.m-edge.co.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
39 2026-08-26 12:49 639233445367152284
246 ms 172.104.77.64
38 2026-08-26 12:32 639233434974187439
258 ms 172.104.77.64
37 2026-08-26 12:14 639233424567558554
532 ms 172.104.77.64
36 2026-08-26 11:57 639233414056832719
398 ms 172.104.77.64
35 2026-08-26 11:39 639233403515141099
522 ms 172.104.77.64
34 2026-08-26 10:44 639233370841350248
637 ms 172.104.77.64
33 2026-08-26 10:27 639233360361507238
563 ms 172.104.77.64
32 2026-08-26 10:10 639233350067824371
241 ms 172.104.77.64
31 2026-08-26 09:53 639233339545274518
930 ms 172.104.77.64
30 2026-08-26 09:35 639233329214918079
253 ms 172.104.77.64
29 2026-08-26 09:18 639233318749762337
503 ms 172.104.77.64
28 2026-08-26 09:00 639233308387917838
541 ms 172.104.77.64
27 2026-08-26 08:43 639233297961740122
536 ms 172.104.77.64
26 2026-08-26 08:26 639233287487159094
674 ms 172.104.77.64
25 2026-08-26 08:08 639233276995531707
516 ms 172.104.77.64
24 2026-08-26 07:51 639233266521568229
320 ms 172.104.77.64
23 2026-08-26 07:33 639233256081047431
251 ms 172.104.77.64
22 2026-08-26 06:39 639233223620132921
489 ms 172.104.77.64
21 2026-08-26 06:22 639233213287814244
508 ms 172.104.77.64
20 2026-08-26 06:05 639233202925983161
495 ms 172.104.77.64
19 2026-08-26 05:47 639233192644780696
259 ms 172.104.77.64
18 2026-08-26 05:30 639233182401183833
512 ms 172.104.77.64
17 2026-08-26 05:13 639233172074181051
253 ms 172.104.77.64
16 2026-08-26 04:56 639233161808421455
259 ms 172.104.77.64
15 2026-08-26 04:39 639233151357344052
720 ms 172.104.77.64
14 2026-08-26 04:21 639233141034116946
513 ms 172.104.77.64
13 2026-08-26 04:04 639233130828334142
500 ms 172.104.77.64
12 2026-08-26 03:47 639233120373450007
686 ms 172.104.77.64
11 2026-08-26 03:30 639233110066216193
508 ms 172.104.77.64
10 2026-08-26 02:37 639233078065410564
503 ms 172.104.77.64
9 2026-08-26 02:19 639233067787457832
270 ms 172.104.77.64
8 2026-08-26 02:02 639233057501801162
243 ms 172.104.77.64
7 2026-08-26 01:45 639233047089431703
346 ms 172.104.77.64
6 2026-08-26 01:28 639233036754790688
481 ms 172.104.77.64
5 2026-08-26 01:11 639233026412602472
246 ms 172.104.77.64
4 2026-08-26 00:53 639233016064066127
252 ms 172.104.77.64
3 2026-08-26 00:36 639233005922655772
510 ms 172.104.77.64
2 2026-08-26 00:19 639232995672256907
514 ms 172.104.77.64
1 2026-08-26 00:02 639232985300872416
248 ms 172.104.77.64