DNS response history for ns2.godo.co.kr

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

37

Historical checks stored for this nameserver on selected date

Average Latency

578 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

211.233.50.4

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 ns2.godo.co.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
595 ms 211.233.50.4
36 2026-08-25 12:25 639232566381512620
599 ms 211.233.50.4
35 2026-08-25 12:08 639232556111768563
588 ms 211.233.50.4
34 2026-08-25 11:51 639232545839529039
594 ms 211.233.50.4
33 2026-08-25 11:33 639232535349285207
317 ms 211.233.50.4
32 2026-08-25 11:16 639232524938080723
613 ms 211.233.50.4
31 2026-08-25 10:22 639232492740373468
561 ms 211.233.50.4
30 2026-08-25 10:05 639232482235303141
571 ms 211.233.50.4
29 2026-08-25 09:47 639232471861770303
602 ms 211.233.50.4
28 2026-08-25 09:30 639232461630217327
364 ms 211.233.50.4
27 2026-08-25 09:13 639232451282965990
594 ms 211.233.50.4
26 2026-08-25 08:56 639232440814614938
652 ms 211.233.50.4
25 2026-08-25 08:38 639232430410720425
595 ms 211.233.50.4
24 2026-08-25 08:21 639232420003096185
574 ms 211.233.50.4
23 2026-08-25 08:04 639232409467287444
297 ms 211.233.50.4
22 2026-08-25 07:46 639232399077195997
581 ms 211.233.50.4
21 2026-08-25 07:29 639232388731528337
596 ms 211.233.50.4
20 2026-08-25 07:12 639232378288598612
891 ms 211.233.50.4
19 2026-08-25 06:18 639232346196373643
339 ms 211.233.50.4
18 2026-08-25 06:01 639232336112370741
584 ms 211.233.50.4
17 2026-08-25 05:44 639232326146508970
920 ms 211.233.50.4
16 2026-08-25 05:28 639232316189381720
577 ms 211.233.50.4
15 2026-08-25 05:11 639232306217998913
296 ms 211.233.50.4
14 2026-08-25 04:54 639232296255744174
602 ms 211.233.50.4
13 2026-08-25 04:38 639232286095760789
325 ms 211.233.50.4
12 2026-08-25 04:21 639232276086186273
314 ms 211.233.50.4
11 2026-08-25 04:04 639232265900986425
579 ms 211.233.50.4
10 2026-08-25 03:47 639232255723518075
596 ms 211.233.50.4
9 2026-08-25 03:30 639232245484452890
588 ms 211.233.50.4
8 2026-08-25 03:13 639232235157175331
617 ms 211.233.50.4
7 2026-08-25 02:19 639232203197189095
612 ms 211.233.50.4
6 2026-08-25 02:03 639232192844564298
319 ms 211.233.50.4
5 2026-08-25 01:45 639232182496008942
581 ms 211.233.50.4
4 2026-08-25 01:28 639232172197053132
896 ms 211.233.50.4
3 2026-08-25 00:34 639232140250307418
915 ms 211.233.50.4
2 2026-08-25 00:18 639232129927860324
633 ms 211.233.50.4
1 2026-08-25 00:00 639232119551972438
926 ms 211.233.50.4