DNS response history for ns3.jrs-s.net

ns3.jrs-s.net 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 32 DNS check records, 32 successful responses, 0 failed responses, and 280 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.jrs-s.net.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

280 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

159.203.204.139

Most recently resolved hosting IP on selected date

Successful Responses

32

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.jrs-s.net

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
32 2026-08-24 13:33 639231745628278877
210 ms 159.203.204.139
31 2026-08-24 13:16 639231735407682062
214 ms 159.203.204.139
30 2026-08-24 12:23 639231703815441688
202 ms 159.203.204.139
29 2026-08-24 12:06 639231693747052549
102 ms 159.203.204.139
28 2026-08-24 11:50 639231683712487276
107 ms 159.203.204.139
27 2026-08-24 11:33 639231673513573868
103 ms 159.203.204.139
26 2026-08-24 10:40 639231641791249939
202 ms 159.203.204.139
25 2026-08-24 10:23 639231631866211033
202 ms 159.203.204.139
24 2026-08-24 10:06 639231621644955316
176 ms 159.203.204.139
23 2026-08-24 09:49 639231611478799259
206 ms 159.203.204.139
22 2026-08-24 08:57 639231579923718211
220 ms 159.203.204.139
21 2026-08-24 08:40 639231569810702936
203 ms 159.203.204.139
20 2026-08-24 08:23 639231559762411619
161 ms 159.203.204.139
19 2026-08-24 08:06 639231549663595407
163 ms 159.203.204.139
18 2026-08-24 07:14 639231518076817246
103 ms 159.203.204.139
17 2026-08-24 06:57 639231508078650885
103 ms 159.203.204.139
16 2026-08-24 06:40 639231498210697093
205 ms 159.203.204.139
15 2026-08-24 06:24 639231488109699360
102 ms 159.203.204.139
14 2026-08-24 05:32 639231456772510692
102 ms 159.203.204.139
13 2026-08-24 05:15 639231447084631185
177 ms 159.203.204.139
12 2026-08-24 04:59 639231437208519473
2173 ms 159.203.204.139
11 2026-08-24 04:42 639231427209627490
104 ms 159.203.204.139
10 2026-08-24 03:50 639231395791246644
254 ms 159.203.204.139
9 2026-08-24 03:34 639231386075551458
103 ms 159.203.204.139
8 2026-08-24 03:17 639231376208713791
99 ms 159.203.204.139
7 2026-08-24 03:01 639231366170589276
2183 ms 159.203.204.139
6 2026-08-24 02:08 639231334732159368
119 ms 159.203.204.139
5 2026-08-24 01:52 639231325035670078
100 ms 159.203.204.139
4 2026-08-24 01:35 639231315132253837
202 ms 159.203.204.139
3 2026-08-24 01:19 639231305014280808
110 ms 159.203.204.139
2 2026-08-24 00:26 639231273779380675
159 ms 159.203.204.139
1 2026-08-24 00:11 639231264180839154
103 ms 159.203.204.139