DNS response history for ns2.hdpublicidad.mx

ns2.hdpublicidad.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-24. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 313 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.hdpublicidad.mx.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

313 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

129.121.60.121

Most recently resolved hosting IP on selected date

Successful Responses

38

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

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
38 2026-08-24 15:51 639231828211839931
4 ms 129.121.60.121
37 2026-08-24 15:34 639231818080917481
4 ms 129.121.60.121
36 2026-08-24 15:17 639231807961539652
2007 ms 129.121.60.121
35 2026-08-24 15:00 639231797631669865
12 ms 129.121.60.121
34 2026-08-24 14:07 639231765923559455
5 ms 129.121.60.121
33 2026-08-24 13:50 639231755868832964
479 ms 129.121.60.121
32 2026-08-24 13:33 639231745628278877
313 ms 129.121.60.121
31 2026-08-24 13:16 639231735407682062
152 ms 129.121.60.121
30 2026-08-24 12:23 639231703815441688
5 ms 129.121.60.121
29 2026-08-24 12:07 639231693747052549
6 ms 129.121.60.121
28 2026-08-24 11:50 639231683712487276
5 ms 129.121.60.121
27 2026-08-24 11:33 639231673513573868
3 ms 129.121.60.121
26 2026-08-24 10:40 639231641791249939
492 ms 129.121.60.121
25 2026-08-24 10:23 639231631866211033
156 ms 129.121.60.121
24 2026-08-24 10:07 639231621644955316
308 ms 129.121.60.121
23 2026-08-24 09:50 639231611478799259
315 ms 129.121.60.121
22 2026-08-24 08:57 639231579923718211
1963 ms 129.121.60.121
21 2026-08-24 08:40 639231569810702936
156 ms 129.121.60.121
20 2026-08-24 08:23 639231559762411619
4 ms 129.121.60.121
19 2026-08-24 08:06 639231549663595407
306 ms 129.121.60.121
18 2026-08-24 07:14 639231518076817246
2162 ms 129.121.60.121
17 2026-08-24 06:57 639231508078650885
353 ms 129.121.60.121
16 2026-08-24 06:41 639231498210697093
3 ms 129.121.60.121
15 2026-08-24 06:24 639231488109699360
302 ms 129.121.60.121
14 2026-08-24 05:32 639231456772510692
7 ms 129.121.60.121
13 2026-08-24 05:15 639231447084631185
24 ms 129.121.60.121
12 2026-08-24 04:59 639231437208519473
193 ms 129.121.60.121
11 2026-08-24 04:42 639231427209627490
311 ms 129.121.60.121
10 2026-08-24 03:50 639231395791246644
8 ms 129.121.60.121
9 2026-08-24 03:34 639231386075551458
3 ms 129.121.60.121
8 2026-08-24 03:17 639231376208713791
324 ms 129.121.60.121
7 2026-08-24 03:01 639231366170589276
304 ms 129.121.60.121
6 2026-08-24 02:08 639231334732159368
192 ms 129.121.60.121
5 2026-08-24 01:52 639231325035670078
4 ms 129.121.60.121
4 2026-08-24 01:36 639231315132253837
3 ms 129.121.60.121
3 2026-08-24 01:19 639231305014280808
158 ms 129.121.60.121
2 2026-08-24 00:26 639231273779380675
537 ms 129.121.60.121
1 2026-08-24 00:11 639231264180839154
305 ms 129.121.60.121