DNS response history for varekay.reyma.mx

varekay.reyma.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-25. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 363 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 varekay.reyma.mx.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

363 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

201.151.158.101

Most recently resolved hosting IP on selected date

Successful Responses

32

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 varekay.reyma.mx

Showing DNS history for 2026-08-25 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
32 2026-08-25 11:23 639232535349285207
2147 ms 201.151.158.101
31 2026-08-25 11:06 639232524938080723
18 ms 201.151.158.101
30 2026-08-25 10:12 639232492740373468
36 ms 201.151.158.101
29 2026-08-25 09:55 639232482235303141
52 ms 201.151.158.101
28 2026-08-25 09:38 639232471861770303
52 ms 201.151.158.101
27 2026-08-25 09:21 639232461630217327
2371 ms 201.151.158.101
26 2026-08-25 09:03 639232451282965990
29 ms 201.151.158.101
25 2026-08-25 08:46 639232440814614938
181 ms 201.151.158.101
24 2026-08-25 08:28 639232430410720425
29 ms 201.151.158.101
23 2026-08-25 08:11 639232420003096185
18 ms 201.151.158.101
22 2026-08-25 07:54 639232409467287444
21 ms 201.151.158.101
21 2026-08-25 07:36 639232399077195997
2014 ms 201.151.158.101
20 2026-08-25 07:19 639232388731528337
18 ms 201.151.158.101
19 2026-08-25 07:02 639232378288598612
23 ms 201.151.158.101
18 2026-08-25 06:08 639232346196373643
372 ms 201.151.158.101
17 2026-08-25 05:51 639232336112370741
20 ms 201.151.158.101
16 2026-08-25 05:35 639232326146508970
42 ms 201.151.158.101
15 2026-08-25 05:18 639232316189381720
334 ms 201.151.158.101
14 2026-08-25 05:02 639232306217998913
360 ms 201.151.158.101
13 2026-08-25 04:45 639232296255744174
88 ms 201.151.158.101
12 2026-08-25 04:28 639232286095760789
291 ms 201.151.158.101
11 2026-08-25 04:11 639232276086186273
34 ms 201.151.158.101
10 2026-08-25 03:54 639232265900986425
20 ms 201.151.158.101
9 2026-08-25 03:37 639232255723518075
38 ms 201.151.158.101
8 2026-08-25 03:20 639232245484452890
292 ms 201.151.158.101
7 2026-08-25 03:03 639232235157175331
2391 ms 201.151.158.101
6 2026-08-25 02:10 639232203197189095
21 ms 201.151.158.101
5 2026-08-25 01:53 639232192844564298
20 ms 201.151.158.101
4 2026-08-25 01:35 639232182496008942
59 ms 201.151.158.101
3 2026-08-25 01:18 639232172197053132
45 ms 201.151.158.101
2 2026-08-25 00:25 639232140250307418
22 ms 201.151.158.101
1 2026-08-25 00:08 639232129927860324
151 ms 201.151.158.101