DNS response history for ns2.whyweb.kr

ns2.whyweb.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-28. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 612 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.whyweb.kr.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

612 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 15:12

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

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 ns2.whyweb.kr

Showing DNS history for 2026-08-28 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-28 15:12 639235258803654519
566 ms 218.145.65.144
35 2026-08-28 14:54 639235248596087996
547 ms 218.145.65.144
34 2026-08-28 14:37 639235238225955920
550 ms 218.145.65.144
33 2026-08-28 14:20 639235227727862105
580 ms 218.145.65.144
32 2026-08-28 13:26 639235195230848570
570 ms 218.145.65.144
31 2026-08-28 13:09 639235184840503274
574 ms 218.145.65.144
30 2026-08-28 12:51 639235174453894956
2303 ms 218.145.65.144
29 2026-08-28 12:34 639235163898672622
565 ms 218.145.65.144
28 2026-08-28 11:41 639235132147470568
563 ms 218.145.65.144
27 2026-08-28 11:23 639235121907744088
555 ms 218.145.65.144
26 2026-08-28 11:06 639235111428014262
533 ms 218.145.65.144
25 2026-08-28 10:49 639235100921813626
583 ms 218.145.65.144
24 2026-08-28 09:55 639235068670703481
554 ms 218.145.65.144
23 2026-08-28 09:38 639235058337459445
547 ms 218.145.65.144
22 2026-08-28 09:20 639235047825109146
572 ms 218.145.65.144
21 2026-08-28 09:03 639235037383229033
577 ms 218.145.65.144
20 2026-08-28 08:09 639235005619242711
548 ms 218.145.65.144
19 2026-08-28 07:53 639234995310346584
553 ms 218.145.65.144
18 2026-08-28 07:35 639234984946548933
565 ms 218.145.65.144
17 2026-08-28 07:18 639234974608077290
574 ms 218.145.65.144
16 2026-08-28 06:24 639234942529845595
565 ms 218.145.65.144
15 2026-08-28 06:07 639234932259126627
536 ms 218.145.65.144
14 2026-08-28 05:50 639234921916735988
584 ms 218.145.65.144
13 2026-08-28 05:33 639234911470038027
567 ms 218.145.65.144
12 2026-08-28 04:40 639234879588411654
557 ms 218.145.65.144
11 2026-08-28 04:23 639234869341589104
553 ms 218.145.65.144
10 2026-08-28 04:05 639234859012216675
575 ms 218.145.65.144
9 2026-08-28 03:48 639234848695364934
582 ms 218.145.65.144
8 2026-08-28 02:55 639234816952458162
552 ms 218.145.65.144
7 2026-08-28 02:38 639234806773081598
542 ms 218.145.65.144
6 2026-08-28 02:21 639234796382955255
593 ms 218.145.65.144
5 2026-08-28 02:04 639234786015782563
580 ms 218.145.65.144
4 2026-08-28 01:10 639234753811917646
560 ms 218.145.65.144
3 2026-08-28 00:53 639234743739767811
547 ms 218.145.65.144
2 2026-08-28 00:36 639234733372362811
566 ms 218.145.65.144
1 2026-08-28 00:19 639234723048550337
577 ms 218.145.65.144