DNS response history for ns3.diatem.net

ns3.diatem.net 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 25 DNS check records, 25 successful responses, 0 failed responses, and 313 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.diatem.net.
Records on Selected Date

25

Historical checks stored for this nameserver on selected date

Average Latency

313 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

95.130.153.38

Most recently resolved hosting IP on selected date

Successful Responses

25

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.diatem.net

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
25 2026-08-26 08:16 639233287487159094
36 ms 95.130.153.38
24 2026-08-26 07:59 639233276995531707
45 ms 95.130.153.38
23 2026-08-26 07:41 639233266521568229
178 ms 95.130.153.38
22 2026-08-26 07:24 639233256081047431
27 ms 95.130.153.38
21 2026-08-26 06:30 639233223620132921
2051 ms 95.130.153.38
20 2026-08-26 06:12 639233213287814244
37 ms 95.130.153.38
19 2026-08-26 05:55 639233202925983161
57 ms 95.130.153.38
18 2026-08-26 05:38 639233192644780696
19 ms 95.130.153.38
17 2026-08-26 05:21 639233182401183833
2077 ms 95.130.153.38
16 2026-08-26 05:04 639233172074181051
588 ms 95.130.153.38
15 2026-08-26 04:47 639233161808421455
2009 ms 95.130.153.38
14 2026-08-26 04:29 639233151357344052
32 ms 95.130.153.38
13 2026-08-26 04:12 639233141034116946
39 ms 95.130.153.38
12 2026-08-26 03:55 639233130828334142
36 ms 95.130.153.38
11 2026-08-26 03:38 639233120373450007
52 ms 95.130.153.38
10 2026-08-26 03:20 639233110066216193
43 ms 95.130.153.38
9 2026-08-26 02:27 639233078065410564
41 ms 95.130.153.38
8 2026-08-26 02:10 639233067787457832
44 ms 95.130.153.38
7 2026-08-26 01:53 639233057501801162
86 ms 95.130.153.38
6 2026-08-26 01:35 639233047089431703
132 ms 95.130.153.38
5 2026-08-26 01:18 639233036754790688
8 ms 95.130.153.38
4 2026-08-26 01:01 639233026412602472
32 ms 95.130.153.38
3 2026-08-26 00:44 639233016064066127
30 ms 95.130.153.38
2 2026-08-26 00:27 639233005922655772
58 ms 95.130.153.38
1 2026-08-26 00:10 639232995672256907
74 ms 95.130.153.38