DNS response history for ns2.tggs.kr

ns2.tggs.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 465 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.tggs.kr.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

465 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

141.164.59.232

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.tggs.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:45 639233370841350248
547 ms 141.164.59.232
33 2026-08-26 10:27 639233360361507238
552 ms 141.164.59.232
32 2026-08-26 10:10 639233350067824371
272 ms 141.164.59.232
31 2026-08-26 09:53 639233339545274518
264 ms 141.164.59.232
30 2026-08-26 09:35 639233329214918079
276 ms 141.164.59.232
29 2026-08-26 09:18 639233318749762337
285 ms 141.164.59.232
28 2026-08-26 09:01 639233308387917838
275 ms 141.164.59.232
27 2026-08-26 08:43 639233297961740122
270 ms 141.164.59.232
26 2026-08-26 08:26 639233287487159094
746 ms 141.164.59.232
25 2026-08-26 08:09 639233276995531707
593 ms 141.164.59.232
24 2026-08-26 07:51 639233266521568229
271 ms 141.164.59.232
23 2026-08-26 07:33 639233256081047431
559 ms 141.164.59.232
22 2026-08-26 06:39 639233223620132921
554 ms 141.164.59.232
21 2026-08-26 06:22 639233213287814244
279 ms 141.164.59.232
20 2026-08-26 06:05 639233202925983161
560 ms 141.164.59.232
19 2026-08-26 05:48 639233192644780696
280 ms 141.164.59.232
18 2026-08-26 05:30 639233182401183833
550 ms 141.164.59.232
17 2026-08-26 05:13 639233172074181051
275 ms 141.164.59.232
16 2026-08-26 04:56 639233161808421455
562 ms 141.164.59.232
15 2026-08-26 04:39 639233151357344052
565 ms 141.164.59.232
14 2026-08-26 04:22 639233141034116946
554 ms 141.164.59.232
13 2026-08-26 04:04 639233130828334142
545 ms 141.164.59.232
12 2026-08-26 03:47 639233120373450007
275 ms 141.164.59.232
11 2026-08-26 03:30 639233110066216193
555 ms 141.164.59.232
10 2026-08-26 02:37 639233078065410564
573 ms 141.164.59.232
9 2026-08-26 02:20 639233067787457832
590 ms 141.164.59.232
8 2026-08-26 02:02 639233057501801162
581 ms 141.164.59.232
7 2026-08-26 01:45 639233047089431703
550 ms 141.164.59.232
6 2026-08-26 01:28 639233036754790688
549 ms 141.164.59.232
5 2026-08-26 01:11 639233026412602472
553 ms 141.164.59.232
4 2026-08-26 00:53 639233016064066127
569 ms 141.164.59.232
3 2026-08-26 00:36 639233005922655772
269 ms 141.164.59.232
2 2026-08-26 00:19 639232995672256907
540 ms 141.164.59.232
1 2026-08-26 00:02 639232985300872416
556 ms 141.164.59.232