DNS response history for ns3.uptimeforge.com

ns3.uptimeforge.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-24. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 204 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 ns3.uptimeforge.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

204 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 11:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

141.164.45.163

Most recently resolved hosting IP on selected date

Successful Responses

28

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 ns3.uptimeforge.com

Showing DNS history for 2026-08-24 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
28 2026-08-24 11:45 639231683712487276
29 ms 141.164.45.163
27 2026-08-24 11:28 639231673513573868
47 ms 141.164.45.163
26 2026-08-24 10:35 639231641791249939
65 ms 141.164.45.163
25 2026-08-24 10:18 639231631866211033
29 ms 141.164.45.163
24 2026-08-24 10:01 639231621644955316
16 ms 141.164.45.163
23 2026-08-24 09:44 639231611478799259
176 ms 141.164.45.163
22 2026-08-24 08:52 639231579923718211
11 ms 141.164.45.163
21 2026-08-24 08:35 639231569810702936
21 ms 141.164.45.163
20 2026-08-24 08:18 639231559762411619
31 ms 141.164.45.163
19 2026-08-24 08:01 639231549663595407
88 ms 141.164.45.163
18 2026-08-24 07:09 639231518076817246
112 ms 141.164.45.163
17 2026-08-24 06:52 639231508078650885
178 ms 141.164.45.163
16 2026-08-24 06:35 639231498210697093
2098 ms 141.164.45.163
15 2026-08-24 06:19 639231488109699360
2201 ms 141.164.45.163
14 2026-08-24 05:26 639231456772510692
114 ms 141.164.45.163
13 2026-08-24 05:10 639231447084631185
52 ms 141.164.45.163
12 2026-08-24 04:54 639231437208519473
41 ms 141.164.45.163
11 2026-08-24 04:37 639231427209627490
32 ms 141.164.45.163
10 2026-08-24 03:45 639231395791246644
68 ms 141.164.45.163
9 2026-08-24 03:29 639231386075551458
57 ms 141.164.45.163
8 2026-08-24 03:12 639231376208713791
25 ms 141.164.45.163
7 2026-08-24 02:55 639231366170589276
9 ms 141.164.45.163
6 2026-08-24 02:03 639231334732159368
59 ms 141.164.45.163
5 2026-08-24 01:47 639231325035670078
14 ms 141.164.45.163
4 2026-08-24 01:30 639231315132253837
6 ms 141.164.45.163
3 2026-08-24 01:14 639231305014280808
43 ms 141.164.45.163
2 2026-08-24 00:21 639231273779380675
71 ms 141.164.45.163
1 2026-08-24 00:05 639231264180839154
10 ms 141.164.45.163