DNS response history for ns.sayurijapan.co.kr

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

34

Historical checks stored for this nameserver on selected date

Average Latency

614 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

218.145.65.143

Most recently resolved hosting IP on selected date

Successful Responses

34

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.sayurijapan.co.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
34 2026-08-27 11:00 639234243654907465
563 ms 218.145.65.143
33 2026-08-27 10:42 639234233269654413
566 ms 218.145.65.143
32 2026-08-27 10:25 639234222943951923
577 ms 218.145.65.143
31 2026-08-27 10:08 639234212558002823
556 ms 218.145.65.143
30 2026-08-27 09:51 639234202117531850
558 ms 218.145.65.143
29 2026-08-27 09:33 639234191649612722
556 ms 218.145.65.143
28 2026-08-27 09:16 639234181105879568
563 ms 218.145.65.143
27 2026-08-27 08:58 639234170713214496
562 ms 218.145.65.143
26 2026-08-27 08:41 639234160341037652
578 ms 218.145.65.143
25 2026-08-27 08:23 639234149799404224
2735 ms 218.145.65.143
24 2026-08-27 08:06 639234139553286469
577 ms 218.145.65.143
23 2026-08-27 07:12 639234107183588293
563 ms 218.145.65.143
22 2026-08-27 06:55 639234096905435724
568 ms 218.145.65.143
21 2026-08-27 06:38 639234086579410775
561 ms 218.145.65.143
20 2026-08-27 06:21 639234076291157956
571 ms 218.145.65.143
19 2026-08-27 06:04 639234065981939454
571 ms 218.145.65.143
18 2026-08-27 05:46 639234055548642997
562 ms 218.145.65.143
17 2026-08-27 05:29 639234045267979603
571 ms 218.145.65.143
16 2026-08-27 05:12 639234034999717463
579 ms 218.145.65.143
15 2026-08-27 04:55 639234024739225358
579 ms 218.145.65.143
14 2026-08-27 04:38 639234014311170162
552 ms 218.145.65.143
13 2026-08-27 04:20 639234003806017640
575 ms 218.145.65.143
12 2026-08-27 04:03 639233993356203030
586 ms 218.145.65.143
11 2026-08-27 03:09 639233961301716608
564 ms 218.145.65.143
10 2026-08-27 02:52 639233950834200647
560 ms 218.145.65.143
9 2026-08-27 02:34 639233940431849026
3 ms 218.145.65.143
8 2026-08-27 02:17 639233930110596398
552 ms 218.145.65.143
7 2026-08-27 02:00 639233919705434540
563 ms 218.145.65.143
6 2026-08-27 01:43 639233909452807845
574 ms 218.145.65.143
5 2026-08-27 01:25 639233899096420820
563 ms 218.145.65.143
4 2026-08-27 01:08 639233888707824939
568 ms 218.145.65.143
3 2026-08-27 00:51 639233878461203802
564 ms 218.145.65.143
2 2026-08-27 00:34 639233868060868209
575 ms 218.145.65.143
1 2026-08-27 00:16 639233857450922991
571 ms 218.145.65.143