DNS response history for ns2.lozanotech.com

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

29

Historical checks stored for this nameserver on selected date

Average Latency

339 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

107.180.107.130

Most recently resolved hosting IP on selected date

Successful Responses

29

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.lozanotech.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
29 2026-08-26 09:16 639233318749762337
338 ms 107.180.107.130
28 2026-08-26 08:59 639233308387917838
343 ms 107.180.107.130
27 2026-08-26 08:41 639233297961740122
338 ms 107.180.107.130
26 2026-08-26 08:24 639233287487159094
337 ms 107.180.107.130
25 2026-08-26 08:07 639233276995531707
344 ms 107.180.107.130
24 2026-08-26 07:49 639233266521568229
333 ms 107.180.107.130
23 2026-08-26 07:32 639233256081047431
366 ms 107.180.107.130
22 2026-08-26 06:38 639233223620132921
455 ms 107.180.107.130
21 2026-08-26 06:20 639233213287814244
337 ms 107.180.107.130
20 2026-08-26 06:03 639233202925983161
50 ms 107.180.107.130
19 2026-08-26 05:46 639233192644780696
354 ms 107.180.107.130
18 2026-08-26 05:29 639233182401183833
336 ms 107.180.107.130
17 2026-08-26 05:12 639233172074181051
338 ms 107.180.107.130
16 2026-08-26 04:54 639233161808421455
364 ms 107.180.107.130
15 2026-08-26 04:37 639233151357344052
231 ms 107.180.107.130
14 2026-08-26 04:20 639233141034116946
158 ms 107.180.107.130
13 2026-08-26 04:03 639233130828334142
333 ms 107.180.107.130
12 2026-08-26 03:46 639233120373450007
178 ms 107.180.107.130
11 2026-08-26 03:28 639233110066216193
338 ms 107.180.107.130
10 2026-08-26 02:35 639233078065410564
14 ms 107.180.107.130
9 2026-08-26 02:18 639233067787457832
4 ms 107.180.107.130
8 2026-08-26 02:01 639233057501801162
339 ms 107.180.107.130
7 2026-08-26 01:43 639233047089431703
351 ms 107.180.107.130
6 2026-08-26 01:26 639233036754790688
3 ms 107.180.107.130
5 2026-08-26 01:09 639233026412602472
2 ms 107.180.107.130
4 2026-08-26 00:52 639233016064066127
353 ms 107.180.107.130
3 2026-08-26 00:35 639233005922655772
334 ms 107.180.107.130
2 2026-08-26 00:18 639232995672256907
336 ms 107.180.107.130
1 2026-08-26 00:00 639232985300872416
2235 ms 107.180.107.130