DNS response history for ns2.dayalmc.com

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

30

Historical checks stored for this nameserver on selected date

Average Latency

347 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

172.93.121.124

Most recently resolved hosting IP on selected date

Successful Responses

30

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.dayalmc.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
30 2026-08-25 10:20 639232492740373468
168 ms 172.93.121.124
29 2026-08-25 10:02 639232482235303141
163 ms 172.93.121.124
28 2026-08-25 09:45 639232471861770303
352 ms 172.93.121.124
27 2026-08-25 09:28 639232461630217327
333 ms 172.93.121.124
26 2026-08-25 09:10 639232451282965990
181 ms 172.93.121.124
25 2026-08-25 08:53 639232440814614938
340 ms 172.93.121.124
24 2026-08-25 08:36 639232430410720425
172 ms 172.93.121.124
23 2026-08-25 08:18 639232420003096185
15 ms 172.93.121.124
22 2026-08-25 08:01 639232409467287444
170 ms 172.93.121.124
21 2026-08-25 07:43 639232399077195997
343 ms 172.93.121.124
20 2026-08-25 07:26 639232388731528337
174 ms 172.93.121.124
19 2026-08-25 07:09 639232378288598612
330 ms 172.93.121.124
18 2026-08-25 06:15 639232346196373643
335 ms 172.93.121.124
17 2026-08-25 05:58 639232336112370741
330 ms 172.93.121.124
16 2026-08-25 05:42 639232326146508970
326 ms 172.93.121.124
15 2026-08-25 05:25 639232316189381720
2010 ms 172.93.121.124
14 2026-08-25 05:09 639232306217998913
340 ms 172.93.121.124
13 2026-08-25 04:52 639232296255744174
7 ms 172.93.121.124
12 2026-08-25 04:35 639232286095760789
164 ms 172.93.121.124
11 2026-08-25 04:18 639232276086186273
2008 ms 172.93.121.124
10 2026-08-25 04:01 639232265900986425
327 ms 172.93.121.124
9 2026-08-25 03:44 639232255723518075
166 ms 172.93.121.124
8 2026-08-25 03:27 639232245484452890
166 ms 172.93.121.124
7 2026-08-25 03:10 639232235157175331
161 ms 172.93.121.124
6 2026-08-25 02:17 639232203197189095
162 ms 172.93.121.124
5 2026-08-25 02:00 639232192844564298
167 ms 172.93.121.124
4 2026-08-25 01:43 639232182496008942
167 ms 172.93.121.124
3 2026-08-25 01:25 639232172197053132
333 ms 172.93.121.124
2 2026-08-25 00:32 639232140250307418
172 ms 172.93.121.124
1 2026-08-25 00:15 639232129927860324
326 ms 172.93.121.124