DNS response history for ns2.rcmguadalupenuevo.org

ns2.rcmguadalupenuevo.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-27. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 324 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.rcmguadalupenuevo.org.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

324 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

152.160.203.60

Most recently resolved hosting IP on selected date

Successful Responses

31

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.rcmguadalupenuevo.org

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
31 2026-08-27 10:03 639234212558002823
255 ms 152.160.203.60
30 2026-08-27 09:45 639234202117531850
236 ms 152.160.203.60
29 2026-08-27 09:28 639234191649612722
115 ms 152.160.203.60
28 2026-08-27 09:10 639234181105879568
114 ms 152.160.203.60
27 2026-08-27 08:53 639234170713214496
114 ms 152.160.203.60
26 2026-08-27 08:36 639234160341037652
250 ms 152.160.203.60
25 2026-08-27 08:18 639234149799404224
235 ms 152.160.203.60
24 2026-08-27 08:01 639234139553286469
350 ms 152.160.203.60
23 2026-08-27 07:07 639234107183588293
597 ms 152.160.203.60
22 2026-08-27 06:50 639234096905435724
210 ms 152.160.203.60
21 2026-08-27 06:33 639234086579410775
351 ms 152.160.203.60
20 2026-08-27 06:16 639234076291157956
357 ms 152.160.203.60
19 2026-08-27 05:59 639234065981939454
582 ms 152.160.203.60
18 2026-08-27 05:41 639234055548642997
139 ms 152.160.203.60
17 2026-08-27 05:24 639234045267979603
120 ms 152.160.203.60
16 2026-08-27 05:07 639234034999717463
113 ms 152.160.203.60
15 2026-08-27 04:50 639234024739225358
117 ms 152.160.203.60
14 2026-08-27 04:33 639234014311170162
354 ms 152.160.203.60
13 2026-08-27 04:15 639234003806017640
618 ms 152.160.203.60
12 2026-08-27 03:58 639233993356203030
111 ms 152.160.203.60
11 2026-08-27 03:04 639233961301716608
112 ms 152.160.203.60
10 2026-08-27 02:47 639233950834200647
394 ms 152.160.203.60
9 2026-08-27 02:29 639233940431849026
482 ms 152.160.203.60
8 2026-08-27 02:12 639233930110596398
191 ms 152.160.203.60
7 2026-08-27 01:55 639233919705434540
115 ms 152.160.203.60
6 2026-08-27 01:38 639233909452807845
112 ms 152.160.203.60
5 2026-08-27 01:20 639233899096420820
472 ms 152.160.203.60
4 2026-08-27 01:03 639233888707824939
353 ms 152.160.203.60
3 2026-08-27 00:46 639233878461203802
2116 ms 152.160.203.60
2 2026-08-27 00:29 639233868060868209
116 ms 152.160.203.60
1 2026-08-27 00:11 639233857450922991
239 ms 152.160.203.60