DNS response history for ns2.hasman.in

ns2.hasman.in 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 37 DNS check records, 37 successful responses, 0 failed responses, and 401 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.hasman.in.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

401 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:29

All timestamps shown in UTC

Latest Resolved IP on Selected Date

119.18.52.236

Most recently resolved hosting IP on selected date

Successful Responses

37

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.hasman.in

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
37 2026-08-26 12:29 639233434974187439
273 ms 119.18.52.236
36 2026-08-26 12:11 639233424567558554
130 ms 119.18.52.236
35 2026-08-26 11:54 639233414056832719
273 ms 119.18.52.236
34 2026-08-26 11:36 639233403515141099
274 ms 119.18.52.236
33 2026-08-26 10:42 639233370841350248
267 ms 119.18.52.236
32 2026-08-26 10:25 639233360361507238
2140 ms 119.18.52.236
31 2026-08-26 10:07 639233350067824371
134 ms 119.18.52.236
30 2026-08-26 09:50 639233339545274518
294 ms 119.18.52.236
29 2026-08-26 09:32 639233329214918079
139 ms 119.18.52.236
28 2026-08-26 09:15 639233318749762337
138 ms 119.18.52.236
27 2026-08-26 08:58 639233308387917838
148 ms 119.18.52.236
26 2026-08-26 08:41 639233297961740122
2385 ms 119.18.52.236
25 2026-08-26 08:23 639233287487159094
285 ms 119.18.52.236
24 2026-08-26 08:06 639233276995531707
281 ms 119.18.52.236
23 2026-08-26 07:48 639233266521568229
299 ms 119.18.52.236
22 2026-08-26 07:31 639233256081047431
300 ms 119.18.52.236
21 2026-08-26 06:37 639233223620132921
286 ms 119.18.52.236
20 2026-08-26 06:19 639233213287814244
272 ms 119.18.52.236
19 2026-08-26 06:02 639233202925983161
275 ms 119.18.52.236
18 2026-08-26 05:45 639233192644780696
277 ms 119.18.52.236
17 2026-08-26 05:28 639233182401183833
195 ms 119.18.52.236
16 2026-08-26 05:11 639233172074181051
299 ms 119.18.52.236
15 2026-08-26 04:53 639233161808421455
280 ms 119.18.52.236
14 2026-08-26 04:36 639233151357344052
276 ms 119.18.52.236
13 2026-08-26 04:19 639233141034116946
275 ms 119.18.52.236
12 2026-08-26 04:02 639233130828334142
269 ms 119.18.52.236
11 2026-08-26 03:45 639233120373450007
291 ms 119.18.52.236
10 2026-08-26 03:27 639233110066216193
3 ms 119.18.52.236
9 2026-08-26 02:34 639233078065410564
269 ms 119.18.52.236
8 2026-08-26 02:17 639233067787457832
142 ms 119.18.52.236
7 2026-08-26 02:00 639233057501801162
8 ms 119.18.52.236
6 2026-08-26 01:43 639233047089431703
2400 ms 119.18.52.236
5 2026-08-26 01:25 639233036754790688
289 ms 119.18.52.236
4 2026-08-26 01:08 639233026412602472
267 ms 119.18.52.236
3 2026-08-26 00:51 639233016064066127
138 ms 119.18.52.236
2 2026-08-26 00:34 639233005922655772
286 ms 119.18.52.236
1 2026-08-26 00:17 639232995672256907
275 ms 119.18.52.236