DNS response history for ns4.nameanchor.com

ns4.nameanchor.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, 33 successful responses, 1 failed responses, and 157 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 ns4.nameanchor.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

157 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:57

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.80.125.2

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns4.nameanchor.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 11:57 639232556111768563
58 ms 208.80.125.2
33 2026-08-25 11:40 639232545839529039
43 ms 208.80.125.2
32 2026-08-25 11:22 639232535349285207
15 ms 208.80.125.2
31 2026-08-25 11:05 639232524938080723
2121 ms 208.80.125.2
30 2026-08-25 10:11 639232492740373468
73 ms 208.80.125.2
29 2026-08-25 09:54 639232482235303141
13 ms 208.80.125.2
28 2026-08-25 09:36 639232471861770303
14 ms 208.80.125.2
27 2026-08-25 09:19 639232461630217327
37 ms 208.80.125.2
26 2026-08-25 09:02 639232451282965990
16 ms 208.80.125.2
25 2026-08-25 08:45 639232440814614938
38 ms 208.80.125.2
24 2026-08-25 08:27 639232430410720425
55 ms 208.80.125.2
23 2026-08-25 08:10 639232420003096185
47 ms 208.80.125.2
22 2026-08-25 07:52 639232409467287444
19 ms 208.80.125.2
21 2026-08-25 07:35 639232399077195997
26 ms 208.80.125.2
20 2026-08-25 07:18 639232388731528337
21 ms 208.80.125.2
19 2026-08-25 07:00 639232378288598612
62 ms 208.80.125.2
18 2026-08-25 06:07 639232346196373643
40 ms 208.80.125.2
17 2026-08-25 05:50 639232336112370741
24 ms 208.80.125.2
16 2026-08-25 05:33 639232326146508970
31 ms 208.80.125.2
15 2026-08-25 05:17 639232316189381720
19 ms 208.80.125.2
14 2026-08-25 05:00 639232306217998913
84 ms 208.80.125.2
13 2026-08-25 04:44 639232296255744174
10 ms 208.80.125.2
12 2026-08-25 04:27 639232286095760789
40 ms 208.80.125.2
11 2026-08-25 04:10 639232276086186273
24 ms 208.80.125.2
10 2026-08-25 03:53 639232265900986425
16 ms 208.80.125.2
9 2026-08-25 03:36 639232255723518075
23 ms 208.80.125.2
8 2026-08-25 03:19 639232245484452890
60 ms 208.80.125.2
7 2026-08-25 03:02 639232235157175331
20 ms 208.80.125.2
6 2026-08-25 02:08 639232203197189095
31 ms 208.80.125.2
5 2026-08-25 01:51 639232192844564298
-
4 2026-08-25 01:34 639232182496008942
10 ms 208.80.125.2
3 2026-08-25 01:17 639232172197053132
10 ms 208.80.125.2
2 2026-08-25 00:24 639232140250307418
10 ms 208.80.125.2
1 2026-08-25 00:06 639232129927860324
2060 ms 208.80.125.2