DNS response history for ns2.rte.party

ns2.rte.party 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 35 DNS check records, 35 successful responses, 0 failed responses, and 264 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.rte.party.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

264 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:37

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.38.132.55

Most recently resolved hosting IP on selected date

Successful Responses

35

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.rte.party

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
35 2026-08-26 11:37 639233403515141099
28 ms 51.38.132.55
34 2026-08-26 10:42 639233370841350248
12 ms 51.38.132.55
33 2026-08-26 10:25 639233360361507238
13 ms 51.38.132.55
32 2026-08-26 10:08 639233350067824371
11 ms 51.38.132.55
31 2026-08-26 09:51 639233339545274518
14 ms 51.38.132.55
30 2026-08-26 09:33 639233329214918079
28 ms 51.38.132.55
29 2026-08-26 09:16 639233318749762337
20 ms 51.38.132.55
28 2026-08-26 08:58 639233308387917838
13 ms 51.38.132.55
27 2026-08-26 08:41 639233297961740122
12 ms 51.38.132.55
26 2026-08-26 08:24 639233287487159094
20 ms 51.38.132.55
25 2026-08-26 08:06 639233276995531707
14 ms 51.38.132.55
24 2026-08-26 07:49 639233266521568229
11 ms 51.38.132.55
23 2026-08-26 07:31 639233256081047431
13 ms 51.38.132.55
22 2026-08-26 06:37 639233223620132921
2046 ms 51.38.132.55
21 2026-08-26 06:20 639233213287814244
11 ms 51.38.132.55
20 2026-08-26 06:03 639233202925983161
11 ms 51.38.132.55
19 2026-08-26 05:45 639233192644780696
20 ms 51.38.132.55
18 2026-08-26 05:28 639233182401183833
11 ms 51.38.132.55
17 2026-08-26 05:11 639233172074181051
19 ms 51.38.132.55
16 2026-08-26 04:54 639233161808421455
25 ms 51.38.132.55
15 2026-08-26 04:37 639233151357344052
33 ms 51.38.132.55
14 2026-08-26 04:19 639233141034116946
51 ms 51.38.132.55
13 2026-08-26 04:02 639233130828334142
11 ms 51.38.132.55
12 2026-08-26 03:45 639233120373450007
1527 ms 51.38.132.55
11 2026-08-26 03:28 639233110066216193
2033 ms 51.38.132.55
10 2026-08-26 02:34 639233078065410564
33 ms 51.38.132.55
9 2026-08-26 02:17 639233067787457832
1532 ms 51.38.132.55
8 2026-08-26 02:00 639233057501801162
20 ms 51.38.132.55
7 2026-08-26 01:43 639233047089431703
13 ms 51.38.132.55
6 2026-08-26 01:26 639233036754790688
12 ms 51.38.132.55
5 2026-08-26 01:09 639233026412602472
13 ms 51.38.132.55
4 2026-08-26 00:51 639233016064066127
13 ms 51.38.132.55
3 2026-08-26 00:34 639233005922655772
20 ms 51.38.132.55
2 2026-08-26 00:17 639232995672256907
1544 ms 51.38.132.55
1 2026-08-26 00:00 639232985300872416
25 ms 51.38.132.55