DNS response history for ns2.webhostingkorea.com

ns2.webhostingkorea.com 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 1218 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.webhostingkorea.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

1218 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

121.254.222.10

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.webhostingkorea.com

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:09 639232556111768563
1198 ms 121.254.222.10
34 2026-08-25 11:51 639232545839529039
1181 ms 121.254.222.10
33 2026-08-25 11:34 639232535349285207
1222 ms 121.254.222.10
32 2026-08-25 11:17 639232524938080723
1196 ms 121.254.222.10
31 2026-08-25 10:23 639232492740373468
1216 ms 121.254.222.10
30 2026-08-25 10:06 639232482235303141
1192 ms 121.254.222.10
29 2026-08-25 09:48 639232471861770303
1243 ms 121.254.222.10
28 2026-08-25 09:31 639232461630217327
1231 ms 121.254.222.10
27 2026-08-25 09:14 639232451282965990
1149 ms 121.254.222.10
26 2026-08-25 08:57 639232440814614938
1485 ms 121.254.222.10
25 2026-08-25 08:39 639232430410720425
1259 ms 121.254.222.10
24 2026-08-25 08:22 639232420003096185
1220 ms 121.254.222.10
23 2026-08-25 08:05 639232409467287444
1205 ms 121.254.222.10
22 2026-08-25 07:47 639232399077195997
1241 ms 121.254.222.10
21 2026-08-25 07:30 639232388731528337
1231 ms 121.254.222.10
20 2026-08-25 07:12 639232378288598612
1169 ms 121.254.222.10
19 2026-08-25 06:18 639232346196373643
1279 ms 121.254.222.10
18 2026-08-25 06:02 639232336112370741
1185 ms 121.254.222.10
17 2026-08-25 05:45 639232326146508970
1238 ms 121.254.222.10
16 2026-08-25 05:28 639232316189381720
1231 ms 121.254.222.10
15 2026-08-25 05:12 639232306217998913
1194 ms 121.254.222.10
14 2026-08-25 04:55 639232296255744174
1192 ms 121.254.222.10
13 2026-08-25 04:38 639232286095760789
1203 ms 121.254.222.10
12 2026-08-25 04:21 639232276086186273
1220 ms 121.254.222.10
11 2026-08-25 04:05 639232265900986425
1166 ms 121.254.222.10
10 2026-08-25 03:48 639232255723518075
1220 ms 121.254.222.10
9 2026-08-25 03:31 639232245484452890
1161 ms 121.254.222.10
8 2026-08-25 03:14 639232235157175331
1218 ms 121.254.222.10
7 2026-08-25 02:20 639232203197189095
1195 ms 121.254.222.10
6 2026-08-25 02:03 639232192844564298
1200 ms 121.254.222.10
5 2026-08-25 01:46 639232182496008942
1220 ms 121.254.222.10
4 2026-08-25 01:29 639232172197053132
1241 ms 121.254.222.10
3 2026-08-25 00:35 639232140250307418
1216 ms 121.254.222.10
2 2026-08-25 00:18 639232129927860324
1240 ms 121.254.222.10
1 2026-08-25 00:01 639232119551972438
1189 ms 121.254.222.10