DNS response history for ns2.webdynamica.net

ns2.webdynamica.net 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, 34 successful responses, 0 failed responses, and 536 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.webdynamica.net.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

536 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

212.24.101.150

Most recently resolved hosting IP on selected date

Successful Responses

34

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.webdynamica.net

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 12:01 639232556111768563
45 ms 212.24.101.150
33 2026-08-25 11:44 639232545839529039
85 ms 212.24.101.150
32 2026-08-25 11:26 639232535349285207
43 ms 212.24.101.150
31 2026-08-25 11:09 639232524938080723
89 ms 212.24.101.150
30 2026-08-25 10:15 639232492740373468
71 ms 212.24.101.150
29 2026-08-25 09:58 639232482235303141
78 ms 212.24.101.150
28 2026-08-25 09:40 639232471861770303
91 ms 212.24.101.150
27 2026-08-25 09:24 639232461630217327
2041 ms 212.24.101.150
26 2026-08-25 09:06 639232451282965990
82 ms 212.24.101.150
25 2026-08-25 08:49 639232440814614938
65 ms 212.24.101.150
24 2026-08-25 08:32 639232430410720425
2057 ms 212.24.101.150
23 2026-08-25 08:14 639232420003096185
77 ms 212.24.101.150
22 2026-08-25 07:57 639232409467287444
70 ms 212.24.101.150
21 2026-08-25 07:39 639232399077195997
42 ms 212.24.101.150
20 2026-08-25 07:22 639232388731528337
75 ms 212.24.101.150
19 2026-08-25 07:05 639232378288598612
2040 ms 212.24.101.150
18 2026-08-25 06:11 639232346196373643
87 ms 212.24.101.150
17 2026-08-25 05:54 639232336112370741
68 ms 212.24.101.150
16 2026-08-25 05:38 639232326146508970
73 ms 212.24.101.150
15 2026-08-25 05:21 639232316189381720
2042 ms 212.24.101.150
14 2026-08-25 05:05 639232306217998913
68 ms 212.24.101.150
13 2026-08-25 04:48 639232296255744174
83 ms 212.24.101.150
12 2026-08-25 04:31 639232286095760789
32 ms 212.24.101.150
11 2026-08-25 04:14 639232276086186273
81 ms 212.24.101.150
10 2026-08-25 03:57 639232265900986425
52 ms 212.24.101.150
9 2026-08-25 03:40 639232255723518075
74 ms 212.24.101.150
8 2026-08-25 03:23 639232245484452890
4041 ms 212.24.101.150
7 2026-08-25 03:06 639232235157175331
64 ms 212.24.101.150
6 2026-08-25 02:13 639232203197189095
2052 ms 212.24.101.150
5 2026-08-25 01:56 639232192844564298
68 ms 212.24.101.150
4 2026-08-25 01:38 639232182496008942
2063 ms 212.24.101.150
3 2026-08-25 01:21 639232172197053132
75 ms 212.24.101.150
2 2026-08-25 00:28 639232140250307418
77 ms 212.24.101.150
1 2026-08-25 00:11 639232129927860324
74 ms 212.24.101.150