DNS response history for ns2.home-4me.com

ns2.home-4me.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 202 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.home-4me.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

202 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

64.113.9.83

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.home-4me.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:17 639232492740373468
204 ms 64.113.9.83
29 2026-08-25 10:00 639232482235303141
159 ms 64.113.9.83
28 2026-08-25 09:43 639232471861770303
4 ms 64.113.9.83
27 2026-08-25 09:26 639232461630217327
156 ms 64.113.9.83
26 2026-08-25 09:08 639232451282965990
165 ms 64.113.9.83
25 2026-08-25 08:51 639232440814614938
161 ms 64.113.9.83
24 2026-08-25 08:34 639232430410720425
168 ms 64.113.9.83
23 2026-08-25 08:16 639232420003096185
163 ms 64.113.9.83
22 2026-08-25 07:59 639232409467287444
161 ms 127.0.0.1
21 2026-08-25 07:42 639232399077195997
153 ms 64.113.9.83
20 2026-08-25 07:24 639232388731528337
119 ms 64.113.9.83
19 2026-08-25 07:07 639232378288598612
159 ms 64.113.9.83
18 2026-08-25 06:13 639232346196373643
164 ms 64.113.9.83
17 2026-08-25 05:56 639232336112370741
257 ms 64.113.9.83
16 2026-08-25 05:40 639232326146508970
172 ms 64.113.9.83
15 2026-08-25 05:23 639232316189381720
3 ms 64.113.9.83
14 2026-08-25 05:07 639232306217998913
343 ms 64.113.9.83
13 2026-08-25 04:50 639232296255744174
2202 ms 64.113.9.83
12 2026-08-25 04:33 639232286095760789
164 ms 64.113.9.83
11 2026-08-25 04:16 639232276086186273
164 ms 64.113.9.83
10 2026-08-25 03:59 639232265900986425
3 ms 64.113.9.83
9 2026-08-25 03:43 639232255723518075
3 ms 64.113.9.83
8 2026-08-25 03:25 639232245484452890
104 ms 64.113.9.83
7 2026-08-25 03:08 639232235157175331
163 ms 64.113.9.83
6 2026-08-25 02:15 639232203197189095
195 ms 64.113.9.83
5 2026-08-25 01:58 639232192844564298
106 ms 64.113.9.83
4 2026-08-25 01:41 639232182496008942
98 ms 64.113.9.83
3 2026-08-25 01:23 639232172197053132
157 ms 64.113.9.83
2 2026-08-25 00:30 639232140250307418
2 ms 64.113.9.83
1 2026-08-25 00:13 639232129927860324
2 ms 64.113.9.83