DNS response history for ns2.telepark.tv

ns2.telepark.tv 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 33 DNS check records, 33 successful responses, 0 failed responses, and 331 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.telepark.tv.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

331 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.136.97.122

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 ns2.telepark.tv

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
33 2026-08-26 10:36 639233370841350248
7 ms 185.136.97.122
32 2026-08-26 10:18 639233360361507238
9 ms 185.136.97.122
31 2026-08-26 10:01 639233350067824371
2041 ms 185.136.97.122
30 2026-08-26 09:44 639233339545274518
14 ms 185.136.97.122
29 2026-08-26 09:26 639233329214918079
36 ms 185.136.97.122
28 2026-08-26 09:09 639233318749762337
30 ms 185.136.97.122
27 2026-08-26 08:52 639233308387917838
22 ms 185.136.97.122
26 2026-08-26 08:34 639233297961740122
37 ms 185.136.97.122
25 2026-08-26 08:17 639233287487159094
9 ms 185.136.97.122
24 2026-08-26 08:00 639233276995531707
2017 ms 185.136.97.122
23 2026-08-26 07:42 639233266521568229
31 ms 185.136.97.122
22 2026-08-26 07:25 639233256081047431
36 ms 185.136.97.122
21 2026-08-26 06:31 639233223620132921
18 ms 185.136.97.122
20 2026-08-26 06:13 639233213287814244
2035 ms 185.136.97.122
19 2026-08-26 05:56 639233202925983161
26 ms 185.136.97.122
18 2026-08-26 05:39 639233192644780696
33 ms 185.136.97.122
17 2026-08-26 05:22 639233182401183833
62 ms 185.136.97.122
16 2026-08-26 05:05 639233172074181051
41 ms 185.136.97.122
15 2026-08-26 04:48 639233161808421455
33 ms 185.136.97.122
14 2026-08-26 04:30 639233151357344052
66 ms 185.136.97.122
13 2026-08-26 04:13 639233141034116946
21 ms 185.136.97.122
12 2026-08-26 03:56 639233130828334142
2010 ms 185.136.97.122
11 2026-08-26 03:38 639233120373450007
24 ms 185.136.97.122
10 2026-08-26 03:21 639233110066216193
25 ms 185.136.97.122
9 2026-08-26 02:28 639233078065410564
83 ms 185.136.97.122
8 2026-08-26 02:11 639233067787457832
31 ms 185.136.97.122
7 2026-08-26 01:54 639233057501801162
11 ms 185.136.97.122
6 2026-08-26 01:36 639233047089431703
17 ms 185.136.97.122
5 2026-08-26 01:19 639233036754790688
8 ms 185.136.97.122
4 2026-08-26 01:02 639233026412602472
5 ms 185.136.97.122
3 2026-08-26 00:45 639233016064066127
32 ms 185.136.97.122
2 2026-08-26 00:28 639233005922655772
2016 ms 185.136.97.122
1 2026-08-26 00:11 639232995672256907
48 ms 185.136.97.122