DNS response history for ns2.datasignalreport.com

ns2.datasignalreport.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-25. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 339 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.datasignalreport.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

339 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

70.98.79.72

Most recently resolved hosting IP on selected date

Successful Responses

33

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

Showing DNS history for 2026-08-25 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
33 2026-08-25 11:46 639232545839529039
310 ms 70.98.79.72
32 2026-08-25 11:29 639232535349285207
317 ms 70.98.79.72
31 2026-08-25 11:11 639232524938080723
322 ms 70.98.79.72
30 2026-08-25 10:17 639232492740373468
311 ms 70.98.79.72
29 2026-08-25 10:00 639232482235303141
313 ms 70.98.79.72
28 2026-08-25 09:43 639232471861770303
322 ms 70.98.79.72
27 2026-08-25 09:25 639232461630217327
321 ms 70.98.79.72
26 2026-08-25 09:08 639232451282965990
313 ms 70.98.79.72
25 2026-08-25 08:51 639232440814614938
326 ms 70.98.79.72
24 2026-08-25 08:34 639232430410720425
319 ms 70.98.79.72
23 2026-08-25 08:16 639232420003096185
314 ms 70.98.79.72
22 2026-08-25 07:59 639232409467287444
310 ms 70.98.79.72
21 2026-08-25 07:41 639232399077195997
324 ms 70.98.79.72
20 2026-08-25 07:24 639232388731528337
315 ms 70.98.79.72
19 2026-08-25 07:07 639232378288598612
316 ms 70.98.79.72
18 2026-08-25 06:13 639232346196373643
303 ms 70.98.79.72
17 2026-08-25 05:56 639232336112370741
306 ms 70.98.79.72
16 2026-08-25 05:40 639232326146508970
335 ms 70.98.79.72
15 2026-08-25 05:23 639232316189381720
308 ms 70.98.79.72
14 2026-08-25 05:07 639232306217998913
7 ms 70.98.79.72
13 2026-08-25 04:50 639232296255744174
312 ms 70.98.79.72
12 2026-08-25 04:33 639232286095760789
313 ms 70.98.79.72
11 2026-08-25 04:16 639232276086186273
167 ms 70.98.79.72
10 2026-08-25 03:59 639232265900986425
304 ms 70.98.79.72
9 2026-08-25 03:42 639232255723518075
160 ms 70.98.79.72
8 2026-08-25 03:25 639232245484452890
300 ms 70.98.79.72
7 2026-08-25 03:08 639232235157175331
317 ms 70.98.79.72
6 2026-08-25 02:15 639232203197189095
304 ms 70.98.79.72
5 2026-08-25 01:58 639232192844564298
302 ms 70.98.79.72
4 2026-08-25 01:40 639232182496008942
307 ms 70.98.79.72
3 2026-08-25 01:23 639232172197053132
14 ms 70.98.79.72
2 2026-08-25 00:30 639232140250307418
182 ms 70.98.79.72
1 2026-08-25 00:13 639232129927860324
2179 ms 70.98.79.72