DNS response history for ns2.svyaz-telekom.ru

ns2.svyaz-telekom.ru 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 37 DNS check records, 37 successful responses, 0 failed responses, and 315 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.svyaz-telekom.ru.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

315 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

134.19.151.187

Most recently resolved hosting IP on selected date

Successful Responses

37

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.svyaz-telekom.ru

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
37 2026-08-26 12:27 639233434974187439
94 ms 134.19.151.187
36 2026-08-26 12:10 639233424567558554
115 ms 134.19.151.187
35 2026-08-26 11:52 639233414056832719
87 ms 134.19.151.187
34 2026-08-26 11:34 639233403515141099
187 ms 134.19.151.187
33 2026-08-26 10:40 639233370841350248
2064 ms 134.19.151.187
32 2026-08-26 10:23 639233360361507238
130 ms 134.19.151.187
31 2026-08-26 10:05 639233350067824371
61 ms 134.19.151.187
30 2026-08-26 09:48 639233339545274518
63 ms 134.19.151.187
29 2026-08-26 09:30 639233329214918079
126 ms 134.19.151.187
28 2026-08-26 09:13 639233318749762337
164 ms 134.19.151.187
27 2026-08-26 08:56 639233308387917838
131 ms 134.19.151.187
26 2026-08-26 08:39 639233297961740122
2101 ms 134.19.151.187
25 2026-08-26 08:21 639233287487159094
154 ms 134.19.151.187
24 2026-08-26 08:04 639233276995531707
2154 ms 134.19.151.187
23 2026-08-26 07:46 639233266521568229
7 ms 134.19.151.187
22 2026-08-26 07:29 639233256081047431
60 ms 134.19.151.187
21 2026-08-26 06:35 639233223620132921
126 ms 134.19.151.187
20 2026-08-26 06:17 639233213287814244
158 ms 134.19.151.187
19 2026-08-26 06:00 639233202925983161
209 ms 134.19.151.187
18 2026-08-26 05:43 639233192644780696
7 ms 134.19.151.187
17 2026-08-26 05:26 639233182401183833
57 ms 134.19.151.187
16 2026-08-26 05:09 639233172074181051
212 ms 134.19.151.187
15 2026-08-26 04:52 639233161808421455
59 ms 134.19.151.187
14 2026-08-26 04:34 639233151357344052
56 ms 134.19.151.187
13 2026-08-26 04:17 639233141034116946
54 ms 134.19.151.187
12 2026-08-26 04:00 639233130828334142
55 ms 134.19.151.187
11 2026-08-26 03:43 639233120373450007
8 ms 134.19.151.187
10 2026-08-26 03:25 639233110066216193
127 ms 134.19.151.187
9 2026-08-26 02:32 639233078065410564
136 ms 134.19.151.187
8 2026-08-26 02:15 639233067787457832
136 ms 134.19.151.187
7 2026-08-26 01:58 639233057501801162
131 ms 134.19.151.187
6 2026-08-26 01:40 639233047089431703
154 ms 134.19.151.187
5 2026-08-26 01:23 639233036754790688
159 ms 134.19.151.187
4 2026-08-26 01:06 639233026412602472
32 ms 134.19.151.187
3 2026-08-26 00:49 639233016064066127
7 ms 134.19.151.187
2 2026-08-26 00:32 639233005922655772
2007 ms 134.19.151.187
1 2026-08-26 00:15 639232995672256907
70 ms 134.19.151.187