DNS response history for ns2.effective-ls3.com

ns2.effective-ls3.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 293 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.effective-ls3.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

293 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.89.16.121

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 ns2.effective-ls3.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:09 639232597643611557
138 ms 69.89.16.121
37 2026-08-25 12:52 639232587225721862
2194 ms 69.89.16.121
36 2026-08-25 12:34 639232576780683689
140 ms 69.89.16.121
35 2026-08-25 12:17 639232566381512620
138 ms 69.89.16.121
34 2026-08-25 12:00 639232556111768563
153 ms 69.89.16.121
33 2026-08-25 11:43 639232545839529039
256 ms 69.89.16.121
32 2026-08-25 11:25 639232535349285207
144 ms 69.89.16.121
31 2026-08-25 11:08 639232524938080723
134 ms 69.89.16.121
30 2026-08-25 10:14 639232492740373468
246 ms 69.89.16.121
29 2026-08-25 09:57 639232482235303141
134 ms 69.89.16.121
28 2026-08-25 09:39 639232471861770303
125 ms 69.89.16.121
27 2026-08-25 09:22 639232461630217327
132 ms 69.89.16.121
26 2026-08-25 09:05 639232451282965990
71 ms 69.89.16.121
25 2026-08-25 08:48 639232440814614938
28 ms 69.89.16.121
24 2026-08-25 08:30 639232430410720425
14 ms 69.89.16.121
23 2026-08-25 08:13 639232420003096185
165 ms 69.89.16.121
22 2026-08-25 07:56 639232409467287444
148 ms 69.89.16.121
21 2026-08-25 07:38 639232399077195997
241 ms 69.89.16.121
20 2026-08-25 07:21 639232388731528337
129 ms 69.89.16.121
19 2026-08-25 07:03 639232378288598612
191 ms 69.89.16.121
18 2026-08-25 06:10 639232346196373643
141 ms 69.89.16.121
17 2026-08-25 05:53 639232336112370741
138 ms 69.89.16.121
16 2026-08-25 05:37 639232326146508970
6 ms 69.89.16.121
15 2026-08-25 05:20 639232316189381720
2134 ms 69.89.16.121
14 2026-08-25 05:03 639232306217998913
124 ms 69.89.16.121
13 2026-08-25 04:47 639232296255744174
122 ms 69.89.16.121
12 2026-08-25 04:30 639232286095760789
245 ms 69.89.16.121
11 2026-08-25 04:13 639232276086186273
136 ms 69.89.16.121
10 2026-08-25 03:56 639232265900986425
123 ms 69.89.16.121
9 2026-08-25 03:39 639232255723518075
122 ms 69.89.16.121
8 2026-08-25 03:22 639232245484452890
17 ms 69.89.16.121
7 2026-08-25 03:05 639232235157175331
255 ms 69.89.16.121
6 2026-08-25 02:12 639232203197189095
2122 ms 69.89.16.121
5 2026-08-25 01:54 639232192844564298
119 ms 69.89.16.121
4 2026-08-25 01:37 639232182496008942
8 ms 69.89.16.121
3 2026-08-25 01:20 639232172197053132
3 ms 69.89.16.121
2 2026-08-25 00:27 639232140250307418
243 ms 69.89.16.121
1 2026-08-25 00:10 639232129927860324
153 ms 69.89.16.121