DNS response history for ns2.infowatch.com

ns2.infowatch.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 28 DNS check records, 28 successful responses, 0 failed responses, and 225 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.infowatch.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

225 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:37

All timestamps shown in UTC

Latest Resolved IP on Selected Date

217.67.180.188

Most recently resolved hosting IP on selected date

Successful Responses

28

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.infowatch.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
28 2026-08-25 09:37 639232471861770303
82 ms 217.67.180.188
27 2026-08-25 09:20 639232461630217327
100 ms 217.67.180.188
26 2026-08-25 09:03 639232451282965990
163 ms 217.67.180.188
25 2026-08-25 08:46 639232440814614938
136 ms 217.67.180.188
24 2026-08-25 08:28 639232430410720425
111 ms 217.67.180.188
23 2026-08-25 08:11 639232420003096185
60 ms 217.67.180.188
22 2026-08-25 07:54 639232409467287444
110 ms 217.67.180.188
21 2026-08-25 07:36 639232399077195997
133 ms 217.67.180.188
20 2026-08-25 07:19 639232388731528337
48 ms 217.67.180.188
19 2026-08-25 07:02 639232378288598612
2023 ms 217.67.180.188
18 2026-08-25 06:08 639232346196373643
120 ms 217.67.180.188
17 2026-08-25 05:51 639232336112370741
57 ms 217.67.180.188
16 2026-08-25 05:35 639232326146508970
55 ms 217.67.180.188
15 2026-08-25 05:18 639232316189381720
2075 ms 217.67.180.188
14 2026-08-25 05:02 639232306217998913
54 ms 217.67.180.188
13 2026-08-25 04:45 639232296255744174
118 ms 217.67.180.188
12 2026-08-25 04:28 639232286095760789
50 ms 217.67.180.188
11 2026-08-25 04:11 639232276086186273
66 ms 217.67.180.188
10 2026-08-25 03:54 639232265900986425
58 ms 217.67.180.188
9 2026-08-25 03:37 639232255723518075
58 ms 217.67.180.188
8 2026-08-25 03:20 639232245484452890
83 ms 217.67.180.188
7 2026-08-25 03:03 639232235157175331
122 ms 217.67.180.188
6 2026-08-25 02:10 639232203197189095
110 ms 217.67.180.188
5 2026-08-25 01:53 639232192844564298
120 ms 217.67.180.188
4 2026-08-25 01:35 639232182496008942
54 ms 217.67.180.188
3 2026-08-25 01:18 639232172197053132
7 ms 217.67.180.188
2 2026-08-25 00:25 639232140250307418
9 ms 217.67.180.188
1 2026-08-25 00:08 639232129927860324
117 ms 217.67.180.188