DNS response history for ns2.s501host.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

370 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.64.69.47

Most recently resolved hosting IP on selected date

Successful Responses

34

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.s501host.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
34 2026-08-26 10:42 639233370841350248
290 ms 69.64.69.47
33 2026-08-26 10:25 639233360361507238
289 ms 69.64.69.47
32 2026-08-26 10:08 639233350067824371
291 ms 69.64.69.47
31 2026-08-26 09:50 639233339545274518
298 ms 69.64.69.47
30 2026-08-26 09:33 639233329214918079
291 ms 69.64.69.47
29 2026-08-26 09:16 639233318749762337
292 ms 69.64.69.47
28 2026-08-26 08:58 639233308387917838
293 ms 69.64.69.47
27 2026-08-26 08:41 639233297961740122
294 ms 69.64.69.47
26 2026-08-26 08:23 639233287487159094
292 ms 69.64.69.47
25 2026-08-26 08:06 639233276995531707
20 ms 69.64.69.47
24 2026-08-26 07:48 639233266521568229
291 ms 69.64.69.47
23 2026-08-26 07:31 639233256081047431
289 ms 69.64.69.47
22 2026-08-26 06:37 639233223620132921
290 ms 69.64.69.47
21 2026-08-26 06:20 639233213287814244
292 ms 69.64.69.47
20 2026-08-26 06:02 639233202925983161
293 ms 69.64.69.47
19 2026-08-26 05:45 639233192644780696
318 ms 69.64.69.47
18 2026-08-26 05:28 639233182401183833
294 ms 69.64.69.47
17 2026-08-26 05:11 639233172074181051
289 ms 69.64.69.47
16 2026-08-26 04:54 639233161808421455
291 ms 69.64.69.47
15 2026-08-26 04:37 639233151357344052
289 ms 69.64.69.47
14 2026-08-26 04:19 639233141034116946
7 ms 69.64.69.47
13 2026-08-26 04:02 639233130828334142
180 ms 69.64.69.47
12 2026-08-26 03:45 639233120373450007
290 ms 69.64.69.47
11 2026-08-26 03:28 639233110066216193
7 ms 69.64.69.47
10 2026-08-26 02:34 639233078065410564
289 ms 69.64.69.47
9 2026-08-26 02:17 639233067787457832
293 ms 69.64.69.47
8 2026-08-26 02:00 639233057501801162
150 ms 69.64.69.47
7 2026-08-26 01:43 639233047089431703
297 ms 69.64.69.47
6 2026-08-26 01:26 639233036754790688
302 ms 69.64.69.47
5 2026-08-26 01:08 639233026412602472
174 ms 69.64.69.47
4 2026-08-26 00:51 639233016064066127
296 ms 69.64.69.47
3 2026-08-26 00:34 639233005922655772
2273 ms 69.64.69.47
2 2026-08-26 00:17 639232995672256907
299 ms 69.64.69.47
1 2026-08-26 00:00 639232985300872416
2149 ms 69.64.69.47