DNS response history for ns2.tender.pro

ns2.tender.pro 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 36 DNS check records, 36 successful responses, 0 failed responses, and 390 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.tender.pro.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

390 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

31.28.14.147

Most recently resolved hosting IP on selected date

Successful Responses

36

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.tender.pro

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
36 2026-08-26 12:11 639233424567558554
185 ms 31.28.14.147
35 2026-08-26 11:53 639233414056832719
97 ms 31.28.14.147
34 2026-08-26 11:36 639233403515141099
48 ms 31.28.14.147
33 2026-08-26 10:41 639233370841350248
2129 ms 31.28.14.147
32 2026-08-26 10:24 639233360361507238
380 ms 31.28.14.147
31 2026-08-26 10:06 639233350067824371
53 ms 31.28.14.147
30 2026-08-26 09:49 639233339545274518
47 ms 31.28.14.147
29 2026-08-26 09:31 639233329214918079
48 ms 31.28.14.147
28 2026-08-26 09:14 639233318749762337
235 ms 31.28.14.147
27 2026-08-26 08:57 639233308387917838
59 ms 31.28.14.147
26 2026-08-26 08:40 639233297961740122
50 ms 31.28.14.147
25 2026-08-26 08:22 639233287487159094
24 ms 31.28.14.147
24 2026-08-26 08:05 639233276995531707
45 ms 31.28.14.147
23 2026-08-26 07:47 639233266521568229
50 ms 31.28.14.147
22 2026-08-26 07:30 639233256081047431
90 ms 31.28.14.147
21 2026-08-26 06:36 639233223620132921
62 ms 31.28.14.147
20 2026-08-26 06:18 639233213287814244
2008 ms 31.28.14.147
19 2026-08-26 06:01 639233202925983161
49 ms 31.28.14.147
18 2026-08-26 05:44 639233192644780696
91 ms 31.28.14.147
17 2026-08-26 05:27 639233182401183833
8 ms 31.28.14.147
16 2026-08-26 05:10 639233172074181051
287 ms 31.28.14.147
15 2026-08-26 04:53 639233161808421455
46 ms 31.28.14.147
14 2026-08-26 04:35 639233151357344052
9 ms 31.28.14.147
13 2026-08-26 04:18 639233141034116946
2057 ms 31.28.14.147
12 2026-08-26 04:01 639233130828334142
77 ms 31.28.14.147
11 2026-08-26 03:44 639233120373450007
50 ms 31.28.14.147
10 2026-08-26 03:26 639233110066216193
98 ms 31.28.14.147
9 2026-08-26 02:33 639233078065410564
57 ms 31.28.14.147
8 2026-08-26 02:16 639233067787457832
2010 ms 31.28.14.147
7 2026-08-26 01:59 639233057501801162
298 ms 31.28.14.147
6 2026-08-26 01:42 639233047089431703
45 ms 31.28.14.147
5 2026-08-26 01:24 639233036754790688
50 ms 31.28.14.147
4 2026-08-26 01:07 639233026412602472
2054 ms 31.28.14.147
3 2026-08-26 00:50 639233016064066127
55 ms 31.28.14.147
2 2026-08-26 00:33 639233005922655772
303 ms 31.28.14.147
1 2026-08-26 00:16 639232995672256907
772 ms 31.28.14.147