DNS response history for ns2.itechbytes.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

210 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

166.117.220.151

Most recently resolved hosting IP on selected date

Successful Responses

36

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.itechbytes.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
36 2026-08-25 12:31 639232576780683689
24 ms 166.117.220.151
35 2026-08-25 12:14 639232566381512620
36 ms 166.117.220.151
34 2026-08-25 11:57 639232556111768563
92 ms 166.117.220.151
33 2026-08-25 11:40 639232545839529039
32 ms 166.117.220.151
32 2026-08-25 11:22 639232535349285207
2037 ms 166.117.220.151
31 2026-08-25 11:05 639232524938080723
46 ms 166.117.220.151
30 2026-08-25 10:11 639232492740373468
2041 ms 166.117.220.151
29 2026-08-25 09:54 639232482235303141
46 ms 166.117.220.151
28 2026-08-25 09:36 639232471861770303
18 ms 166.117.220.151
27 2026-08-25 09:19 639232461630217327
43 ms 166.117.220.151
26 2026-08-25 09:02 639232451282965990
46 ms 166.117.220.151
25 2026-08-25 08:44 639232440814614938
7 ms 166.117.220.151
24 2026-08-25 08:27 639232430410720425
51 ms 166.117.220.151
23 2026-08-25 08:10 639232420003096185
123 ms 166.117.220.151
22 2026-08-25 07:52 639232409467287444
2020 ms 166.117.220.151
21 2026-08-25 07:35 639232399077195997
24 ms 166.117.220.151
20 2026-08-25 07:18 639232388731528337
24 ms 166.117.220.151
19 2026-08-25 07:00 639232378288598612
22 ms 166.117.220.151
18 2026-08-25 06:07 639232346196373643
9 ms 166.117.220.151
17 2026-08-25 05:50 639232336112370741
36 ms 166.117.220.151
16 2026-08-25 05:33 639232326146508970
42 ms 166.117.220.151
15 2026-08-25 05:17 639232316189381720
9 ms 166.117.220.151
14 2026-08-25 05:00 639232306217998913
60 ms 166.117.220.151
13 2026-08-25 04:44 639232296255744174
73 ms 166.117.220.151
12 2026-08-25 04:27 639232286095760789
61 ms 166.117.220.151
11 2026-08-25 04:10 639232276086186273
40 ms 166.117.220.151
10 2026-08-25 03:53 639232265900986425
20 ms 166.117.220.151
9 2026-08-25 03:36 639232255723518075
24 ms 166.117.220.151
8 2026-08-25 03:19 639232245484452890
41 ms 166.117.220.151
7 2026-08-25 03:02 639232235157175331
37 ms 166.117.220.151
6 2026-08-25 02:08 639232203197189095
144 ms 166.117.220.151
5 2026-08-25 01:51 639232192844564298
25 ms 166.117.220.151
4 2026-08-25 01:34 639232182496008942
36 ms 166.117.220.151
3 2026-08-25 01:17 639232172197053132
38 ms 166.117.220.151
2 2026-08-25 00:24 639232140250307418
31 ms 166.117.220.151
1 2026-08-25 00:06 639232129927860324
109 ms 166.117.220.151