DNS response history for ns2.therenaissanceleague.com

ns2.therenaissanceleague.com 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 31 DNS check records, 31 successful responses, 0 failed responses, and 289 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.therenaissanceleague.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

289 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

199.192.26.186

Most recently resolved hosting IP on selected date

Successful Responses

31

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.therenaissanceleague.com

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
31 2026-08-26 10:05 639233350067824371
251 ms 199.192.26.186
30 2026-08-26 09:48 639233339545274518
266 ms 199.192.26.186
29 2026-08-26 09:30 639233329214918079
162 ms 199.192.26.186
28 2026-08-26 09:13 639233318749762337
268 ms 199.192.26.186
27 2026-08-26 08:56 639233308387917838
247 ms 199.192.26.186
26 2026-08-26 08:38 639233297961740122
244 ms 199.192.26.186
25 2026-08-26 08:21 639233287487159094
242 ms 199.192.26.186
24 2026-08-26 08:04 639233276995531707
254 ms 199.192.26.186
23 2026-08-26 07:46 639233266521568229
247 ms 199.192.26.186
22 2026-08-26 07:29 639233256081047431
229 ms 199.192.26.186
21 2026-08-26 06:35 639233223620132921
237 ms 199.192.26.186
20 2026-08-26 06:17 639233213287814244
2253 ms 199.192.26.186
19 2026-08-26 06:00 639233202925983161
131 ms 199.192.26.186
18 2026-08-26 05:43 639233192644780696
242 ms 199.192.26.186
17 2026-08-26 05:26 639233182401183833
236 ms 199.192.26.186
16 2026-08-26 05:09 639233172074181051
131 ms 199.192.26.186
15 2026-08-26 04:51 639233161808421455
243 ms 199.192.26.186
14 2026-08-26 04:34 639233151357344052
254 ms 199.192.26.186
13 2026-08-26 04:17 639233141034116946
236 ms 199.192.26.186
12 2026-08-26 04:00 639233130828334142
3 ms 199.192.26.186
11 2026-08-26 03:43 639233120373450007
343 ms 199.192.26.186
10 2026-08-26 03:25 639233110066216193
245 ms 199.192.26.186
9 2026-08-26 02:32 639233078065410564
246 ms 199.192.26.186
8 2026-08-26 02:15 639233067787457832
233 ms 199.192.26.186
7 2026-08-26 01:58 639233057501801162
244 ms 199.192.26.186
6 2026-08-26 01:40 639233047089431703
159 ms 199.192.26.186
5 2026-08-26 01:23 639233036754790688
240 ms 199.192.26.186
4 2026-08-26 01:06 639233026412602472
238 ms 199.192.26.186
3 2026-08-26 00:49 639233016064066127
241 ms 199.192.26.186
2 2026-08-26 00:32 639233005922655772
246 ms 199.192.26.186
1 2026-08-26 00:15 639232995672256907
146 ms 199.192.26.186