DNS response history for parco.kdts.net

parco.kdts.net 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-26. For this date, NameServerHistory found 39 DNS check records, 39 successful responses, 0 failed responses, and 587 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 parco.kdts.net.
Records on Selected Date

39

Historical checks stored for this nameserver on selected date

Average Latency

587 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:49

All timestamps shown in UTC

Latest Resolved IP on Selected Date

36.52.207.97

Most recently resolved hosting IP on selected date

Successful Responses

39

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 parco.kdts.net

Showing DNS history for 2026-08-26 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
39 2026-08-26 12:49 639233445367152284
974 ms 36.52.207.97
38 2026-08-26 12:32 639233434974187439
776 ms 36.52.207.97
37 2026-08-26 12:15 639233424567558554
884 ms 36.52.207.97
36 2026-08-26 11:57 639233414056832719
607 ms 36.52.207.97
35 2026-08-26 11:40 639233403515141099
613 ms 36.52.207.97
34 2026-08-26 10:45 639233370841350248
544 ms 36.52.207.97
33 2026-08-26 10:28 639233360361507238
705 ms 36.52.207.97
32 2026-08-26 10:11 639233350067824371
761 ms 36.52.207.97
31 2026-08-26 09:53 639233339545274518
543 ms 36.52.207.97
30 2026-08-26 09:36 639233329214918079
507 ms 36.52.207.97
29 2026-08-26 09:19 639233318749762337
537 ms 36.52.207.97
28 2026-08-26 09:01 639233308387917838
501 ms 36.52.207.97
27 2026-08-26 08:44 639233297961740122
504 ms 36.52.207.97
26 2026-08-26 08:26 639233287487159094
510 ms 36.52.207.97
25 2026-08-26 08:09 639233276995531707
599 ms 36.52.207.97
24 2026-08-26 07:51 639233266521568229
493 ms 36.52.207.97
23 2026-08-26 07:34 639233256081047431
485 ms 36.52.207.97
22 2026-08-26 06:40 639233223620132921
484 ms 36.52.207.97
21 2026-08-26 06:23 639233213287814244
486 ms 36.52.207.97
20 2026-08-26 06:05 639233202925983161
487 ms 36.52.207.97
19 2026-08-26 05:48 639233192644780696
487 ms 36.52.207.97
18 2026-08-26 05:31 639233182401183833
495 ms 36.52.207.97
17 2026-08-26 05:14 639233172074181051
263 ms 36.52.207.97
16 2026-08-26 04:57 639233161808421455
493 ms 36.52.207.97
15 2026-08-26 04:40 639233151357344052
492 ms 36.52.207.97
14 2026-08-26 04:22 639233141034116946
494 ms 36.52.207.97
13 2026-08-26 04:05 639233130828334142
489 ms 36.52.207.97
12 2026-08-26 03:48 639233120373450007
500 ms 36.52.207.97
11 2026-08-26 03:30 639233110066216193
482 ms 36.52.207.97
10 2026-08-26 02:37 639233078065410564
493 ms 36.52.207.97
9 2026-08-26 02:20 639233067787457832
491 ms 36.52.207.97
8 2026-08-26 02:03 639233057501801162
494 ms 36.52.207.97
7 2026-08-26 01:46 639233047089431703
503 ms 36.52.207.97
6 2026-08-26 01:28 639233036754790688
484 ms 36.52.207.97
5 2026-08-26 01:11 639233026412602472
486 ms 36.52.207.97
4 2026-08-26 00:54 639233016064066127
497 ms 36.52.207.97
3 2026-08-26 00:37 639233005922655772
2258 ms 36.52.207.97
2 2026-08-26 00:20 639232995672256907
492 ms 36.52.207.97
1 2026-08-26 00:03 639232985300872416
487 ms 36.52.207.97