DNS response history for ns2.hasiru.net

ns2.hasiru.net 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 483 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.hasiru.net.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

483 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

219.166.53.195

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.hasiru.net

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:14 639233424567558554
768 ms 219.166.53.195
36 2026-08-26 11:56 639233414056832719
532 ms 219.166.53.195
35 2026-08-26 11:39 639233403515141099
246 ms 219.166.53.195
34 2026-08-26 10:44 639233370841350248
257 ms 219.166.53.195
33 2026-08-26 10:27 639233360361507238
597 ms 219.166.53.195
32 2026-08-26 10:10 639233350067824371
274 ms 219.166.53.195
31 2026-08-26 09:52 639233339545274518
494 ms 219.166.53.195
30 2026-08-26 09:35 639233329214918079
260 ms 219.166.53.195
29 2026-08-26 09:18 639233318749762337
503 ms 219.166.53.195
28 2026-08-26 09:00 639233308387917838
259 ms 219.166.53.195
27 2026-08-26 08:43 639233297961740122
503 ms 219.166.53.195
26 2026-08-26 08:25 639233287487159094
521 ms 219.166.53.195
25 2026-08-26 08:08 639233276995531707
655 ms 219.166.53.195
24 2026-08-26 07:51 639233266521568229
495 ms 219.166.53.195
23 2026-08-26 07:33 639233256081047431
249 ms 219.166.53.195
22 2026-08-26 06:39 639233223620132921
259 ms 219.166.53.195
21 2026-08-26 06:22 639233213287814244
256 ms 219.166.53.195
20 2026-08-26 06:04 639233202925983161
254 ms 219.166.53.195
19 2026-08-26 05:47 639233192644780696
2279 ms 219.166.53.195
18 2026-08-26 05:30 639233182401183833
503 ms 219.166.53.195
17 2026-08-26 05:13 639233172074181051
259 ms 219.166.53.195
16 2026-08-26 04:56 639233161808421455
325 ms 219.166.53.195
15 2026-08-26 04:39 639233151357344052
520 ms 219.166.53.195
14 2026-08-26 04:21 639233141034116946
511 ms 219.166.53.195
13 2026-08-26 04:04 639233130828334142
498 ms 219.166.53.195
12 2026-08-26 03:47 639233120373450007
519 ms 219.166.53.195
11 2026-08-26 03:30 639233110066216193
241 ms 219.166.53.195
10 2026-08-26 02:36 639233078065410564
253 ms 219.166.53.195
9 2026-08-26 02:19 639233067787457832
508 ms 219.166.53.195
8 2026-08-26 02:02 639233057501801162
505 ms 219.166.53.195
7 2026-08-26 01:45 639233047089431703
516 ms 219.166.53.195
6 2026-08-26 01:28 639233036754790688
514 ms 219.166.53.195
5 2026-08-26 01:10 639233026412602472
519 ms 219.166.53.195
4 2026-08-26 00:53 639233016064066127
516 ms 219.166.53.195
3 2026-08-26 00:36 639233005922655772
499 ms 219.166.53.195
2 2026-08-26 00:19 639232995672256907
507 ms 219.166.53.195
1 2026-08-26 00:02 639232985300872416
511 ms 219.166.53.195