DNS response history for ns.fdikorea.com

ns.fdikorea.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-27. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 567 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.fdikorea.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

567 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

59.17.207.148

Most recently resolved hosting IP on selected date

Successful Responses

30

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

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
30 2026-08-27 09:51 639234202117531850
592 ms 59.17.207.148
29 2026-08-27 09:33 639234191649612722
566 ms 59.17.207.148
28 2026-08-27 09:16 639234181105879568
568 ms 59.17.207.148
27 2026-08-27 08:58 639234170713214496
558 ms 59.17.207.148
26 2026-08-27 08:41 639234160341037652
565 ms 59.17.207.148
25 2026-08-27 08:24 639234149799404224
573 ms 59.17.207.148
24 2026-08-27 08:06 639234139553286469
558 ms 59.17.207.148
23 2026-08-27 07:13 639234107183588293
581 ms 59.17.207.148
22 2026-08-27 06:55 639234096905435724
569 ms 59.17.207.148
21 2026-08-27 06:38 639234086579410775
576 ms 59.17.207.148
20 2026-08-27 06:21 639234076291157956
566 ms 59.17.207.148
19 2026-08-27 06:04 639234065981939454
570 ms 59.17.207.148
18 2026-08-27 05:47 639234055548642997
569 ms 59.17.207.148
17 2026-08-27 05:29 639234045267979603
568 ms 59.17.207.148
16 2026-08-27 05:12 639234034999717463
572 ms 59.17.207.148
15 2026-08-27 04:55 639234024739225358
572 ms 59.17.207.148
14 2026-08-27 04:38 639234014311170162
573 ms 59.17.207.148
13 2026-08-27 04:20 639234003806017640
567 ms 59.17.207.148
12 2026-08-27 04:03 639233993356203030
539 ms 59.17.207.148
11 2026-08-27 03:09 639233961301716608
566 ms 59.17.207.148
10 2026-08-27 02:52 639233950834200647
565 ms 59.17.207.148
9 2026-08-27 02:35 639233940431849026
565 ms 59.17.207.148
8 2026-08-27 02:17 639233930110596398
559 ms 59.17.207.148
7 2026-08-27 02:00 639233919705434540
570 ms 59.17.207.148
6 2026-08-27 01:43 639233909452807845
574 ms 59.17.207.148
5 2026-08-27 01:26 639233899096420820
573 ms 59.17.207.148
4 2026-08-27 01:09 639233888707824939
573 ms 59.17.207.148
3 2026-08-27 00:51 639233878461203802
544 ms 59.17.207.148
2 2026-08-27 00:34 639233868060868209
560 ms 59.17.207.148
1 2026-08-27 00:17 639233857450922991
564 ms 59.17.207.148