DNS response history for ns2.dnsreply.com

ns2.dnsreply.com 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 429 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.dnsreply.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

429 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:29

All timestamps shown in UTC

Latest Resolved IP on Selected Date

52.0.239.131

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.dnsreply.com

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:29 639233434974187439
9 ms 52.0.239.131
37 2026-08-26 12:12 639233424567558554
118 ms 52.0.239.131
36 2026-08-26 11:54 639233414056832719
182 ms 52.0.239.131
35 2026-08-26 11:37 639233403515141099
184 ms 52.0.239.131
34 2026-08-26 10:42 639233370841350248
92 ms 52.0.239.131
33 2026-08-26 10:25 639233360361507238
134 ms 52.0.239.131
32 2026-08-26 10:07 639233350067824371
183 ms 52.0.239.131
31 2026-08-26 09:50 639233339545274518
457 ms 52.0.239.131
30 2026-08-26 09:33 639233329214918079
114 ms 52.0.239.131
29 2026-08-26 09:16 639233318749762337
459 ms 52.0.239.131
28 2026-08-26 08:58 639233308387917838
181 ms 52.0.239.131
27 2026-08-26 08:41 639233297961740122
464 ms 52.0.239.131
26 2026-08-26 08:23 639233287487159094
97 ms 52.0.239.131
25 2026-08-26 08:06 639233276995531707
450 ms 52.0.239.131
24 2026-08-26 07:48 639233266521568229
476 ms 52.0.239.131
23 2026-08-26 07:31 639233256081047431
119 ms 52.0.239.131
22 2026-08-26 06:37 639233223620132921
90 ms 52.0.239.131
21 2026-08-26 06:20 639233213287814244
177 ms 52.0.239.131
20 2026-08-26 06:02 639233202925983161
362 ms 52.0.239.131
19 2026-08-26 05:45 639233192644780696
105 ms 52.0.239.131
18 2026-08-26 05:28 639233182401183833
523 ms 52.0.239.131
17 2026-08-26 05:11 639233172074181051
90 ms 52.0.239.131
16 2026-08-26 04:54 639233161808421455
178 ms 52.0.239.131
15 2026-08-26 04:37 639233151357344052
112 ms 52.0.239.131
14 2026-08-26 04:19 639233141034116946
101 ms 52.0.239.131
13 2026-08-26 04:02 639233130828334142
4217 ms 52.0.239.131
12 2026-08-26 03:45 639233120373450007
363 ms 52.0.239.131
11 2026-08-26 03:28 639233110066216193
361 ms 52.0.239.131
10 2026-08-26 02:34 639233078065410564
92 ms 52.0.239.131
9 2026-08-26 02:17 639233067787457832
365 ms 52.0.239.131
8 2026-08-26 02:00 639233057501801162
451 ms 52.0.239.131
7 2026-08-26 01:43 639233047089431703
179 ms 52.0.239.131
6 2026-08-26 01:25 639233036754790688
2209 ms 52.0.239.131
5 2026-08-26 01:08 639233026412602472
177 ms 52.0.239.131
4 2026-08-26 00:51 639233016064066127
110 ms 52.0.239.131
3 2026-08-26 00:34 639233005922655772
91 ms 52.0.239.131
2 2026-08-26 00:17 639232995672256907
182 ms 52.0.239.131
1 2026-08-26 00:00 639232985300872416
2032 ms 52.0.239.131