DNS response history for ns2.reduaz.mx

ns2.reduaz.mx 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 209 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.reduaz.mx.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

209 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

148.217.18.7

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.reduaz.mx

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:16 639234253963286387
340 ms 148.217.18.7
34 2026-08-27 10:59 639234243654907465
171 ms 148.217.18.7
33 2026-08-27 10:42 639234233269654413
188 ms 148.217.18.7
32 2026-08-27 10:25 639234222943951923
360 ms 148.217.18.7
31 2026-08-27 10:07 639234212558002823
188 ms 148.217.18.7
30 2026-08-27 09:50 639234202117531850
178 ms 148.217.18.7
29 2026-08-27 09:33 639234191649612722
351 ms 148.217.18.7
28 2026-08-27 09:15 639234181105879568
172 ms 148.217.18.7
27 2026-08-27 08:58 639234170713214496
184 ms 148.217.18.7
26 2026-08-27 08:40 639234160341037652
175 ms 148.217.18.7
25 2026-08-27 08:23 639234149799404224
178 ms 148.217.18.7
24 2026-08-27 08:05 639234139553286469
179 ms 148.217.18.7
23 2026-08-27 07:12 639234107183588293
351 ms 148.217.18.7
22 2026-08-27 06:54 639234096905435724
165 ms 148.217.18.7
21 2026-08-27 06:37 639234086579410775
172 ms 148.217.18.7
20 2026-08-27 06:20 639234076291157956
345 ms 148.217.18.7
19 2026-08-27 06:03 639234065981939454
167 ms 148.217.18.7
18 2026-08-27 05:46 639234055548642997
165 ms 148.217.18.7
17 2026-08-27 05:28 639234045267979603
169 ms 148.217.18.7
16 2026-08-27 05:11 639234034999717463
335 ms 148.217.18.7
15 2026-08-27 04:54 639234024739225358
175 ms 148.217.18.7
14 2026-08-27 04:37 639234014311170162
171 ms 148.217.18.7
13 2026-08-27 04:19 639234003806017640
171 ms 148.217.18.7
12 2026-08-27 04:02 639233993356203030
175 ms 148.217.18.7
11 2026-08-27 03:09 639233961301716608
192 ms 148.217.18.7
10 2026-08-27 02:51 639233950834200647
175 ms 148.217.18.7
9 2026-08-27 02:34 639233940431849026
173 ms 148.217.18.7
8 2026-08-27 02:17 639233930110596398
173 ms 148.217.18.7
7 2026-08-27 01:59 639233919705434540
171 ms 148.217.18.7
6 2026-08-27 01:42 639233909452807845
344 ms 148.217.18.7
5 2026-08-27 01:25 639233899096420820
183 ms 148.217.18.7
4 2026-08-27 01:08 639233888707824939
170 ms 148.217.18.7
3 2026-08-27 00:50 639233878461203802
172 ms 148.217.18.7
2 2026-08-27 00:33 639233868060868209
173 ms 148.217.18.7
1 2026-08-27 00:16 639233857450922991
165 ms 148.217.18.7