DNS response history for ns3.inhousepk.com

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

38

Historical checks stored for this nameserver on selected date

Average Latency

262 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

108.160.157.7

Most recently resolved hosting IP on selected date

Successful Responses

38

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.inhousepk.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
38 2026-08-25 13:00 639232587225721862
4 ms 108.160.157.7
37 2026-08-25 12:43 639232576780683689
301 ms 108.160.157.7
36 2026-08-25 12:25 639232566381512620
263 ms 108.160.157.7
35 2026-08-25 12:08 639232556111768563
266 ms 108.160.157.7
34 2026-08-25 11:51 639232545839529039
315 ms 108.160.157.7
33 2026-08-25 11:34 639232535349285207
300 ms 108.160.157.7
32 2026-08-25 11:16 639232524938080723
319 ms 108.160.157.7
31 2026-08-25 10:22 639232492740373468
177 ms 108.160.157.7
30 2026-08-25 10:05 639232482235303141
161 ms 108.160.157.7
29 2026-08-25 09:48 639232471861770303
151 ms 108.160.157.7
28 2026-08-25 09:30 639232461630217327
295 ms 108.160.157.7
27 2026-08-25 09:13 639232451282965990
313 ms 108.160.157.7
26 2026-08-25 08:56 639232440814614938
294 ms 108.160.157.7
25 2026-08-25 08:39 639232430410720425
304 ms 108.160.157.7
24 2026-08-25 08:21 639232420003096185
327 ms 108.160.157.7
23 2026-08-25 08:04 639232409467287444
143 ms 108.160.157.7
22 2026-08-25 07:46 639232399077195997
308 ms 108.160.157.7
21 2026-08-25 07:29 639232388731528337
302 ms 108.160.157.7
20 2026-08-25 07:12 639232378288598612
153 ms 108.160.157.7
19 2026-08-25 06:18 639232346196373643
325 ms 108.160.157.7
18 2026-08-25 06:01 639232336112370741
290 ms 108.160.157.7
17 2026-08-25 05:44 639232326146508970
314 ms 108.160.157.7
16 2026-08-25 05:28 639232316189381720
304 ms 108.160.157.7
15 2026-08-25 05:11 639232306217998913
298 ms 108.160.157.7
14 2026-08-25 04:54 639232296255744174
282 ms 108.160.157.7
13 2026-08-25 04:38 639232286095760789
293 ms 108.160.157.7
12 2026-08-25 04:21 639232276086186273
310 ms 108.160.157.7
11 2026-08-25 04:04 639232265900986425
153 ms 108.160.157.7
10 2026-08-25 03:47 639232255723518075
294 ms 108.160.157.7
9 2026-08-25 03:30 639232245484452890
268 ms 108.160.157.7
8 2026-08-25 03:13 639232235157175331
314 ms 108.160.157.7
7 2026-08-25 02:20 639232203197189095
316 ms 108.160.157.7
6 2026-08-25 02:03 639232192844564298
301 ms 108.160.157.7
5 2026-08-25 01:45 639232182496008942
275 ms 108.160.157.7
4 2026-08-25 01:28 639232172197053132
312 ms 108.160.157.7
3 2026-08-25 00:35 639232140250307418
300 ms 108.160.157.7
2 2026-08-25 00:18 639232129927860324
164 ms 108.160.157.7
1 2026-08-25 00:00 639232119551972438
148 ms 108.160.157.7