DNS response history for ns2.webarda.com

ns2.webarda.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 37 DNS check records, 37 successful responses, 0 failed responses, and 280 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.webarda.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

280 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

216.120.147.200

Most recently resolved hosting IP on selected date

Successful Responses

37

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.webarda.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
37 2026-08-25 12:42 639232576780683689
169 ms 216.120.147.200
36 2026-08-25 12:25 639232566381512620
165 ms 216.120.147.200
35 2026-08-25 12:08 639232556111768563
314 ms 216.120.147.200
34 2026-08-25 11:51 639232545839529039
320 ms 216.120.147.200
33 2026-08-25 11:33 639232535349285207
175 ms 216.120.147.200
32 2026-08-25 11:16 639232524938080723
359 ms 216.120.147.200
31 2026-08-25 10:22 639232492740373468
319 ms 216.120.147.200
30 2026-08-25 10:05 639232482235303141
381 ms 216.120.147.200
29 2026-08-25 09:47 639232471861770303
357 ms 216.120.147.200
28 2026-08-25 09:30 639232461630217327
368 ms 216.120.147.200
27 2026-08-25 09:13 639232451282965990
166 ms 216.120.147.200
26 2026-08-25 08:56 639232440814614938
346 ms 216.120.147.200
25 2026-08-25 08:38 639232430410720425
344 ms 216.120.147.200
24 2026-08-25 08:21 639232420003096185
163 ms 216.120.147.200
23 2026-08-25 08:04 639232409467287444
327 ms 216.120.147.200
22 2026-08-25 07:46 639232399077195997
328 ms 216.120.147.200
21 2026-08-25 07:29 639232388731528337
162 ms 216.120.147.200
20 2026-08-25 07:12 639232378288598612
166 ms 216.120.147.200
19 2026-08-25 06:18 639232346196373643
172 ms 216.120.147.200
18 2026-08-25 06:01 639232336112370741
338 ms 216.120.147.200
17 2026-08-25 05:44 639232326146508970
164 ms 216.120.147.200
16 2026-08-25 05:28 639232316189381720
324 ms 216.120.147.200
15 2026-08-25 05:11 639232306217998913
342 ms 216.120.147.200
14 2026-08-25 04:54 639232296255744174
173 ms 216.120.147.200
13 2026-08-25 04:38 639232286095760789
201 ms 216.120.147.200
12 2026-08-25 04:21 639232276086186273
329 ms 216.120.147.200
11 2026-08-25 04:04 639232265900986425
342 ms 216.120.147.200
10 2026-08-25 03:47 639232255723518075
333 ms 216.120.147.200
9 2026-08-25 03:30 639232245484452890
360 ms 216.120.147.200
8 2026-08-25 03:13 639232235157175331
366 ms 216.120.147.200
7 2026-08-25 02:19 639232203197189095
173 ms 216.120.147.200
6 2026-08-25 02:03 639232192844564298
171 ms 216.120.147.200
5 2026-08-25 01:45 639232182496008942
330 ms 216.120.147.200
4 2026-08-25 01:28 639232172197053132
324 ms 216.120.147.200
3 2026-08-25 00:34 639232140250307418
325 ms 216.120.147.200
2 2026-08-25 00:18 639232129927860324
324 ms 216.120.147.200
1 2026-08-25 00:00 639232119551972438
326 ms 216.120.147.200