DNS response history for ns2.hiriscare.com

ns2.hiriscare.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 30 DNS check records, 29 successful responses, 1 failed responses, and 428 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.hiriscare.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

428 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

82.223.1.136

Most recently resolved hosting IP on selected date

Successful Responses

29

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.hiriscare.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
30 2026-08-26 09:44 639233339545274518
107 ms 82.223.1.136
29 2026-08-26 09:26 639233329214918079
2065 ms 82.223.1.136
28 2026-08-26 09:09 639233318749762337
137 ms 82.223.1.136
27 2026-08-26 08:52 639233308387917838
100 ms 82.223.1.136
26 2026-08-26 08:34 639233297961740122
2053 ms 82.223.1.136
25 2026-08-26 08:17 639233287487159094
61 ms 82.223.1.136
24 2026-08-26 08:00 639233276995531707
134 ms 82.223.1.136
23 2026-08-26 07:42 639233266521568229
13 ms 82.223.1.136
22 2026-08-26 07:25 639233256081047431
50 ms 82.223.1.136
21 2026-08-26 06:31 639233223620132921
81 ms 82.223.1.136
20 2026-08-26 06:13 639233213287814244
100 ms 82.223.1.136
19 2026-08-26 05:56 639233202925983161
142 ms 82.223.1.136
18 2026-08-26 05:39 639233192644780696
88 ms 82.223.1.136
17 2026-08-26 05:22 639233182401183833
2010 ms 82.223.1.136
16 2026-08-26 05:05 639233172074181051
10 ms 82.223.1.136
15 2026-08-26 04:48 639233161808421455
49 ms 82.223.1.136
14 2026-08-26 04:30 639233151357344052
-
13 2026-08-26 04:13 639233141034116946
95 ms 82.223.1.136
12 2026-08-26 03:56 639233130828334142
95 ms 82.223.1.136
11 2026-08-26 03:39 639233120373450007
102 ms 82.223.1.136
10 2026-08-26 03:21 639233110066216193
93 ms 82.223.1.136
9 2026-08-26 02:28 639233078065410564
168 ms 82.223.1.136
8 2026-08-26 02:11 639233067787457832
101 ms 82.223.1.136
7 2026-08-26 01:54 639233057501801162
56 ms 82.223.1.136
6 2026-08-26 01:36 639233047089431703
92 ms 82.223.1.136
5 2026-08-26 01:19 639233036754790688
49 ms 82.223.1.136
4 2026-08-26 01:02 639233026412602472
107 ms 82.223.1.136
3 2026-08-26 00:45 639233016064066127
4063 ms 82.223.1.136
2 2026-08-26 00:28 639233005922655772
90 ms 82.223.1.136
1 2026-08-26 00:11 639232995672256907
96 ms 82.223.1.136