DNS response history for ns2.tiger-rescue.org

ns2.tiger-rescue.org 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 30 DNS check records, 30 successful responses, 0 failed responses, and 170 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.tiger-rescue.org.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

170 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.79.248.122

Most recently resolved hosting IP on selected date

Successful Responses

30

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.tiger-rescue.org

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
30 2026-08-24 12:24 639231703815441688
163 ms 51.79.248.122
29 2026-08-24 12:08 639231693747052549
342 ms 51.79.248.122
28 2026-08-24 11:51 639231683712487276
426 ms 51.79.248.122
27 2026-08-24 11:34 639231673513573868
438 ms 51.79.248.122
26 2026-08-24 10:41 639231641791249939
10 ms 51.79.248.122
25 2026-08-24 10:25 639231631866211033
4 ms 51.79.248.122
24 2026-08-24 10:08 639231621644955316
339 ms 51.79.248.122
23 2026-08-24 09:51 639231611478799259
265 ms 51.79.248.122
22 2026-08-24 08:58 639231579923718211
252 ms 51.79.248.122
21 2026-08-24 08:41 639231569810702936
348 ms 51.79.248.122
20 2026-08-24 08:24 639231559762411619
4 ms 51.79.248.122
19 2026-08-24 08:08 639231549663595407
4 ms 51.79.248.122
18 2026-08-24 07:15 639231518076817246
2 ms 51.79.248.122
17 2026-08-24 06:59 639231508078650885
166 ms 51.79.248.122
16 2026-08-24 06:42 639231498210697093
427 ms 51.79.248.122
15 2026-08-24 06:25 639231488109699360
3 ms 51.79.248.122
14 2026-08-24 05:33 639231456772510692
314 ms 51.79.248.122
13 2026-08-24 05:17 639231447084631185
3 ms 51.79.248.122
12 2026-08-24 05:00 639231437208519473
3 ms 51.79.248.122
11 2026-08-24 04:43 639231427209627490
2 ms 51.79.248.122
10 2026-08-24 03:51 639231395791246644
3 ms 51.79.248.122
9 2026-08-24 03:35 639231386075551458
163 ms 51.79.248.122
8 2026-08-24 03:19 639231376208713791
171 ms 51.79.248.122
7 2026-08-24 03:02 639231366170589276
347 ms 51.79.248.122
6 2026-08-24 02:09 639231334732159368
8 ms 51.79.248.122
5 2026-08-24 01:53 639231325035670078
422 ms 51.79.248.122
4 2026-08-24 01:37 639231315132253837
3 ms 51.79.248.122
3 2026-08-24 01:20 639231305014280808
2 ms 51.79.248.122
2 2026-08-24 00:28 639231273779380675
9 ms 51.79.248.122
1 2026-08-24 00:12 639231264180839154
454 ms 51.79.248.122