DNS response history for ns2.hamaninc.com

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

31

Historical checks stored for this nameserver on selected date

Average Latency

308 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.79.232.115

Most recently resolved hosting IP on selected date

Successful Responses

31

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.hamaninc.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
31 2026-08-26 10:06 639233350067824371
225 ms 208.79.232.115
30 2026-08-26 09:49 639233339545274518
248 ms 208.79.232.115
29 2026-08-26 09:31 639233329214918079
233 ms 208.79.232.115
28 2026-08-26 09:14 639233318749762337
2134 ms 208.79.232.115
27 2026-08-26 08:57 639233308387917838
115 ms 208.79.232.115
26 2026-08-26 08:39 639233297961740122
139 ms 208.79.232.115
25 2026-08-26 08:22 639233287487159094
222 ms 208.79.232.115
24 2026-08-26 08:05 639233276995531707
127 ms 208.79.232.115
23 2026-08-26 07:47 639233266521568229
2232 ms 208.79.232.115
22 2026-08-26 07:30 639233256081047431
230 ms 208.79.232.115
21 2026-08-26 06:36 639233223620132921
222 ms 208.79.232.115
20 2026-08-26 06:18 639233213287814244
225 ms 208.79.232.115
19 2026-08-26 06:01 639233202925983161
110 ms 208.79.232.115
18 2026-08-26 05:44 639233192644780696
114 ms 208.79.232.115
17 2026-08-26 05:27 639233182401183833
227 ms 208.79.232.115
16 2026-08-26 05:10 639233172074181051
228 ms 208.79.232.115
15 2026-08-26 04:52 639233161808421455
113 ms 208.79.232.115
14 2026-08-26 04:35 639233151357344052
224 ms 208.79.232.115
13 2026-08-26 04:18 639233141034116946
116 ms 208.79.232.115
12 2026-08-26 04:01 639233130828334142
225 ms 208.79.232.115
11 2026-08-26 03:44 639233120373450007
126 ms 208.79.232.115
10 2026-08-26 03:26 639233110066216193
125 ms 208.79.232.115
9 2026-08-26 02:33 639233078065410564
115 ms 208.79.232.115
8 2026-08-26 02:16 639233067787457832
182 ms 208.79.232.115
7 2026-08-26 01:59 639233057501801162
115 ms 208.79.232.115
6 2026-08-26 01:41 639233047089431703
123 ms 208.79.232.115
5 2026-08-26 01:24 639233036754790688
225 ms 208.79.232.115
4 2026-08-26 01:07 639233026412602472
244 ms 208.79.232.115
3 2026-08-26 00:50 639233016064066127
227 ms 208.79.232.115
2 2026-08-26 00:32 639233005922655772
236 ms 208.79.232.115
1 2026-08-26 00:15 639232995672256907
117 ms 208.79.232.115