DNS response history for gw2.nerd.jp

gw2.nerd.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 36 DNS check records, 36 successful responses, 0 failed responses, and 1652 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 gw2.nerd.jp.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

1652 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

61.206.120.94

Most recently resolved hosting IP on selected date

Successful Responses

36

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 gw2.nerd.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
36 2026-08-26 11:59 639233414056832719
1711 ms 61.206.120.94
35 2026-08-26 11:41 639233403515141099
1715 ms 61.206.120.94
34 2026-08-26 10:46 639233370841350248
1708 ms 61.206.120.94
33 2026-08-26 10:29 639233360361507238
1715 ms 61.206.120.94
32 2026-08-26 10:12 639233350067824371
1709 ms 61.206.120.94
31 2026-08-26 09:55 639233339545274518
1709 ms 61.206.120.94
30 2026-08-26 09:37 639233329214918079
1716 ms 61.206.120.94
29 2026-08-26 09:20 639233318749762337
1708 ms 61.206.120.94
28 2026-08-26 09:02 639233308387917838
1119 ms 61.206.120.94
27 2026-08-26 08:45 639233297961740122
1707 ms 61.206.120.94
26 2026-08-26 08:28 639233287487159094
1719 ms 61.206.120.94
25 2026-08-26 08:10 639233276995531707
1712 ms 61.206.120.94
24 2026-08-26 07:53 639233266521568229
1702 ms 61.206.120.94
23 2026-08-26 07:35 639233256081047431
1713 ms 61.206.120.94
22 2026-08-26 06:41 639233223620132921
1713 ms 61.206.120.94
21 2026-08-26 06:24 639233213287814244
1707 ms 61.206.120.94
20 2026-08-26 06:07 639233202925983161
1701 ms 61.206.120.94
19 2026-08-26 05:49 639233192644780696
1711 ms 61.206.120.94
18 2026-08-26 05:32 639233182401183833
1719 ms 61.206.120.94
17 2026-08-26 05:15 639233172074181051
1700 ms 61.206.120.94
16 2026-08-26 04:58 639233161808421455
1714 ms 61.206.120.94
15 2026-08-26 04:41 639233151357344052
1707 ms 61.206.120.94
14 2026-08-26 04:23 639233141034116946
1705 ms 61.206.120.94
13 2026-08-26 04:06 639233130828334142
1704 ms 61.206.120.94
12 2026-08-26 03:49 639233120373450007
1716 ms 61.206.120.94
11 2026-08-26 03:32 639233110066216193
1707 ms 61.206.120.94
10 2026-08-26 02:39 639233078065410564
1700 ms 61.206.120.94
9 2026-08-26 02:21 639233067787457832
848 ms 61.206.120.94
8 2026-08-26 02:04 639233057501801162
1707 ms 61.206.120.94
7 2026-08-26 01:47 639233047089431703
1706 ms 61.206.120.94
6 2026-08-26 01:30 639233036754790688
1126 ms 61.206.120.94
5 2026-08-26 01:13 639233026412602472
1697 ms 61.206.120.94
4 2026-08-26 00:55 639233016064066127
1704 ms 61.206.120.94
3 2026-08-26 00:38 639233005922655772
1720 ms 61.206.120.94
2 2026-08-26 00:21 639232995672256907
1705 ms 61.206.120.94
1 2026-08-26 00:04 639232985300872416
1710 ms 61.206.120.94