DNS response history for ns1.centralnoticiasmx.com

ns1.centralnoticiasmx.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-26. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 405 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 ns1.centralnoticiasmx.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

405 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.103.84

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns1.centralnoticiasmx.com

Showing DNS history for 2026-08-26 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
29 2026-08-26 09:16 639233318749762337
385 ms 162.240.103.84
28 2026-08-26 08:59 639233308387917838
418 ms 162.240.103.84
27 2026-08-26 08:41 639233297961740122
403 ms 162.240.103.84
26 2026-08-26 08:24 639233287487159094
374 ms 162.240.103.84
25 2026-08-26 08:07 639233276995531707
374 ms 162.240.103.84
24 2026-08-26 07:49 639233266521568229
355 ms 162.240.103.84
23 2026-08-26 07:31 639233256081047431
355 ms 162.240.103.84
22 2026-08-26 06:38 639233223620132921
350 ms 162.240.103.84
21 2026-08-26 06:20 639233213287814244
392 ms 162.240.103.84
20 2026-08-26 06:03 639233202925983161
348 ms 162.240.103.84
19 2026-08-26 05:46 639233192644780696
351 ms 162.240.103.84
18 2026-08-26 05:29 639233182401183833
347 ms 162.240.103.84
17 2026-08-26 05:12 639233172074181051
360 ms 162.240.103.84
16 2026-08-26 04:54 639233161808421455
349 ms 162.240.103.84
15 2026-08-26 04:37 639233151357344052
349 ms 162.240.103.84
14 2026-08-26 04:20 639233141034116946
176 ms 162.240.103.84
13 2026-08-26 04:03 639233130828334142
194 ms 162.240.103.84
12 2026-08-26 03:46 639233120373450007
180 ms 162.240.103.84
11 2026-08-26 03:28 639233110066216193
348 ms 162.240.103.84
10 2026-08-26 02:35 639233078065410564
349 ms 162.240.103.84
9 2026-08-26 02:18 639233067787457832
350 ms 162.240.103.84
8 2026-08-26 02:01 639233057501801162
2351 ms 162.240.103.84
7 2026-08-26 01:43 639233047089431703
347 ms 162.240.103.84
6 2026-08-26 01:26 639233036754790688
350 ms 162.240.103.84
5 2026-08-26 01:09 639233026412602472
345 ms 162.240.103.84
4 2026-08-26 00:52 639233016064066127
358 ms 162.240.103.84
3 2026-08-26 00:34 639233005922655772
346 ms 162.240.103.84
2 2026-08-26 00:17 639232995672256907
181 ms 162.240.103.84
1 2026-08-26 00:00 639232985300872416
346 ms 162.240.103.84