DNS response history for ns2.cordyl.com

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

33

Historical checks stored for this nameserver on selected date

Average Latency

251 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.129.207.79

Most recently resolved hosting IP on selected date

Successful Responses

33

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.cordyl.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
33 2026-08-25 11:47 639232545839529039
349 ms 202.129.207.79
32 2026-08-25 11:30 639232535349285207
216 ms 202.129.207.79
31 2026-08-25 11:13 639232524938080723
200 ms 202.129.207.79
30 2026-08-25 10:19 639232492740373468
378 ms 202.129.207.79
29 2026-08-25 10:02 639232482235303141
385 ms 202.129.207.79
28 2026-08-25 09:44 639232471861770303
185 ms 202.129.207.79
27 2026-08-25 09:27 639232461630217327
358 ms 202.129.207.79
26 2026-08-25 09:10 639232451282965990
350 ms 202.129.207.79
25 2026-08-25 08:52 639232440814614938
175 ms 202.129.207.79
24 2026-08-25 08:35 639232430410720425
367 ms 202.129.207.79
23 2026-08-25 08:18 639232420003096185
364 ms 202.129.207.79
22 2026-08-25 08:00 639232409467287444
8 ms 202.129.207.79
21 2026-08-25 07:43 639232399077195997
364 ms 202.129.207.79
20 2026-08-25 07:26 639232388731528337
381 ms 202.129.207.79
19 2026-08-25 07:08 639232378288598612
399 ms 202.129.207.79
18 2026-08-25 06:14 639232346196373643
4 ms 202.129.207.79
17 2026-08-25 05:58 639232336112370741
2 ms 202.129.207.79
16 2026-08-25 05:41 639232326146508970
2 ms 202.129.207.79
15 2026-08-25 05:24 639232316189381720
18 ms 202.129.207.79
14 2026-08-25 05:08 639232306217998913
4 ms 202.129.207.79
13 2026-08-25 04:51 639232296255744174
376 ms 202.129.207.79
12 2026-08-25 04:34 639232286095760789
368 ms 202.129.207.79
11 2026-08-25 04:17 639232276086186273
345 ms 202.129.207.79
10 2026-08-25 04:01 639232265900986425
375 ms 202.129.207.79
9 2026-08-25 03:44 639232255723518075
621 ms 202.129.207.79
8 2026-08-25 03:27 639232245484452890
213 ms 202.129.207.79
7 2026-08-25 03:10 639232235157175331
185 ms 202.129.207.79
6 2026-08-25 02:16 639232203197189095
355 ms 202.129.207.79
5 2026-08-25 01:59 639232192844564298
182 ms 202.129.207.79
4 2026-08-25 01:42 639232182496008942
182 ms 202.129.207.79
3 2026-08-25 01:25 639232172197053132
184 ms 202.129.207.79
2 2026-08-25 00:31 639232140250307418
363 ms 202.129.207.79
1 2026-08-25 00:14 639232129927860324
9 ms 202.129.207.79