DNS response history for raz2.redshift.com

raz2.redshift.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 34 DNS check records, 34 successful responses, 0 failed responses, and 511 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 raz2.redshift.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

511 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

76.72.156.59

Most recently resolved hosting IP on selected date

Successful Responses

34

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 raz2.redshift.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
34 2026-08-24 14:06 639231765923559455
162 ms 76.72.156.59
33 2026-08-24 13:50 639231755868832964
314 ms 76.72.156.59
32 2026-08-24 13:33 639231745628278877
171 ms 76.72.156.59
31 2026-08-24 13:15 639231735407682062
162 ms 76.72.156.59
30 2026-08-24 12:23 639231703815441688
317 ms 76.72.156.59
29 2026-08-24 12:06 639231693747052549
321 ms 76.72.156.59
28 2026-08-24 11:49 639231683712487276
161 ms 76.72.156.59
27 2026-08-24 11:32 639231673513573868
159 ms 76.72.156.59
26 2026-08-24 10:39 639231641791249939
319 ms 76.72.156.59
25 2026-08-24 10:23 639231631866211033
316 ms 76.72.156.59
24 2026-08-24 10:06 639231621644955316
179 ms 76.72.156.59
23 2026-08-24 09:49 639231611478799259
209 ms 76.72.156.59
22 2026-08-24 08:57 639231579923718211
320 ms 76.72.156.59
21 2026-08-24 08:40 639231569810702936
4161 ms 76.72.156.59
20 2026-08-24 08:23 639231559762411619
317 ms 76.72.156.59
19 2026-08-24 08:06 639231549663595407
160 ms 76.72.156.59
18 2026-08-24 07:13 639231518076817246
316 ms 76.72.156.59
17 2026-08-24 06:57 639231508078650885
161 ms 76.72.156.59
16 2026-08-24 06:40 639231498210697093
161 ms 76.72.156.59
15 2026-08-24 06:24 639231488109699360
2188 ms 76.72.156.59
14 2026-08-24 05:31 639231456772510692
166 ms 76.72.156.59
13 2026-08-24 05:15 639231447084631185
318 ms 76.72.156.59
12 2026-08-24 04:58 639231437208519473
2187 ms 76.72.156.59
11 2026-08-24 04:42 639231427209627490
162 ms 76.72.156.59
10 2026-08-24 03:49 639231395791246644
316 ms 76.72.156.59
9 2026-08-24 03:33 639231386075551458
318 ms 76.72.156.59
8 2026-08-24 03:17 639231376208713791
2 ms 76.72.156.59
7 2026-08-24 03:00 639231366170589276
159 ms 76.72.156.59
6 2026-08-24 02:08 639231334732159368
17 ms 76.72.156.59
5 2026-08-24 01:51 639231325035670078
176 ms 76.72.156.59
4 2026-08-24 01:35 639231315132253837
174 ms 76.72.156.59
3 2026-08-24 01:18 639231305014280808
317 ms 76.72.156.59
2 2026-08-24 00:26 639231273779380675
2169 ms 76.72.156.59
1 2026-08-24 00:10 639231264180839154
329 ms 76.72.156.59