DNS response history for ns.efform.com.mx

ns.efform.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-27. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 459 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 ns.efform.com.mx.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

459 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

74.208.29.47

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 ns.efform.com.mx

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
32 2026-08-27 10:26 639234222943951923
656 ms 74.208.29.47
31 2026-08-27 10:09 639234212558002823
339 ms 74.208.29.47
30 2026-08-27 09:51 639234202117531850
149 ms 74.208.29.47
29 2026-08-27 09:34 639234191649612722
320 ms 74.208.29.47
28 2026-08-27 09:17 639234181105879568
657 ms 74.208.29.47
27 2026-08-27 08:59 639234170713214496
165 ms 74.208.29.47
26 2026-08-27 08:42 639234160341037652
328 ms 74.208.29.47
25 2026-08-27 08:24 639234149799404224
699 ms 74.208.29.47
24 2026-08-27 08:07 639234139553286469
637 ms 74.208.29.47
23 2026-08-27 07:13 639234107183588293
649 ms 74.208.29.47
22 2026-08-27 06:56 639234096905435724
5 ms 74.208.29.47
21 2026-08-27 06:39 639234086579410775
313 ms 74.208.29.47
20 2026-08-27 06:21 639234076291157956
663 ms 74.208.29.47
19 2026-08-27 06:04 639234065981939454
308 ms 74.208.29.47
18 2026-08-27 05:47 639234055548642997
383 ms 74.208.29.47
17 2026-08-27 05:30 639234045267979603
327 ms 74.208.29.47
16 2026-08-27 05:13 639234034999717463
641 ms 74.208.29.47
15 2026-08-27 04:56 639234024739225358
295 ms 74.208.29.47
14 2026-08-27 04:38 639234014311170162
1235 ms 74.208.29.47
13 2026-08-27 04:21 639234003806017640
639 ms 74.208.29.47
12 2026-08-27 04:03 639233993356203030
657 ms 74.208.29.47
11 2026-08-27 03:10 639233961301716608
634 ms 74.208.29.47
10 2026-08-27 02:53 639233950834200647
330 ms 74.208.29.47
9 2026-08-27 02:35 639233940431849026
161 ms 74.208.29.47
8 2026-08-27 02:18 639233930110596398
661 ms 74.208.29.47
7 2026-08-27 02:01 639233919705434540
330 ms 74.208.29.47
6 2026-08-27 01:44 639233909452807845
154 ms 74.208.29.47
5 2026-08-27 01:26 639233899096420820
450 ms 74.208.29.47
4 2026-08-27 01:09 639233888707824939
671 ms 74.208.29.47
3 2026-08-27 00:52 639233878461203802
258 ms 74.208.29.47
2 2026-08-27 00:35 639233868060868209
328 ms 74.208.29.47
1 2026-08-27 00:17 639233857450922991
641 ms 74.208.29.47