DNS response history for ns2.informadns.com

ns2.informadns.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, 29 successful responses, 1 failed responses, and 301 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.informadns.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

301 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.159.1.208

Most recently resolved hosting IP on selected date

Successful Responses

29

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.informadns.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:08 639232492740373468
10 ms 162.159.1.208
29 2026-08-25 09:50 639232482235303141
28 ms 162.159.1.208
28 2026-08-25 09:33 639232471861770303
4033 ms 162.159.1.208
27 2026-08-25 09:16 639232461630217327
7 ms 162.159.1.208
26 2026-08-25 08:59 639232451282965990
70 ms 162.159.1.208
25 2026-08-25 08:41 639232440814614938
101 ms 162.159.1.208
24 2026-08-25 08:24 639232430410720425
30 ms 162.159.1.208
23 2026-08-25 08:06 639232420003096185
15 ms 162.159.1.208
22 2026-08-25 07:49 639232409467287444
9 ms 162.159.1.208
21 2026-08-25 07:32 639232399077195997
13 ms 162.159.1.208
20 2026-08-25 07:14 639232388731528337
13 ms 162.159.1.208
19 2026-08-25 06:57 639232378288598612
16 ms 162.159.1.208
18 2026-08-25 06:03 639232346196373643
29 ms 162.159.1.208
17 2026-08-25 05:47 639232336112370741
27 ms 162.159.1.208
16 2026-08-25 05:30 639232326146508970
52 ms 162.159.1.208
15 2026-08-25 05:13 639232316189381720
9 ms 162.159.1.208
14 2026-08-25 04:57 639232306217998913
-
13 2026-08-25 04:40 639232296255744174
13 ms 162.159.1.208
12 2026-08-25 04:23 639232286095760789
2069 ms 162.159.1.208
11 2026-08-25 04:07 639232276086186273
2014 ms 162.159.1.208
10 2026-08-25 03:50 639232265900986425
6 ms 162.159.1.208
9 2026-08-25 03:33 639232255723518075
7 ms 162.159.1.208
8 2026-08-25 03:16 639232245484452890
16 ms 162.159.1.208
7 2026-08-25 02:58 639232235157175331
10 ms 162.159.1.208
6 2026-08-25 02:05 639232203197189095
24 ms 162.159.1.208
5 2026-08-25 01:48 639232192844564298
23 ms 162.159.1.208
4 2026-08-25 01:30 639232182496008942
14 ms 162.159.1.208
3 2026-08-25 01:13 639232172197053132
31 ms 162.159.1.208
2 2026-08-25 00:20 639232140250307418
35 ms 162.159.1.208
1 2026-08-25 00:03 639232129927860324
12 ms 162.159.1.208