DNS response history for ns2.codemyo.com

ns2.codemyo.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-27. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 218 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.codemyo.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

218 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

165.232.126.61

Most recently resolved hosting IP on selected date

Successful Responses

29

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.codemyo.com

Showing DNS history for 2026-08-27 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
29 2026-08-27 09:27 639234191649612722
70 ms 165.232.126.61
28 2026-08-27 09:09 639234181105879568
31 ms 165.232.126.61
27 2026-08-27 08:52 639234170713214496
206 ms 165.232.126.61
26 2026-08-27 08:34 639234160341037652
187 ms 165.232.126.61
25 2026-08-27 08:17 639234149799404224
30 ms 165.232.126.61
24 2026-08-27 08:00 639234139553286469
84 ms 165.232.126.61
23 2026-08-27 07:06 639234107183588293
352 ms 165.232.126.61
22 2026-08-27 06:49 639234096905435724
380 ms 165.232.126.61
21 2026-08-27 06:32 639234086579410775
37 ms 165.232.126.61
20 2026-08-27 06:14 639234076291157956
299 ms 165.232.126.61
19 2026-08-27 05:57 639234065981939454
234 ms 165.232.126.61
18 2026-08-27 05:40 639234055548642997
164 ms 165.232.126.61
17 2026-08-27 05:23 639234045267979603
36 ms 165.232.126.61
16 2026-08-27 05:06 639234034999717463
180 ms 165.232.126.61
15 2026-08-27 04:48 639234024739225358
9 ms 165.232.126.61
14 2026-08-27 04:31 639234014311170162
7 ms 165.232.126.61
13 2026-08-27 04:14 639234003806017640
52 ms 165.232.126.61
12 2026-08-27 03:56 639233993356203030
189 ms 165.232.126.61
11 2026-08-27 03:03 639233961301716608
75 ms 165.232.126.61
10 2026-08-27 02:46 639233950834200647
102 ms 165.232.126.61
9 2026-08-27 02:28 639233940431849026
2011 ms 165.232.126.61
8 2026-08-27 02:11 639233930110596398
205 ms 165.232.126.61
7 2026-08-27 01:54 639233919705434540
21 ms 165.232.126.61
6 2026-08-27 01:36 639233909452807845
205 ms 165.232.126.61
5 2026-08-27 01:19 639233899096420820
346 ms 165.232.126.61
4 2026-08-27 01:02 639233888707824939
163 ms 165.232.126.61
3 2026-08-27 00:45 639233878461203802
24 ms 165.232.126.61
2 2026-08-27 00:27 639233868060868209
171 ms 165.232.126.61
1 2026-08-27 00:10 639233857450922991
444 ms 165.232.126.61