DNS response history for ns2.hansung-b.com

ns2.hansung-b.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 29 DNS check records, 29 successful responses, 0 failed responses, and 489 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.hansung-b.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

489 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

158.247.255.81

Most recently resolved hosting IP on selected date

Successful Responses

29

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.hansung-b.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
29 2026-08-26 09:18 639233318749762337
560 ms 158.247.255.81
28 2026-08-26 09:00 639233308387917838
556 ms 158.247.255.81
27 2026-08-26 08:43 639233297961740122
272 ms 158.247.255.81
26 2026-08-26 08:26 639233287487159094
541 ms 158.247.255.81
25 2026-08-26 08:08 639233276995531707
585 ms 158.247.255.81
24 2026-08-26 07:51 639233266521568229
272 ms 158.247.255.81
23 2026-08-26 07:33 639233256081047431
264 ms 158.247.255.81
22 2026-08-26 06:39 639233223620132921
557 ms 158.247.255.81
21 2026-08-26 06:22 639233213287814244
541 ms 158.247.255.81
20 2026-08-26 06:04 639233202925983161
283 ms 158.247.255.81
19 2026-08-26 05:47 639233192644780696
556 ms 158.247.255.81
18 2026-08-26 05:30 639233182401183833
542 ms 158.247.255.81
17 2026-08-26 05:13 639233172074181051
557 ms 158.247.255.81
16 2026-08-26 04:56 639233161808421455
269 ms 158.247.255.81
15 2026-08-26 04:39 639233151357344052
269 ms 158.247.255.81
14 2026-08-26 04:21 639233141034116946
553 ms 158.247.255.81
13 2026-08-26 04:04 639233130828334142
263 ms 158.247.255.81
12 2026-08-26 03:47 639233120373450007
267 ms 158.247.255.81
11 2026-08-26 03:30 639233110066216193
548 ms 158.247.255.81
10 2026-08-26 02:36 639233078065410564
541 ms 158.247.255.81
9 2026-08-26 02:19 639233067787457832
581 ms 158.247.255.81
8 2026-08-26 02:02 639233057501801162
286 ms 158.247.255.81
7 2026-08-26 01:45 639233047089431703
2296 ms 158.247.255.81
6 2026-08-26 01:28 639233036754790688
275 ms 158.247.255.81
5 2026-08-26 01:10 639233026412602472
271 ms 158.247.255.81
4 2026-08-26 00:53 639233016064066127
547 ms 158.247.255.81
3 2026-08-26 00:36 639233005922655772
264 ms 158.247.255.81
2 2026-08-26 00:19 639232995672256907
562 ms 158.247.255.81
1 2026-08-26 00:02 639232985300872416
313 ms 158.247.255.81