DNS response history for ns1.goept.kr

ns1.goept.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 36 DNS check records, 36 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 ns1.goept.kr.
Records on Selected Date

36

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-25 12:25

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

36

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.goept.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
36 2026-08-25 12:25 639232566381512620
247 ms 121.136.83.121
35 2026-08-25 12:08 639232556111768563
261 ms 121.136.83.121
34 2026-08-25 11:50 639232545839529039
524 ms 121.136.83.121
33 2026-08-25 11:33 639232535349285207
525 ms 121.136.83.121
32 2026-08-25 11:16 639232524938080723
523 ms 121.136.83.121
31 2026-08-25 10:22 639232492740373468
519 ms 121.136.83.121
30 2026-08-25 10:05 639232482235303141
542 ms 121.136.83.121
29 2026-08-25 09:47 639232471861770303
257 ms 121.136.83.121
28 2026-08-25 09:30 639232461630217327
510 ms 121.136.83.121
27 2026-08-25 09:13 639232451282965990
522 ms 121.136.83.121
26 2026-08-25 08:56 639232440814614938
256 ms 121.136.83.121
25 2026-08-25 08:38 639232430410720425
503 ms 121.136.83.121
24 2026-08-25 08:21 639232420003096185
544 ms 121.136.83.121
23 2026-08-25 08:04 639232409467287444
253 ms 121.136.83.121
22 2026-08-25 07:46 639232399077195997
524 ms 121.136.83.121
21 2026-08-25 07:29 639232388731528337
250 ms 121.136.83.121
20 2026-08-25 07:11 639232378288598612
805 ms 121.136.83.121
19 2026-08-25 06:17 639232346196373643
524 ms 121.136.83.121
18 2026-08-25 06:01 639232336112370741
509 ms 121.136.83.121
17 2026-08-25 05:44 639232326146508970
752 ms 121.136.83.121
16 2026-08-25 05:27 639232316189381720
271 ms 121.136.83.121
15 2026-08-25 05:11 639232306217998913
519 ms 121.136.83.121
14 2026-08-25 04:54 639232296255744174
502 ms 121.136.83.121
13 2026-08-25 04:37 639232286095760789
535 ms 121.136.83.121
12 2026-08-25 04:20 639232276086186273
523 ms 121.136.83.121
11 2026-08-25 04:04 639232265900986425
247 ms 121.136.83.121
10 2026-08-25 03:47 639232255723518075
523 ms 121.136.83.121
9 2026-08-25 03:30 639232245484452890
511 ms 121.136.83.121
8 2026-08-25 03:13 639232235157175331
534 ms 121.136.83.121
7 2026-08-25 02:19 639232203197189095
255 ms 121.136.83.121
6 2026-08-25 02:02 639232192844564298
594 ms 121.136.83.121
5 2026-08-25 01:45 639232182496008942
264 ms 121.136.83.121
4 2026-08-25 01:28 639232172197053132
509 ms 121.136.83.121
3 2026-08-25 00:34 639232140250307418
525 ms 121.136.83.121
2 2026-08-25 00:17 639232129927860324
834 ms 121.136.83.121
1 2026-08-25 00:00 639232119551972438
254 ms 121.136.83.121