DNS response history for ns2.redwarning.com

ns2.redwarning.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-27. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 225 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.redwarning.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

225 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.72.176.4

Most recently resolved hosting IP on selected date

Successful Responses

35

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.redwarning.com

Showing DNS history for 2026-08-27 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
35 2026-08-27 11:10 639234253963286387
215 ms 208.72.176.4
34 2026-08-27 10:53 639234243654907465
207 ms 208.72.176.4
33 2026-08-27 10:36 639234233269654413
204 ms 208.72.176.4
32 2026-08-27 10:19 639234222943951923
206 ms 208.72.176.4
31 2026-08-27 10:01 639234212558002823
205 ms 208.72.176.4
30 2026-08-27 09:44 639234202117531850
210 ms 208.72.176.4
29 2026-08-27 09:27 639234191649612722
215 ms 208.72.176.4
28 2026-08-27 09:09 639234181105879568
155 ms 208.72.176.4
27 2026-08-27 08:52 639234170713214496
9 ms 208.72.176.4
26 2026-08-27 08:34 639234160341037652
211 ms 208.72.176.4
25 2026-08-27 08:17 639234149799404224
222 ms 208.72.176.4
24 2026-08-27 08:00 639234139553286469
102 ms 208.72.176.4
23 2026-08-27 07:06 639234107183588293
219 ms 208.72.176.4
22 2026-08-27 06:49 639234096905435724
112 ms 208.72.176.4
21 2026-08-27 06:32 639234086579410775
208 ms 208.72.176.4
20 2026-08-27 06:14 639234076291157956
112 ms 208.72.176.4
19 2026-08-27 05:57 639234065981939454
205 ms 208.72.176.4
18 2026-08-27 05:40 639234055548642997
110 ms 208.72.176.4
17 2026-08-27 05:23 639234045267979603
210 ms 208.72.176.4
16 2026-08-27 05:06 639234034999717463
137 ms 208.72.176.4
15 2026-08-27 04:48 639234024739225358
2104 ms 208.72.176.4
14 2026-08-27 04:31 639234014311170162
215 ms 208.72.176.4
13 2026-08-27 04:14 639234003806017640
205 ms 208.72.176.4
12 2026-08-27 03:56 639233993356203030
211 ms 208.72.176.4
11 2026-08-27 03:03 639233961301716608
213 ms 208.72.176.4
10 2026-08-27 02:46 639233950834200647
222 ms 208.72.176.4
9 2026-08-27 02:28 639233940431849026
127 ms 208.72.176.4
8 2026-08-27 02:11 639233930110596398
219 ms 208.72.176.4
7 2026-08-27 01:54 639233919705434540
10 ms 208.72.176.4
6 2026-08-27 01:36 639233909452807845
211 ms 208.72.176.4
5 2026-08-27 01:19 639233899096420820
8 ms 208.72.176.4
4 2026-08-27 01:02 639233888707824939
3 ms 208.72.176.4
3 2026-08-27 00:45 639233878461203802
225 ms 208.72.176.4
2 2026-08-27 00:27 639233868060868209
204 ms 208.72.176.4
1 2026-08-27 00:10 639233857450922991
215 ms 208.72.176.4