DNS response history for ns2.codeez.io

ns2.codeez.io 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 35 DNS check records, 35 successful responses, 0 failed responses, and 151 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.codeez.io.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

151 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

95.179.233.167

Most recently resolved hosting IP on selected date

Successful Responses

35

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.codeez.io

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
35 2026-08-27 11:06 639234253963286387
429 ms 95.179.233.167
34 2026-08-27 10:49 639234243654907465
27 ms 95.179.233.167
33 2026-08-27 10:31 639234233269654413
291 ms 95.179.233.167
32 2026-08-27 10:14 639234222943951923
6 ms 95.179.233.167
31 2026-08-27 09:57 639234212558002823
31 ms 95.179.233.167
30 2026-08-27 09:39 639234202117531850
40 ms 95.179.233.167
29 2026-08-27 09:22 639234191649612722
334 ms 95.179.233.167
28 2026-08-27 09:04 639234181105879568
45 ms 95.179.233.167
27 2026-08-27 08:47 639234170713214496
38 ms 95.179.233.167
26 2026-08-27 08:30 639234160341037652
477 ms 95.179.233.167
25 2026-08-27 08:12 639234149799404224
260 ms 95.179.233.167
24 2026-08-27 07:55 639234139553286469
293 ms 95.179.233.167
23 2026-08-27 07:01 639234107183588293
184 ms 95.179.233.167
22 2026-08-27 06:44 639234096905435724
36 ms 95.179.233.167
21 2026-08-27 06:27 639234086579410775
48 ms 95.179.233.167
20 2026-08-27 06:10 639234076291157956
258 ms 95.179.233.167
19 2026-08-27 05:53 639234065981939454
51 ms 95.179.233.167
18 2026-08-27 05:35 639234055548642997
15 ms 95.179.233.167
17 2026-08-27 05:18 639234045267979603
4 ms 95.179.233.167
16 2026-08-27 05:01 639234034999717463
5 ms 95.179.233.167
15 2026-08-27 04:44 639234024739225358
145 ms 95.179.233.167
14 2026-08-27 04:27 639234014311170162
141 ms 95.179.233.167
13 2026-08-27 04:09 639234003806017640
36 ms 95.179.233.167
12 2026-08-27 03:51 639233993356203030
31 ms 95.179.233.167
11 2026-08-27 02:58 639233961301716608
295 ms 95.179.233.167
10 2026-08-27 02:41 639233950834200647
531 ms 95.179.233.167
9 2026-08-27 02:23 639233940431849026
73 ms 95.179.233.167
8 2026-08-27 02:06 639233930110596398
135 ms 95.179.233.167
7 2026-08-27 01:49 639233919705434540
148 ms 95.179.233.167
6 2026-08-27 01:32 639233909452807845
142 ms 95.179.233.167
5 2026-08-27 01:15 639233899096420820
4 ms 95.179.233.167
4 2026-08-27 00:57 639233888707824939
35 ms 95.179.233.167
3 2026-08-27 00:40 639233878461203802
298 ms 95.179.233.167
2 2026-08-27 00:23 639233868060868209
18 ms 95.179.233.167
1 2026-08-27 00:05 639233857450922991
379 ms 95.179.233.167