DNS response history for ns1.republicrenaissance.com

ns1.republicrenaissance.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-25. For this date, NameServerHistory found 30 DNS check records, 28 successful responses, 2 failed responses, and 221 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 ns1.republicrenaissance.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

221 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.160.145.176

Most recently resolved hosting IP on selected date

Successful Responses

28

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

7%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.republicrenaissance.com

Showing DNS history for 2026-08-25 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
30 2026-08-25 10:21 639232492740373468
3 ms 103.160.145.176
29 2026-08-25 10:04 639232482235303141
9 ms 103.160.145.176
28 2026-08-25 09:46 639232471861770303
266 ms 103.160.145.176
27 2026-08-25 09:29 639232461630217327
255 ms 103.160.145.176
26 2026-08-25 09:12 639232451282965990
267 ms 103.160.145.176
25 2026-08-25 08:55 639232440814614938
4 ms 103.160.145.176
24 2026-08-25 08:37 639232430410720425
-
23 2026-08-25 08:20 639232420003096185
269 ms 103.160.145.176
22 2026-08-25 08:02 639232409467287444
3 ms 103.160.145.176
21 2026-08-25 07:45 639232399077195997
4 ms 103.160.145.176
20 2026-08-25 07:28 639232388731528337
267 ms 103.160.145.176
19 2026-08-25 07:10 639232378288598612
268 ms 103.160.145.176
18 2026-08-25 06:17 639232346196373643
265 ms 103.160.145.176
17 2026-08-25 06:00 639232336112370741
270 ms 103.160.145.176
16 2026-08-25 05:43 639232326146508970
263 ms 103.160.145.176
15 2026-08-25 05:26 639232316189381720
258 ms 103.160.145.176
14 2026-08-25 05:10 639232306217998913
-
13 2026-08-25 04:53 639232296255744174
279 ms 103.160.145.176
12 2026-08-25 04:36 639232286095760789
258 ms 103.160.145.176
11 2026-08-25 04:19 639232276086186273
282 ms 103.160.145.176
10 2026-08-25 04:03 639232265900986425
257 ms 103.160.145.176
9 2026-08-25 03:46 639232255723518075
276 ms 103.160.145.176
8 2026-08-25 03:29 639232245484452890
280 ms 103.160.145.176
7 2026-08-25 03:12 639232235157175331
255 ms 103.160.145.176
6 2026-08-25 02:18 639232203197189095
193 ms 103.160.145.176
5 2026-08-25 02:01 639232192844564298
293 ms 103.160.145.176
4 2026-08-25 01:44 639232182496008942
279 ms 103.160.145.176
3 2026-08-25 01:27 639232172197053132
293 ms 103.160.145.176
2 2026-08-25 00:33 639232140250307418
302 ms 103.160.145.176
1 2026-08-25 00:16 639232129927860324
264 ms 103.160.145.176