DNS response history for ns1.lojamdt.com

ns1.lojamdt.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 39 DNS check records, 34 successful responses, 5 failed responses, and 598 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 ns1.lojamdt.com.
Records on Selected Date

39

Historical checks stored for this nameserver on selected date

Average Latency

598 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:49

All timestamps shown in UTC

Latest Resolved IP on Selected Date

129.121.38.110

Most recently resolved hosting IP on selected date

Successful Responses

34

Checks that returned a measurable response

Failed Responses

5

Checks with no response or no returned latency

Failure Rate

13%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.lojamdt.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
39 2026-08-26 12:49 639233445367152284
781 ms 129.121.38.110
38 2026-08-26 12:32 639233434974187439
298 ms 129.121.38.110
37 2026-08-26 12:14 639233424567558554
284 ms 129.121.38.110
36 2026-08-26 11:57 639233414056832719
284 ms 129.121.38.110
35 2026-08-26 11:39 639233403515141099
-
34 2026-08-26 10:45 639233370841350248
2008 ms 129.121.38.110
33 2026-08-26 10:27 639233360361507238
2031 ms 129.121.38.110
32 2026-08-26 10:10 639233350067824371
-
31 2026-08-26 09:53 639233339545274518
-
30 2026-08-26 09:35 639233329214918079
-
29 2026-08-26 09:18 639233318749762337
-
28 2026-08-26 09:01 639233308387917838
1914 ms 129.121.38.110
27 2026-08-26 08:43 639233297961740122
291 ms 129.121.38.110
26 2026-08-26 08:26 639233287487159094
290 ms 129.121.38.110
25 2026-08-26 08:08 639233276995531707
290 ms 129.121.38.110
24 2026-08-26 07:51 639233266521568229
287 ms 129.121.38.110
23 2026-08-26 07:33 639233256081047431
286 ms 129.121.38.110
22 2026-08-26 06:39 639233223620132921
289 ms 129.121.38.110
21 2026-08-26 06:22 639233213287814244
287 ms 129.121.38.110
20 2026-08-26 06:05 639233202925983161
292 ms 129.121.38.110
19 2026-08-26 05:48 639233192644780696
290 ms 129.121.38.110
18 2026-08-26 05:30 639233182401183833
287 ms 129.121.38.110
17 2026-08-26 05:13 639233172074181051
282 ms 129.121.38.110
16 2026-08-26 04:56 639233161808421455
280 ms 129.121.38.110
15 2026-08-26 04:39 639233151357344052
1287 ms 129.121.38.110
14 2026-08-26 04:22 639233141034116946
1757 ms 129.121.38.110
13 2026-08-26 04:04 639233130828334142
280 ms 129.121.38.110
12 2026-08-26 03:47 639233120373450007
286 ms 129.121.38.110
11 2026-08-26 03:30 639233110066216193
284 ms 129.121.38.110
10 2026-08-26 02:37 639233078065410564
7 ms 129.121.38.110
9 2026-08-26 02:20 639233067787457832
278 ms 129.121.38.110
8 2026-08-26 02:02 639233057501801162
285 ms 129.121.38.110
7 2026-08-26 01:45 639233047089431703
1904 ms 129.121.38.110
6 2026-08-26 01:28 639233036754790688
285 ms 129.121.38.110
5 2026-08-26 01:11 639233026412602472
219 ms 129.121.38.110
4 2026-08-26 00:53 639233016064066127
2 ms 129.121.38.110
3 2026-08-26 00:36 639233005922655772
1269 ms 129.121.38.110
2 2026-08-26 00:19 639232995672256907
287 ms 129.121.38.110
1 2026-08-26 00:02 639232985300872416
842 ms 129.121.38.110