DNS response history for ns2.codeifyy.com

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

38

Historical checks stored for this nameserver on selected date

Average Latency

137 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.38.124.34

Most recently resolved hosting IP on selected date

Successful Responses

38

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.codeifyy.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
38 2026-08-27 12:36 639234307007468133
46 ms 51.38.124.34
37 2026-08-27 12:19 639234296664302575
48 ms 51.38.124.34
36 2026-08-27 12:01 639234286253196126
11 ms 51.38.124.34
35 2026-08-27 11:08 639234253963286387
27 ms 51.38.124.34
34 2026-08-27 10:50 639234243654907465
20 ms 51.38.124.34
33 2026-08-27 10:33 639234233269654413
26 ms 51.38.124.34
32 2026-08-27 10:16 639234222943951923
33 ms 51.38.124.34
31 2026-08-27 09:59 639234212558002823
48 ms 51.38.124.34
30 2026-08-27 09:41 639234202117531850
29 ms 51.38.124.34
29 2026-08-27 09:24 639234191649612722
24 ms 51.38.124.34
28 2026-08-27 09:06 639234181105879568
2030 ms 51.38.124.34
27 2026-08-27 08:49 639234170713214496
36 ms 51.38.124.34
26 2026-08-27 08:32 639234160341037652
22 ms 51.38.124.34
25 2026-08-27 08:14 639234149799404224
24 ms 51.38.124.34
24 2026-08-27 07:57 639234139553286469
25 ms 51.38.124.34
23 2026-08-27 07:03 639234107183588293
25 ms 51.38.124.34
22 2026-08-27 06:46 639234096905435724
69 ms 51.38.124.34
21 2026-08-27 06:29 639234086579410775
36 ms 51.38.124.34
20 2026-08-27 06:12 639234076291157956
17 ms 51.38.124.34
19 2026-08-27 05:55 639234065981939454
24 ms 51.38.124.34
18 2026-08-27 05:37 639234055548642997
25 ms 51.38.124.34
17 2026-08-27 05:20 639234045267979603
71 ms 51.38.124.34
16 2026-08-27 05:03 639234034999717463
27 ms 51.38.124.34
15 2026-08-27 04:46 639234024739225358
14 ms 51.38.124.34
14 2026-08-27 04:28 639234014311170162
75 ms 51.38.124.34
13 2026-08-27 04:11 639234003806017640
46 ms 51.38.124.34
12 2026-08-27 03:53 639233993356203030
13 ms 51.38.124.34
11 2026-08-27 03:00 639233961301716608
9 ms 51.38.124.34
10 2026-08-27 02:43 639233950834200647
19 ms 51.38.124.34
9 2026-08-27 02:25 639233940431849026
56 ms 51.38.124.34
8 2026-08-27 02:08 639233930110596398
30 ms 51.38.124.34
7 2026-08-27 01:51 639233919705434540
33 ms 51.38.124.34
6 2026-08-27 01:34 639233909452807845
19 ms 51.38.124.34
5 2026-08-27 01:16 639233899096420820
25 ms 51.38.124.34
4 2026-08-27 00:59 639233888707824939
19 ms 51.38.124.34
3 2026-08-27 00:42 639233878461203802
65 ms 51.38.124.34
2 2026-08-27 00:25 639233868060868209
42 ms 51.38.124.34
1 2026-08-27 00:07 639233857450922991
2008 ms 51.38.124.34