DNS response history for ns2.dataverge.com

ns2.dataverge.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 37 DNS check records, 36 successful responses, 1 failed responses, and 249 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.dataverge.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

249 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:52

All timestamps shown in UTC

Latest Resolved IP on Selected Date

192.157.80.8

Most recently resolved hosting IP on selected date

Successful Responses

36

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.dataverge.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
37 2026-08-25 12:52 639232587225721862
125 ms 192.157.80.8
36 2026-08-25 12:35 639232576780683689
200 ms 192.157.80.8
35 2026-08-25 12:18 639232566381512620
7 ms 192.157.80.8
34 2026-08-25 12:00 639232556111768563
188 ms 192.157.80.8
33 2026-08-25 11:43 639232545839529039
200 ms 192.157.80.8
32 2026-08-25 11:26 639232535349285207
170 ms 192.157.80.8
31 2026-08-25 11:08 639232524938080723
105 ms 192.157.80.8
30 2026-08-25 10:15 639232492740373468
158 ms 192.157.80.8
29 2026-08-25 09:58 639232482235303141
-
28 2026-08-25 09:40 639232471861770303
191 ms 192.157.80.8
27 2026-08-25 09:23 639232461630217327
96 ms 192.157.80.8
26 2026-08-25 09:06 639232451282965990
210 ms 192.157.80.8
25 2026-08-25 08:48 639232440814614938
189 ms 192.157.80.8
24 2026-08-25 08:31 639232430410720425
131 ms 192.157.80.8
23 2026-08-25 08:14 639232420003096185
140 ms 192.157.80.8
22 2026-08-25 07:56 639232409467287444
2148 ms 192.157.80.8
21 2026-08-25 07:39 639232399077195997
211 ms 192.157.80.8
20 2026-08-25 07:21 639232388731528337
186 ms 192.157.80.8
19 2026-08-25 07:04 639232378288598612
193 ms 192.157.80.8
18 2026-08-25 06:11 639232346196373643
190 ms 192.157.80.8
17 2026-08-25 05:54 639232336112370741
34 ms 192.157.80.8
16 2026-08-25 05:37 639232326146508970
98 ms 192.157.80.8
15 2026-08-25 05:20 639232316189381720
2008 ms 192.157.80.8
14 2026-08-25 05:04 639232306217998913
131 ms 192.157.80.8
13 2026-08-25 04:47 639232296255744174
103 ms 192.157.80.8
12 2026-08-25 04:30 639232286095760789
129 ms 192.157.80.8
11 2026-08-25 04:14 639232276086186273
90 ms 192.157.80.8
10 2026-08-25 03:57 639232265900986425
94 ms 192.157.80.8
9 2026-08-25 03:40 639232255723518075
195 ms 192.157.80.8
8 2026-08-25 03:23 639232245484452890
96 ms 192.157.80.8
7 2026-08-25 03:06 639232235157175331
97 ms 192.157.80.8
6 2026-08-25 02:12 639232203197189095
106 ms 192.157.80.8
5 2026-08-25 01:55 639232192844564298
103 ms 192.157.80.8
4 2026-08-25 01:38 639232182496008942
201 ms 192.157.80.8
3 2026-08-25 01:20 639232172197053132
180 ms 192.157.80.8
2 2026-08-25 00:27 639232140250307418
186 ms 192.157.80.8
1 2026-08-25 00:10 639232129927860324
92 ms 192.157.80.8