DNS response history for ns2.wccoupling.co.kr

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

35

Historical checks stored for this nameserver on selected date

Average Latency

743 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

218.145.65.144

Most recently resolved hosting IP on selected date

Successful Responses

35

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.wccoupling.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
35 2026-08-25 12:08 639232556111768563
1204 ms 218.145.65.144
34 2026-08-25 11:50 639232545839529039
4 ms 218.145.65.144
33 2026-08-25 11:33 639232535349285207
585 ms 218.145.65.144
32 2026-08-25 11:16 639232524938080723
1140 ms 218.145.65.144
31 2026-08-25 10:22 639232492740373468
5 ms 218.145.65.144
30 2026-08-25 10:05 639232482235303141
1195 ms 218.145.65.144
29 2026-08-25 09:47 639232471861770303
596 ms 218.145.65.144
28 2026-08-25 09:30 639232461630217327
872 ms 218.145.65.144
27 2026-08-25 09:13 639232451282965990
873 ms 218.145.65.144
26 2026-08-25 08:56 639232440814614938
901 ms 218.145.65.144
25 2026-08-25 08:38 639232430410720425
593 ms 218.145.65.144
24 2026-08-25 08:21 639232420003096185
905 ms 218.145.65.144
23 2026-08-25 08:03 639232409467287444
1192 ms 218.145.65.144
22 2026-08-25 07:46 639232399077195997
890 ms 218.145.65.144
21 2026-08-25 07:29 639232388731528337
290 ms 218.145.65.144
20 2026-08-25 07:11 639232378288598612
900 ms 218.145.65.144
19 2026-08-25 06:17 639232346196373643
602 ms 218.145.65.144
18 2026-08-25 06:01 639232336112370741
968 ms 218.145.65.144
17 2026-08-25 05:44 639232326146508970
882 ms 218.145.65.144
16 2026-08-25 05:27 639232316189381720
298 ms 218.145.65.144
15 2026-08-25 05:11 639232306217998913
3 ms 218.145.65.144
14 2026-08-25 04:54 639232296255744174
915 ms 218.145.65.144
13 2026-08-25 04:37 639232286095760789
2 ms 218.145.65.144
12 2026-08-25 04:20 639232276086186273
910 ms 218.145.65.144
11 2026-08-25 04:04 639232265900986425
867 ms 218.145.65.144
10 2026-08-25 03:47 639232255723518075
920 ms 218.145.65.144
9 2026-08-25 03:30 639232245484452890
616 ms 218.145.65.144
8 2026-08-25 03:13 639232235157175331
1209 ms 218.145.65.144
7 2026-08-25 02:19 639232203197189095
3 ms 218.145.65.144
6 2026-08-25 02:02 639232192844564298
1179 ms 218.145.65.144
5 2026-08-25 01:45 639232182496008942
867 ms 218.145.65.144
4 2026-08-25 01:28 639232172197053132
904 ms 218.145.65.144
3 2026-08-25 00:34 639232140250307418
598 ms 218.145.65.144
2 2026-08-25 00:17 639232129927860324
1216 ms 218.145.65.144
1 2026-08-25 00:00 639232119551972438
916 ms 218.145.65.144