DNS response history for ns2.infoozle.com

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

30

Historical checks stored for this nameserver on selected date

Average Latency

426 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.90.162.171

Most recently resolved hosting IP on selected date

Successful Responses

30

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.infoozle.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
30 2026-08-25 10:16 639232492740373468
2112 ms 103.90.162.171
29 2026-08-25 09:59 639232482235303141
249 ms 103.90.162.171
28 2026-08-25 09:41 639232471861770303
231 ms 103.90.162.171
27 2026-08-25 09:24 639232461630217327
239 ms 103.90.162.171
26 2026-08-25 09:07 639232451282965990
225 ms 103.90.162.171
25 2026-08-25 08:49 639232440814614938
2112 ms 103.90.162.171
24 2026-08-25 08:32 639232430410720425
132 ms 103.90.162.171
23 2026-08-25 08:15 639232420003096185
233 ms 103.90.162.171
22 2026-08-25 07:57 639232409467287444
2233 ms 103.90.162.171
21 2026-08-25 07:40 639232399077195997
222 ms 103.90.162.171
20 2026-08-25 07:22 639232388731528337
10 ms 103.90.162.171
19 2026-08-25 07:05 639232378288598612
2008 ms 103.90.162.171
18 2026-08-25 06:12 639232346196373643
234 ms 103.90.162.171
17 2026-08-25 05:55 639232336112370741
241 ms 103.90.162.171
16 2026-08-25 05:38 639232326146508970
232 ms 103.90.162.171
15 2026-08-25 05:22 639232316189381720
240 ms 103.90.162.171
14 2026-08-25 05:05 639232306217998913
230 ms 103.90.162.171
13 2026-08-25 04:48 639232296255744174
122 ms 103.90.162.171
12 2026-08-25 04:32 639232286095760789
4 ms 103.90.162.171
11 2026-08-25 04:15 639232276086186273
8 ms 103.90.162.171
10 2026-08-25 03:58 639232265900986425
234 ms 103.90.162.171
9 2026-08-25 03:41 639232255723518075
111 ms 103.90.162.171
8 2026-08-25 03:24 639232245484452890
231 ms 103.90.162.171
7 2026-08-25 03:07 639232235157175331
10 ms 103.90.162.171
6 2026-08-25 02:13 639232203197189095
111 ms 103.90.162.171
5 2026-08-25 01:56 639232192844564298
126 ms 103.90.162.171
4 2026-08-25 01:39 639232182496008942
238 ms 103.90.162.171
3 2026-08-25 01:22 639232172197053132
248 ms 103.90.162.171
2 2026-08-25 00:28 639232140250307418
22 ms 103.90.162.171
1 2026-08-25 00:11 639232129927860324
121 ms 103.90.162.171