DNS response history for ns2.inforcyber.com

ns2.inforcyber.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, 27 successful responses, 1 failed responses, and 73 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.inforcyber.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

73 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

94.46.135.72

Most recently resolved hosting IP on selected date

Successful Responses

27

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

4%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.inforcyber.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:40 639232471861770303
56 ms 94.46.135.72
27 2026-08-25 09:23 639232461630217327
94 ms 94.46.135.72
26 2026-08-25 09:06 639232451282965990
86 ms 94.46.135.72
25 2026-08-25 08:49 639232440814614938
45 ms 94.46.135.72
24 2026-08-25 08:31 639232430410720425
95 ms 94.46.135.72
23 2026-08-25 08:14 639232420003096185
102 ms 94.46.135.72
22 2026-08-25 07:57 639232409467287444
56 ms 94.46.135.72
21 2026-08-25 07:39 639232399077195997
103 ms 94.46.135.72
20 2026-08-25 07:22 639232388731528337
15 ms 94.46.135.72
19 2026-08-25 07:04 639232378288598612
15 ms 94.46.135.72
18 2026-08-25 06:11 639232346196373643
63 ms 94.46.135.72
17 2026-08-25 05:54 639232336112370741
55 ms 94.46.135.72
16 2026-08-25 05:38 639232326146508970
91 ms 94.46.135.72
15 2026-08-25 05:21 639232316189381720
100 ms 94.46.135.72
14 2026-08-25 05:04 639232306217998913
8 ms 94.46.135.72
13 2026-08-25 04:48 639232296255744174
101 ms 94.46.135.72
12 2026-08-25 04:31 639232286095760789
-
11 2026-08-25 04:14 639232276086186273
88 ms 94.46.135.72
10 2026-08-25 03:57 639232265900986425
90 ms 94.46.135.72
9 2026-08-25 03:40 639232255723518075
176 ms 94.46.135.72
8 2026-08-25 03:23 639232245484452890
35 ms 94.46.135.72
7 2026-08-25 03:06 639232235157175331
92 ms 94.46.135.72
6 2026-08-25 02:13 639232203197189095
75 ms 94.46.135.72
5 2026-08-25 01:56 639232192844564298
8 ms 94.46.135.72
4 2026-08-25 01:38 639232182496008942
87 ms 94.46.135.72
3 2026-08-25 01:21 639232172197053132
90 ms 94.46.135.72
2 2026-08-25 00:28 639232140250307418
92 ms 94.46.135.72
1 2026-08-25 00:11 639232129927860324
53 ms 94.46.135.72