DNS response history for ns3.diagcode.com

ns3.diagcode.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-26. For this date, NameServerHistory found 22 DNS check records, 22 successful responses, 0 failed responses, and 233 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 ns3.diagcode.com.
Records on Selected Date

22

Historical checks stored for this nameserver on selected date

Average Latency

233 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 07:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

167.86.97.200

Most recently resolved hosting IP on selected date

Successful Responses

22

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 ns3.diagcode.com

Showing DNS history for 2026-08-26 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
22 2026-08-26 07:24 639233256081047431
28 ms 167.86.97.200
21 2026-08-26 06:30 639233223620132921
37 ms 167.86.97.200
20 2026-08-26 06:13 639233213287814244
54 ms 167.86.97.200
19 2026-08-26 05:56 639233202925983161
2123 ms 167.86.97.200
18 2026-08-26 05:38 639233192644780696
38 ms 167.86.97.200
17 2026-08-26 05:21 639233182401183833
62 ms 167.86.97.200
16 2026-08-26 05:04 639233172074181051
66 ms 167.86.97.200
15 2026-08-26 04:47 639233161808421455
2008 ms 167.86.97.200
14 2026-08-26 04:30 639233151357344052
40 ms 167.86.97.200
13 2026-08-26 04:12 639233141034116946
86 ms 167.86.97.200
12 2026-08-26 03:55 639233130828334142
50 ms 167.86.97.200
11 2026-08-26 03:38 639233120373450007
44 ms 167.86.97.200
10 2026-08-26 03:21 639233110066216193
16 ms 167.86.97.200
9 2026-08-26 02:27 639233078065410564
46 ms 167.86.97.200
8 2026-08-26 02:10 639233067787457832
87 ms 167.86.97.200
7 2026-08-26 01:53 639233057501801162
44 ms 167.86.97.200
6 2026-08-26 01:36 639233047089431703
61 ms 167.86.97.200
5 2026-08-26 01:19 639233036754790688
91 ms 167.86.97.200
4 2026-08-26 01:01 639233026412602472
48 ms 167.86.97.200
3 2026-08-26 00:44 639233016064066127
32 ms 167.86.97.200
2 2026-08-26 00:27 639233005922655772
45 ms 167.86.97.200
1 2026-08-26 00:10 639232995672256907
22 ms 167.86.97.200