DNS response history for ns1.ghazel.us

ns1.ghazel.us 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-24. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 282 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.ghazel.us.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

282 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.225.144

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 ns1.ghazel.us

Showing DNS history for 2026-08-24 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-24 12:09 639231693747052549
5 ms 162.240.225.144
28 2026-08-24 11:52 639231683712487276
347 ms 162.240.225.144
27 2026-08-24 11:36 639231673513573868
346 ms 162.240.225.144
26 2026-08-24 10:42 639231641791249939
3 ms 162.240.225.144
25 2026-08-24 10:26 639231631866211033
346 ms 162.240.225.144
24 2026-08-24 10:09 639231621644955316
177 ms 162.240.225.144
23 2026-08-24 09:52 639231611478799259
349 ms 162.240.225.144
22 2026-08-24 09:00 639231579923718211
434 ms 162.240.225.144
21 2026-08-24 08:43 639231569810702936
9 ms 162.240.225.144
20 2026-08-24 08:26 639231559762411619
338 ms 162.240.225.144
19 2026-08-24 08:09 639231549663595407
14 ms 162.240.225.144
18 2026-08-24 07:16 639231518076817246
360 ms 162.240.225.144
17 2026-08-24 07:00 639231508078650885
354 ms 162.240.225.144
16 2026-08-24 06:43 639231498210697093
348 ms 162.240.225.144
15 2026-08-24 06:27 639231488109699360
3 ms 162.240.225.144
14 2026-08-24 05:34 639231456772510692
2175 ms 162.240.225.144
13 2026-08-24 05:18 639231447084631185
3 ms 162.240.225.144
12 2026-08-24 05:01 639231437208519473
349 ms 162.240.225.144
11 2026-08-24 04:45 639231427209627490
4 ms 162.240.225.144
10 2026-08-24 03:52 639231395791246644
347 ms 162.240.225.144
9 2026-08-24 03:36 639231386075551458
348 ms 162.240.225.144
8 2026-08-24 03:20 639231376208713791
2 ms 162.240.225.144
7 2026-08-24 03:03 639231366170589276
3 ms 162.240.225.144
6 2026-08-24 02:11 639231334732159368
2 ms 162.240.225.144
5 2026-08-24 01:54 639231325035670078
180 ms 162.240.225.144
4 2026-08-24 01:38 639231315132253837
348 ms 162.240.225.144
3 2026-08-24 01:22 639231305014280808
280 ms 162.240.225.144
2 2026-08-24 00:29 639231273779380675
349 ms 162.240.225.144
1 2026-08-24 00:13 639231264180839154
346 ms 162.240.225.144