DNS response history for ns1.nashville.gov

ns1.nashville.gov 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 30 DNS check records, 30 successful responses, 0 failed responses, and 135 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.nashville.gov.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

135 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

170.190.30.5

Most recently resolved hosting IP on selected date

Successful Responses

30

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.nashville.gov

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
30 2026-08-24 12:19 639231703815441688
173 ms 170.190.30.5
29 2026-08-24 12:02 639231693747052549
33 ms 170.190.30.5
28 2026-08-24 11:46 639231683712487276
10 ms 170.190.30.5
27 2026-08-24 11:29 639231673513573868
130 ms 170.190.30.5
26 2026-08-24 10:36 639231641791249939
228 ms 170.190.30.5
25 2026-08-24 10:19 639231631866211033
133 ms 170.190.30.5
24 2026-08-24 10:02 639231621644955316
248 ms 170.190.30.5
23 2026-08-24 09:45 639231611478799259
232 ms 170.190.30.5
22 2026-08-24 08:53 639231579923718211
173 ms 170.190.30.5
21 2026-08-24 08:36 639231569810702936
17 ms 170.190.30.5
20 2026-08-24 08:19 639231559762411619
158 ms 170.190.30.5
19 2026-08-24 08:02 639231549663595407
129 ms 170.190.30.5
18 2026-08-24 07:10 639231518076817246
139 ms 170.190.30.5
17 2026-08-24 06:53 639231508078650885
229 ms 170.190.30.5
16 2026-08-24 06:36 639231498210697093
8 ms 170.190.30.5
15 2026-08-24 06:20 639231488109699360
230 ms 170.190.30.5
14 2026-08-24 05:27 639231456772510692
9 ms 170.190.30.5
13 2026-08-24 05:11 639231447084631185
141 ms 170.190.30.5
12 2026-08-24 04:55 639231437208519473
116 ms 170.190.30.5
11 2026-08-24 04:38 639231427209627490
179 ms 170.190.30.5
10 2026-08-24 03:46 639231395791246644
30 ms 170.190.30.5
9 2026-08-24 03:30 639231386075551458
228 ms 170.190.30.5
8 2026-08-24 03:13 639231376208713791
233 ms 170.190.30.5
7 2026-08-24 02:56 639231366170589276
183 ms 170.190.30.5
6 2026-08-24 02:04 639231334732159368
8 ms 170.190.30.5
5 2026-08-24 01:48 639231325035670078
3 ms 170.190.30.5
4 2026-08-24 01:31 639231315132253837
231 ms 170.190.30.5
3 2026-08-24 01:15 639231305014280808
232 ms 170.190.30.5
2 2026-08-24 00:22 639231273779380675
7 ms 170.190.30.5
1 2026-08-24 00:06 639231264180839154
168 ms 170.190.30.5