DNS response history for ns2.cordobyte.com

ns2.cordobyte.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 143 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.cordobyte.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

143 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.118.190.146

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.cordobyte.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:09 639232492740373468
84 ms 185.118.190.146
29 2026-08-25 09:52 639232482235303141
131 ms 185.118.190.146
28 2026-08-25 09:35 639232471861770303
28 ms 185.118.190.146
27 2026-08-25 09:18 639232461630217327
94 ms 185.118.190.146
26 2026-08-25 09:00 639232451282965990
50 ms 185.118.190.146
25 2026-08-25 08:43 639232440814614938
97 ms 185.118.190.146
24 2026-08-25 08:26 639232430410720425
105 ms 185.118.190.146
23 2026-08-25 08:08 639232420003096185
172 ms 185.118.190.146
22 2026-08-25 07:51 639232409467287444
85 ms 185.118.190.146
21 2026-08-25 07:33 639232399077195997
53 ms 185.118.190.146
20 2026-08-25 07:16 639232388731528337
90 ms 185.118.190.146
19 2026-08-25 06:59 639232378288598612
2065 ms 185.118.190.146
18 2026-08-25 06:05 639232346196373643
104 ms 185.118.190.146
17 2026-08-25 05:48 639232336112370741
47 ms 185.118.190.146
16 2026-08-25 05:32 639232326146508970
59 ms 185.118.190.146
15 2026-08-25 05:15 639232316189381720
122 ms 185.118.190.146
14 2026-08-25 04:59 639232306217998913
43 ms 185.118.190.146
13 2026-08-25 04:42 639232296255744174
71 ms 185.118.190.146
12 2026-08-25 04:25 639232286095760789
68 ms 185.118.190.146
11 2026-08-25 04:08 639232276086186273
27 ms 185.118.190.146
10 2026-08-25 03:51 639232265900986425
38 ms 185.118.190.146
9 2026-08-25 03:34 639232255723518075
55 ms 185.118.190.146
8 2026-08-25 03:17 639232245484452890
86 ms 185.118.190.146
7 2026-08-25 03:00 639232235157175331
86 ms 185.118.190.146
6 2026-08-25 02:07 639232203197189095
169 ms 185.118.190.146
5 2026-08-25 01:50 639232192844564298
47 ms 185.118.190.146
4 2026-08-25 01:32 639232182496008942
104 ms 185.118.190.146
3 2026-08-25 01:15 639232172197053132
65 ms 185.118.190.146
2 2026-08-25 00:22 639232140250307418
42 ms 185.118.190.146
1 2026-08-25 00:05 639232129927860324
6 ms 185.118.190.146