DNS response history for ns2.svyazcom.org

ns2.svyazcom.org 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 813 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.svyazcom.org.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

813 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

95.172.133.175

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.svyazcom.org

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:15 639233424567558554
2009 ms 95.172.133.175
36 2026-08-26 11:58 639233414056832719
353 ms 95.172.133.175
35 2026-08-26 11:40 639233403515141099
445 ms 95.172.133.175
34 2026-08-26 10:46 639233370841350248
366 ms 95.172.133.175
33 2026-08-26 10:28 639233360361507238
94 ms 95.172.133.175
32 2026-08-26 10:11 639233350067824371
3675 ms 95.172.133.175
31 2026-08-26 09:54 639233339545274518
3863 ms 95.172.133.175
30 2026-08-26 09:36 639233329214918079
2032 ms 95.172.133.175
29 2026-08-26 09:19 639233318749762337
245 ms 95.172.133.175
28 2026-08-26 09:02 639233308387917838
581 ms 95.172.133.175
27 2026-08-26 08:44 639233297961740122
2009 ms 95.172.133.175
26 2026-08-26 08:27 639233287487159094
434 ms 95.172.133.175
25 2026-08-26 08:10 639233276995531707
360 ms 95.172.133.175
24 2026-08-26 07:52 639233266521568229
465 ms 95.172.133.175
23 2026-08-26 07:34 639233256081047431
453 ms 95.172.133.175
22 2026-08-26 06:40 639233223620132921
266 ms 95.172.133.175
21 2026-08-26 06:23 639233213287814244
577 ms 95.172.133.175
20 2026-08-26 06:06 639233202925983161
343 ms 95.172.133.175
19 2026-08-26 05:49 639233192644780696
395 ms 95.172.133.175
18 2026-08-26 05:31 639233182401183833
353 ms 95.172.133.175
17 2026-08-26 05:14 639233172074181051
2008 ms 95.172.133.175
16 2026-08-26 04:57 639233161808421455
386 ms 95.172.133.175
15 2026-08-26 04:40 639233151357344052
324 ms 95.172.133.175
14 2026-08-26 04:23 639233141034116946
198 ms 95.172.133.175
13 2026-08-26 04:05 639233130828334142
2112 ms 95.172.133.175
12 2026-08-26 03:48 639233120373450007
336 ms 95.172.133.175
11 2026-08-26 03:31 639233110066216193
306 ms 95.172.133.175
10 2026-08-26 02:38 639233078065410564
204 ms 95.172.133.175
9 2026-08-26 02:21 639233067787457832
354 ms 95.172.133.175
8 2026-08-26 02:03 639233057501801162
192 ms 95.172.133.175
7 2026-08-26 01:46 639233047089431703
211 ms 95.172.133.175
6 2026-08-26 01:29 639233036754790688
98 ms 95.172.133.175
5 2026-08-26 01:12 639233026412602472
819 ms 95.172.133.175
4 2026-08-26 00:54 639233016064066127
2008 ms 95.172.133.175
3 2026-08-26 00:37 639233005922655772
420 ms 95.172.133.175
2 2026-08-26 00:20 639232995672256907
456 ms 95.172.133.175
1 2026-08-26 00:03 639232985300872416
335 ms 95.172.133.175