DNS response history for ns2.poddarharmony.com

ns2.poddarharmony.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 36 DNS check records, 35 successful responses, 1 failed responses, and 308 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.poddarharmony.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

308 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

43.230.200.32

Most recently resolved hosting IP on selected date

Successful Responses

35

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 ns2.poddarharmony.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
36 2026-08-25 12:38 639232576780683689
4 ms 43.230.200.32
35 2026-08-25 12:21 639232566381512620
4 ms 43.230.200.32
34 2026-08-25 12:03 639232556111768563
2008 ms 43.230.200.32
33 2026-08-25 11:46 639232545839529039
253 ms 43.230.200.32
32 2026-08-25 11:29 639232535349285207
19 ms 43.230.200.32
31 2026-08-25 11:12 639232524938080723
277 ms 43.230.200.32
30 2026-08-25 10:18 639232492740373468
242 ms 43.230.200.32
29 2026-08-25 10:01 639232482235303141
245 ms 43.230.200.32
28 2026-08-25 09:43 639232471861770303
-
27 2026-08-25 09:26 639232461630217327
238 ms 43.230.200.32
26 2026-08-25 09:09 639232451282965990
248 ms 43.230.200.32
25 2026-08-25 08:51 639232440814614938
249 ms 43.230.200.32
24 2026-08-25 08:34 639232430410720425
239 ms 43.230.200.32
23 2026-08-25 08:17 639232420003096185
8 ms 43.230.200.32
22 2026-08-25 07:59 639232409467287444
248 ms 43.230.200.32
21 2026-08-25 07:42 639232399077195997
8 ms 43.230.200.32
20 2026-08-25 07:25 639232388731528337
241 ms 43.230.200.32
19 2026-08-25 07:07 639232378288598612
247 ms 43.230.200.32
18 2026-08-25 06:14 639232346196373643
191 ms 43.230.200.32
17 2026-08-25 05:57 639232336112370741
238 ms 43.230.200.32
16 2026-08-25 05:40 639232326146508970
2011 ms 43.230.200.32
15 2026-08-25 05:23 639232316189381720
162 ms 43.230.200.32
14 2026-08-25 05:07 639232306217998913
244 ms 43.230.200.32
13 2026-08-25 04:50 639232296255744174
254 ms 43.230.200.32
12 2026-08-25 04:33 639232286095760789
259 ms 43.230.200.32
11 2026-08-25 04:17 639232276086186273
246 ms 43.230.200.32
10 2026-08-25 04:00 639232265900986425
244 ms 43.230.200.32
9 2026-08-25 03:43 639232255723518075
245 ms 43.230.200.32
8 2026-08-25 03:26 639232245484452890
245 ms 43.230.200.32
7 2026-08-25 03:09 639232235157175331
255 ms 43.230.200.32
6 2026-08-25 02:15 639232203197189095
242 ms 43.230.200.32
5 2026-08-25 01:58 639232192844564298
244 ms 43.230.200.32
4 2026-08-25 01:41 639232182496008942
238 ms 43.230.200.32
3 2026-08-25 01:24 639232172197053132
278 ms 43.230.200.32
2 2026-08-25 00:30 639232140250307418
250 ms 43.230.200.32
1 2026-08-25 00:13 639232129927860324
154 ms 43.230.200.32