DNS response history for ns2.hitsports.us

ns2.hitsports.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-26. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 360 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.hitsports.us.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

360 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:52

All timestamps shown in UTC

Latest Resolved IP on Selected Date

67.225.147.43

Most recently resolved hosting IP on selected date

Successful Responses

35

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.hitsports.us

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
35 2026-08-26 11:52 639233414056832719
236 ms 67.225.147.43
34 2026-08-26 11:34 639233403515141099
243 ms 67.225.147.43
33 2026-08-26 10:40 639233370841350248
242 ms 67.225.147.43
32 2026-08-26 10:22 639233360361507238
238 ms 67.225.147.43
31 2026-08-26 10:05 639233350067824371
7 ms 67.225.147.43
30 2026-08-26 09:48 639233339545274518
321 ms 67.225.147.43
29 2026-08-26 09:30 639233329214918079
235 ms 67.225.147.43
28 2026-08-26 09:13 639233318749762337
109 ms 67.225.147.43
27 2026-08-26 08:56 639233308387917838
236 ms 67.225.147.43
26 2026-08-26 08:38 639233297961740122
235 ms 67.225.147.43
25 2026-08-26 08:21 639233287487159094
239 ms 67.225.147.43
24 2026-08-26 08:04 639233276995531707
2247 ms 67.225.147.43
23 2026-08-26 07:46 639233266521568229
248 ms 67.225.147.43
22 2026-08-26 07:29 639233256081047431
227 ms 67.225.147.43
21 2026-08-26 06:35 639233223620132921
239 ms 67.225.147.43
20 2026-08-26 06:17 639233213287814244
250 ms 67.225.147.43
19 2026-08-26 06:00 639233202925983161
7 ms 67.225.147.43
18 2026-08-26 05:43 639233192644780696
236 ms 67.225.147.43
17 2026-08-26 05:26 639233182401183833
228 ms 67.225.147.43
16 2026-08-26 05:09 639233172074181051
7 ms 67.225.147.43
15 2026-08-26 04:51 639233161808421455
7 ms 67.225.147.43
14 2026-08-26 04:34 639233151357344052
22 ms 67.225.147.43
13 2026-08-26 04:17 639233141034116946
243 ms 67.225.147.43
12 2026-08-26 04:00 639233130828334142
234 ms 67.225.147.43
11 2026-08-26 03:43 639233120373450007
235 ms 67.225.147.43
10 2026-08-26 03:25 639233110066216193
122 ms 67.225.147.43
9 2026-08-26 02:32 639233078065410564
141 ms 67.225.147.43
8 2026-08-26 02:15 639233067787457832
238 ms 67.225.147.43
7 2026-08-26 01:58 639233057501801162
240 ms 67.225.147.43
6 2026-08-26 01:40 639233047089431703
120 ms 67.225.147.43
5 2026-08-26 01:23 639233036754790688
2144 ms 67.225.147.43
4 2026-08-26 01:06 639233026412602472
245 ms 67.225.147.43
3 2026-08-26 00:49 639233016064066127
225 ms 67.225.147.43
2 2026-08-26 00:32 639233005922655772
238 ms 67.225.147.43
1 2026-08-26 00:15 639232995672256907
2119 ms 67.225.147.43