DNS response history for ns1.goedy.kr

ns1.goedy.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-25. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 418 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 ns1.goedy.kr.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

418 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

121.136.83.121

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns1.goedy.kr

Showing DNS history for 2026-08-25 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
37 2026-08-25 12:42 639232576780683689
525 ms 121.136.83.121
36 2026-08-25 12:25 639232566381512620
255 ms 121.136.83.121
35 2026-08-25 12:08 639232556111768563
524 ms 121.136.83.121
34 2026-08-25 11:50 639232545839529039
262 ms 121.136.83.121
33 2026-08-25 11:33 639232535349285207
258 ms 121.136.83.121
32 2026-08-25 11:16 639232524938080723
253 ms 121.136.83.121
31 2026-08-25 10:22 639232492740373468
252 ms 121.136.83.121
30 2026-08-25 10:05 639232482235303141
258 ms 121.136.83.121
29 2026-08-25 09:47 639232471861770303
534 ms 121.136.83.121
28 2026-08-25 09:30 639232461630217327
533 ms 121.136.83.121
27 2026-08-25 09:13 639232451282965990
518 ms 121.136.83.121
26 2026-08-25 08:56 639232440814614938
258 ms 121.136.83.121
25 2026-08-25 08:38 639232430410720425
610 ms 121.136.83.121
24 2026-08-25 08:21 639232420003096185
254 ms 121.136.83.121
23 2026-08-25 08:03 639232409467287444
527 ms 121.136.83.121
22 2026-08-25 07:46 639232399077195997
260 ms 121.136.83.121
21 2026-08-25 07:29 639232388731528337
259 ms 121.136.83.121
20 2026-08-25 07:11 639232378288598612
536 ms 121.136.83.121
19 2026-08-25 06:17 639232346196373643
266 ms 121.136.83.121
18 2026-08-25 06:01 639232336112370741
524 ms 121.136.83.121
17 2026-08-25 05:44 639232326146508970
262 ms 121.136.83.121
16 2026-08-25 05:27 639232316189381720
262 ms 121.136.83.121
15 2026-08-25 05:11 639232306217998913
266 ms 121.136.83.121
14 2026-08-25 04:54 639232296255744174
261 ms 121.136.83.121
13 2026-08-25 04:37 639232286095760789
515 ms 121.136.83.121
12 2026-08-25 04:20 639232276086186273
518 ms 121.136.83.121
11 2026-08-25 04:04 639232265900986425
526 ms 121.136.83.121
10 2026-08-25 03:47 639232255723518075
516 ms 121.136.83.121
9 2026-08-25 03:30 639232245484452890
504 ms 121.136.83.121
8 2026-08-25 03:13 639232235157175331
532 ms 121.136.83.121
7 2026-08-25 02:19 639232203197189095
514 ms 121.136.83.121
6 2026-08-25 02:02 639232192844564298
523 ms 121.136.83.121
5 2026-08-25 01:45 639232182496008942
267 ms 121.136.83.121
4 2026-08-25 01:28 639232172197053132
522 ms 121.136.83.121
3 2026-08-25 00:34 639232140250307418
519 ms 121.136.83.121
2 2026-08-25 00:17 639232129927860324
521 ms 121.136.83.121
1 2026-08-25 00:00 639232119551972438
754 ms 121.136.83.121