DNS response history for ns3.incisivepoint.com

ns3.incisivepoint.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 34 DNS check records, 34 successful responses, 0 failed responses, and 568 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 ns3.incisivepoint.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

568 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

101.50.1.111

Most recently resolved hosting IP on selected date

Successful Responses

34

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 ns3.incisivepoint.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
34 2026-08-25 12:06 639232556111768563
182 ms 101.50.1.111
33 2026-08-25 11:49 639232545839529039
331 ms 101.50.1.111
32 2026-08-25 11:32 639232535349285207
164 ms 101.50.1.111
31 2026-08-25 11:14 639232524938080723
171 ms 101.50.1.111
30 2026-08-25 10:20 639232492740373468
3678 ms 101.50.1.111
29 2026-08-25 10:03 639232482235303141
324 ms 101.50.1.111
28 2026-08-25 09:46 639232471861770303
329 ms 101.50.1.111
27 2026-08-25 09:28 639232461630217327
167 ms 101.50.1.111
26 2026-08-25 09:11 639232451282965990
332 ms 101.50.1.111
25 2026-08-25 08:54 639232440814614938
7 ms 101.50.1.111
24 2026-08-25 08:37 639232430410720425
2261 ms 101.50.1.111
23 2026-08-25 08:19 639232420003096185
344 ms 101.50.1.111
22 2026-08-25 08:02 639232409467287444
335 ms 101.50.1.111
21 2026-08-25 07:44 639232399077195997
328 ms 101.50.1.111
20 2026-08-25 07:27 639232388731528337
986 ms 101.50.1.111
19 2026-08-25 07:10 639232378288598612
330 ms 101.50.1.111
18 2026-08-25 06:16 639232346196373643
200 ms 101.50.1.111
17 2026-08-25 05:59 639232336112370741
342 ms 101.50.1.111
16 2026-08-25 05:42 639232326146508970
167 ms 101.50.1.111
15 2026-08-25 05:26 639232316189381720
158 ms 101.50.1.111
14 2026-08-25 05:09 639232306217998913
317 ms 101.50.1.111
13 2026-08-25 04:53 639232296255744174
171 ms 101.50.1.111
12 2026-08-25 04:36 639232286095760789
326 ms 101.50.1.111
11 2026-08-25 04:19 639232276086186273
326 ms 101.50.1.111
10 2026-08-25 04:02 639232265900986425
2243 ms 101.50.1.111
9 2026-08-25 03:45 639232255723518075
346 ms 101.50.1.111
8 2026-08-25 03:28 639232245484452890
321 ms 101.50.1.111
7 2026-08-25 03:11 639232235157175331
330 ms 101.50.1.111
6 2026-08-25 02:18 639232203197189095
183 ms 101.50.1.111
5 2026-08-25 02:01 639232192844564298
334 ms 101.50.1.111
4 2026-08-25 01:43 639232182496008942
328 ms 101.50.1.111
3 2026-08-25 01:26 639232172197053132
311 ms 101.50.1.111
2 2026-08-25 00:33 639232140250307418
2319 ms 101.50.1.111
1 2026-08-25 00:16 639232129927860324
328 ms 101.50.1.111