DNS response history for ns2.inetnw.com

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

38

Historical checks stored for this nameserver on selected date

Average Latency

566 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

63.142.198.216

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.inetnw.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
38 2026-08-25 12:59 639232587225721862
313 ms 63.142.198.216
37 2026-08-25 12:42 639232576780683689
324 ms 63.142.198.216
36 2026-08-25 12:24 639232566381512620
325 ms 63.142.198.216
35 2026-08-25 12:07 639232556111768563
4 ms 63.142.198.216
34 2026-08-25 11:50 639232545839529039
331 ms 63.142.198.216
33 2026-08-25 11:33 639232535349285207
314 ms 63.142.198.216
32 2026-08-25 11:15 639232524938080723
158 ms 63.142.198.216
31 2026-08-25 10:21 639232492740373468
338 ms 63.142.198.216
30 2026-08-25 10:04 639232482235303141
160 ms 63.142.198.216
29 2026-08-25 09:47 639232471861770303
5 ms 63.142.198.216
28 2026-08-25 09:30 639232461630217327
342 ms 63.142.198.216
27 2026-08-25 09:12 639232451282965990
340 ms 63.142.198.216
26 2026-08-25 08:55 639232440814614938
324 ms 63.142.198.216
25 2026-08-25 08:38 639232430410720425
157 ms 63.142.198.216
24 2026-08-25 08:20 639232420003096185
317 ms 63.142.198.216
23 2026-08-25 08:03 639232409467287444
931 ms 63.142.198.216
22 2026-08-25 07:46 639232399077195997
342 ms 63.142.198.216
21 2026-08-25 07:28 639232388731528337
3 ms 63.142.198.216
20 2026-08-25 07:11 639232378288598612
324 ms 63.142.198.216
19 2026-08-25 06:17 639232346196373643
4 ms 63.142.198.216
18 2026-08-25 06:00 639232336112370741
165 ms 63.142.198.216
17 2026-08-25 05:44 639232326146508970
333 ms 63.142.198.216
16 2026-08-25 05:27 639232316189381720
2171 ms 63.142.198.216
15 2026-08-25 05:10 639232306217998913
160 ms 63.142.198.216
14 2026-08-25 04:54 639232296255744174
4335 ms 63.142.198.216
13 2026-08-25 04:37 639232286095760789
314 ms 63.142.198.216
12 2026-08-25 04:20 639232276086186273
175 ms 63.142.198.216
11 2026-08-25 04:03 639232265900986425
161 ms 63.142.198.216
10 2026-08-25 03:46 639232255723518075
336 ms 63.142.198.216
9 2026-08-25 03:29 639232245484452890
4171 ms 63.142.198.216
8 2026-08-25 03:12 639232235157175331
2174 ms 63.142.198.216
7 2026-08-25 02:19 639232203197189095
174 ms 63.142.198.216
6 2026-08-25 02:02 639232192844564298
316 ms 63.142.198.216
5 2026-08-25 01:45 639232182496008942
315 ms 63.142.198.216
4 2026-08-25 01:27 639232172197053132
3 ms 63.142.198.216
3 2026-08-25 00:34 639232140250307418
348 ms 63.142.198.216
2 2026-08-25 00:17 639232129927860324
352 ms 63.142.198.216
1 2026-08-25 00:00 639232119551972438
155 ms 63.142.198.216