DNS response history for ns2.indivisionnetwork.com

ns2.indivisionnetwork.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, 32 successful responses, 1 failed responses, and 219 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.indivisionnetwork.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

219 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

198.199.67.170

Most recently resolved hosting IP on selected date

Successful Responses

32

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.indivisionnetwork.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:36 639232545839529039
82 ms 198.199.67.170
32 2026-08-25 11:18 639232535349285207
2041 ms 198.199.67.170
31 2026-08-25 11:01 639232524938080723
343 ms 198.199.67.170
30 2026-08-25 10:07 639232492740373468
45 ms 198.199.67.170
29 2026-08-25 09:50 639232482235303141
19 ms 198.199.67.170
28 2026-08-25 09:33 639232471861770303
79 ms 198.199.67.170
27 2026-08-25 09:16 639232461630217327
21 ms 198.199.67.170
26 2026-08-25 08:58 639232451282965990
57 ms 198.199.67.170
25 2026-08-25 08:41 639232440814614938
66 ms 198.199.67.170
24 2026-08-25 08:24 639232430410720425
126 ms 198.199.67.170
23 2026-08-25 08:06 639232420003096185
36 ms 198.199.67.170
22 2026-08-25 07:49 639232409467287444
81 ms 198.199.67.170
21 2026-08-25 07:31 639232399077195997
63 ms 198.199.67.170
20 2026-08-25 07:14 639232388731528337
-
19 2026-08-25 06:57 639232378288598612
285 ms 198.199.67.170
18 2026-08-25 06:03 639232346196373643
149 ms 198.199.67.170
17 2026-08-25 05:46 639232336112370741
112 ms 198.199.67.170
16 2026-08-25 05:30 639232326146508970
109 ms 198.199.67.170
15 2026-08-25 05:13 639232316189381720
29 ms 198.199.67.170
14 2026-08-25 04:57 639232306217998913
2028 ms 198.199.67.170
13 2026-08-25 04:40 639232296255744174
103 ms 198.199.67.170
12 2026-08-25 04:23 639232286095760789
33 ms 198.199.67.170
11 2026-08-25 04:06 639232276086186273
41 ms 198.199.67.170
10 2026-08-25 03:49 639232265900986425
11 ms 198.199.67.170
9 2026-08-25 03:32 639232255723518075
27 ms 198.199.67.170
8 2026-08-25 03:15 639232245484452890
33 ms 198.199.67.170
7 2026-08-25 02:58 639232235157175331
323 ms 198.199.67.170
6 2026-08-25 02:05 639232203197189095
77 ms 198.199.67.170
5 2026-08-25 01:48 639232192844564298
158 ms 198.199.67.170
4 2026-08-25 01:30 639232182496008942
77 ms 198.199.67.170
3 2026-08-25 01:13 639232172197053132
104 ms 198.199.67.170
2 2026-08-25 00:20 639232140250307418
18 ms 198.199.67.170
1 2026-08-25 00:03 639232129927860324
222 ms 198.199.67.170