DNS response history for ns2.tgience.co.kr

ns2.tgience.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 34 DNS check records, 34 successful responses, 0 failed responses, and 671 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.tgience.co.kr.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

671 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

211.110.10.29

Most recently resolved hosting IP on selected date

Successful Responses

34

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.tgience.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
34 2026-08-26 10:46 639233370841350248
635 ms 211.110.10.29
33 2026-08-26 10:28 639233360361507238
613 ms 211.110.10.29
32 2026-08-26 10:11 639233350067824371
619 ms 211.110.10.29
31 2026-08-26 09:54 639233339545274518
612 ms 211.110.10.29
30 2026-08-26 09:36 639233329214918079
635 ms 211.110.10.29
29 2026-08-26 09:19 639233318749762337
631 ms 211.110.10.29
28 2026-08-26 09:02 639233308387917838
926 ms 211.110.10.29
27 2026-08-26 08:44 639233297961740122
864 ms 211.110.10.29
26 2026-08-26 08:27 639233287487159094
652 ms 211.110.10.29
25 2026-08-26 08:10 639233276995531707
635 ms 211.110.10.29
24 2026-08-26 07:52 639233266521568229
616 ms 211.110.10.29
23 2026-08-26 07:34 639233256081047431
658 ms 211.110.10.29
22 2026-08-26 06:40 639233223620132921
653 ms 211.110.10.29
21 2026-08-26 06:23 639233213287814244
643 ms 211.110.10.29
20 2026-08-26 06:06 639233202925983161
646 ms 211.110.10.29
19 2026-08-26 05:49 639233192644780696
729 ms 211.110.10.29
18 2026-08-26 05:31 639233182401183833
1005 ms 211.110.10.29
17 2026-08-26 05:14 639233172074181051
624 ms 211.110.10.29
16 2026-08-26 04:57 639233161808421455
634 ms 211.110.10.29
15 2026-08-26 04:40 639233151357344052
644 ms 211.110.10.29
14 2026-08-26 04:23 639233141034116946
647 ms 211.110.10.29
13 2026-08-26 04:05 639233130828334142
663 ms 211.110.10.29
12 2026-08-26 03:48 639233120373450007
629 ms 211.110.10.29
11 2026-08-26 03:31 639233110066216193
631 ms 211.110.10.29
10 2026-08-26 02:38 639233078065410564
621 ms 211.110.10.29
9 2026-08-26 02:21 639233067787457832
631 ms 211.110.10.29
8 2026-08-26 02:03 639233057501801162
623 ms 211.110.10.29
7 2026-08-26 01:46 639233047089431703
844 ms 211.110.10.29
6 2026-08-26 01:29 639233036754790688
638 ms 211.110.10.29
5 2026-08-26 01:12 639233026412602472
635 ms 211.110.10.29
4 2026-08-26 00:54 639233016064066127
632 ms 211.110.10.29
3 2026-08-26 00:37 639233005922655772
643 ms 211.110.10.29
2 2026-08-26 00:20 639232995672256907
646 ms 211.110.10.29
1 2026-08-26 00:03 639232985300872416
645 ms 211.110.10.29