DNS response history for ns02.railstream.tv

ns02.railstream.tv 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 36 DNS check records, 36 successful responses, 0 failed responses, and 501 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 ns02.railstream.tv.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

501 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

12.34.199.132

Most recently resolved hosting IP on selected date

Successful Responses

36

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 ns02.railstream.tv

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
36 2026-08-24 15:16 639231807961539652
919 ms 12.34.199.132
35 2026-08-24 14:59 639231797631669865
1733 ms 12.34.199.132
34 2026-08-24 14:06 639231765923559455
245 ms 12.34.199.132
33 2026-08-24 13:50 639231755868832964
131 ms 12.34.199.132
32 2026-08-24 13:33 639231745628278877
587 ms 12.34.199.132
31 2026-08-24 13:15 639231735407682062
223 ms 12.34.199.132
30 2026-08-24 12:23 639231703815441688
260 ms 12.34.199.132
29 2026-08-24 12:06 639231693747052549
124 ms 12.34.199.132
28 2026-08-24 11:49 639231683712487276
127 ms 12.34.199.132
27 2026-08-24 11:32 639231673513573868
3 ms 12.34.199.132
26 2026-08-24 10:39 639231641791249939
2129 ms 12.34.199.132
25 2026-08-24 10:23 639231631866211033
1741 ms 12.34.199.132
24 2026-08-24 10:06 639231621644955316
258 ms 12.34.199.132
23 2026-08-24 09:49 639231611478799259
126 ms 12.34.199.132
22 2026-08-24 08:56 639231579923718211
4 ms 12.34.199.132
21 2026-08-24 08:40 639231569810702936
5 ms 12.34.199.132
20 2026-08-24 08:23 639231559762411619
248 ms 12.34.199.132
19 2026-08-24 08:06 639231549663595407
578 ms 12.34.199.132
18 2026-08-24 07:13 639231518076817246
3 ms 12.34.199.132
17 2026-08-24 06:57 639231508078650885
3 ms 12.34.199.132
16 2026-08-24 06:40 639231498210697093
920 ms 12.34.199.132
15 2026-08-24 06:24 639231488109699360
930 ms 12.34.199.132
14 2026-08-24 05:31 639231456772510692
1753 ms 12.34.199.132
13 2026-08-24 05:15 639231447084631185
118 ms 12.34.199.132
12 2026-08-24 04:58 639231437208519473
244 ms 12.34.199.132
11 2026-08-24 04:42 639231427209627490
250 ms 12.34.199.132
10 2026-08-24 03:49 639231395791246644
4 ms 12.34.199.132
9 2026-08-24 03:33 639231386075551458
226 ms 12.34.199.132
8 2026-08-24 03:17 639231376208713791
236 ms 12.34.199.132
7 2026-08-24 03:00 639231366170589276
122 ms 12.34.199.132
6 2026-08-24 02:08 639231334732159368
1744 ms 12.34.199.132
5 2026-08-24 01:51 639231325035670078
121 ms 12.34.199.132
4 2026-08-24 01:35 639231315132253837
225 ms 12.34.199.132
3 2026-08-24 01:18 639231305014280808
2 ms 12.34.199.132
2 2026-08-24 00:26 639231273779380675
116 ms 12.34.199.132
1 2026-08-24 00:10 639231264180839154
1573 ms 12.34.199.132