DNS response history for ns.eartsquare.kr

ns.eartsquare.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-27. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 1262 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 ns.eartsquare.kr.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

1262 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

220.80.111.41

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns.eartsquare.kr

Showing DNS history for 2026-08-27 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
33 2026-08-27 10:27 639234222943951923
1258 ms 220.80.111.41
32 2026-08-27 10:09 639234212558002823
1217 ms 220.80.111.41
31 2026-08-27 09:52 639234202117531850
1198 ms 220.80.111.41
30 2026-08-27 09:35 639234191649612722
1458 ms 220.80.111.41
29 2026-08-27 09:17 639234181105879568
1254 ms 220.80.111.41
28 2026-08-27 09:00 639234170713214496
1680 ms 220.80.111.41
27 2026-08-27 08:43 639234160341037652
1682 ms 220.80.111.41
26 2026-08-27 08:25 639234149799404224
1439 ms 220.80.111.41
25 2026-08-27 08:08 639234139553286469
1233 ms 220.80.111.41
24 2026-08-27 07:14 639234107183588293
1223 ms 220.80.111.41
23 2026-08-27 06:57 639234096905435724
1232 ms 220.80.111.41
22 2026-08-27 06:39 639234086579410775
1200 ms 220.80.111.41
21 2026-08-27 06:22 639234076291157956
1192 ms 220.80.111.41
20 2026-08-27 06:05 639234065981939454
1222 ms 220.80.111.41
19 2026-08-27 05:48 639234055548642997
1225 ms 220.80.111.41
18 2026-08-27 05:30 639234045267979603
1221 ms 220.80.111.41
17 2026-08-27 05:13 639234034999717463
1198 ms 220.80.111.41
16 2026-08-27 04:56 639234024739225358
1192 ms 220.80.111.41
15 2026-08-27 04:39 639234014311170162
1199 ms 220.80.111.41
14 2026-08-27 04:22 639234003806017640
1212 ms 220.80.111.41
13 2026-08-27 04:04 639233993356203030
1207 ms 220.80.111.41
12 2026-08-27 03:11 639233961301716608
1226 ms 220.80.111.41
11 2026-08-27 02:53 639233950834200647
1219 ms 220.80.111.41
10 2026-08-27 02:36 639233940431849026
1211 ms 220.80.111.41
9 2026-08-27 02:19 639233930110596398
1218 ms 220.80.111.41
8 2026-08-27 02:01 639233919705434540
1233 ms 220.80.111.41
7 2026-08-27 01:44 639233909452807845
1927 ms 220.80.111.41
6 2026-08-27 01:27 639233899096420820
1201 ms 220.80.111.41
5 2026-08-27 01:10 639233888707824939
1196 ms 220.80.111.41
4 2026-08-27 00:52 639233878461203802
1220 ms 220.80.111.41
3 2026-08-27 00:35 639233868060868209
609 ms 220.80.111.41
2 2026-08-27 00:18 639233857450922991
1233 ms 220.80.111.41
1 2026-08-27 00:00 639233846871926285
1214 ms 220.80.111.41