DNS response history for ns1.4ward.com.mx

ns1.4ward.com.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-26. For this date, NameServerHistory found 27 DNS check records, 23 successful responses, 4 failed responses, and 639 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.4ward.com.mx.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

639 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

94.140.14.33

Most recently resolved hosting IP on selected date

Successful Responses

23

Checks that returned a measurable response

Failed Responses

4

Checks with no response or no returned latency

Failure Rate

15%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.4ward.com.mx

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
27 2026-08-26 08:44 639233297961740122
2641 ms 94.140.14.33
26 2026-08-26 08:26 639233287487159094
243 ms 94.140.14.33
25 2026-08-26 08:09 639233276995531707
370 ms 94.140.14.33
24 2026-08-26 07:51 639233266521568229
181 ms 94.140.14.33
23 2026-08-26 07:34 639233256081047431
391 ms 94.140.14.33
22 2026-08-26 06:40 639233223620132921
362 ms 94.140.14.33
21 2026-08-26 06:23 639233213287814244
2392 ms 94.140.14.33
20 2026-08-26 06:05 639233202925983161
176 ms 94.140.14.33
19 2026-08-26 05:48 639233192644780696
349 ms 94.140.14.33
18 2026-08-26 05:31 639233182401183833
204 ms 94.140.14.33
17 2026-08-26 05:14 639233172074181051
333 ms 94.140.14.33
16 2026-08-26 04:57 639233161808421455
487 ms 94.140.14.33
15 2026-08-26 04:40 639233151357344052
-
14 2026-08-26 04:22 639233141034116946
333 ms 94.140.14.33
13 2026-08-26 04:05 639233130828334142
-
12 2026-08-26 03:48 639233120373450007
-
11 2026-08-26 03:30 639233110066216193
359 ms 94.140.14.33
10 2026-08-26 02:37 639233078065410564
376 ms 94.140.14.33
9 2026-08-26 02:20 639233067787457832
-
8 2026-08-26 02:03 639233057501801162
356 ms 94.140.14.33
7 2026-08-26 01:46 639233047089431703
483 ms 94.140.14.33
6 2026-08-26 01:28 639233036754790688
359 ms 94.140.14.33
5 2026-08-26 01:11 639233026412602472
2343 ms 94.140.14.33
4 2026-08-26 00:54 639233016064066127
496 ms 94.140.14.33
3 2026-08-26 00:37 639233005922655772
345 ms 94.140.14.33
2 2026-08-26 00:20 639232995672256907
472 ms 94.140.14.33
1 2026-08-26 00:03 639232985300872416
635 ms 94.140.14.33