DNS response history for ins2.iisweb.co.kr

ins2.iisweb.co.kr 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 485 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 ins2.iisweb.co.kr.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

485 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

183.111.144.126

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 ins2.iisweb.co.kr

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
538 ms 183.111.144.126
28 2026-08-26 09:00 639233308387917838
286 ms 183.111.144.126
27 2026-08-26 08:43 639233297961740122
717 ms 183.111.144.126
26 2026-08-26 08:26 639233287487159094
286 ms 183.111.144.126
25 2026-08-26 08:08 639233276995531707
279 ms 183.111.144.126
24 2026-08-26 07:51 639233266521568229
814 ms 183.111.144.126
23 2026-08-26 07:33 639233256081047431
313 ms 183.111.144.126
22 2026-08-26 06:39 639233223620132921
574 ms 183.111.144.126
21 2026-08-26 06:22 639233213287814244
283 ms 183.111.144.126
20 2026-08-26 06:04 639233202925983161
536 ms 183.111.144.126
19 2026-08-26 05:47 639233192644780696
582 ms 183.111.144.126
18 2026-08-26 05:30 639233182401183833
419 ms 183.111.144.126
17 2026-08-26 05:13 639233172074181051
571 ms 183.111.144.126
16 2026-08-26 04:56 639233161808421455
285 ms 183.111.144.126
15 2026-08-26 04:39 639233151357344052
584 ms 183.111.144.126
14 2026-08-26 04:21 639233141034116946
579 ms 183.111.144.126
13 2026-08-26 04:04 639233130828334142
569 ms 183.111.144.126
12 2026-08-26 03:47 639233120373450007
594 ms 183.111.144.126
11 2026-08-26 03:30 639233110066216193
675 ms 183.111.144.126
10 2026-08-26 02:36 639233078065410564
3 ms 183.111.144.126
9 2026-08-26 02:19 639233067787457832
562 ms 183.111.144.126
8 2026-08-26 02:02 639233057501801162
408 ms 183.111.144.126
7 2026-08-26 01:45 639233047089431703
553 ms 183.111.144.126
6 2026-08-26 01:28 639233036754790688
564 ms 183.111.144.126
5 2026-08-26 01:10 639233026412602472
554 ms 183.111.144.126
4 2026-08-26 00:53 639233016064066127
382 ms 183.111.144.126
3 2026-08-26 00:36 639233005922655772
417 ms 183.111.144.126
2 2026-08-26 00:19 639232995672256907
568 ms 183.111.144.126
1 2026-08-26 00:02 639232985300872416
570 ms 183.111.144.126