DNS response history for ns2.efreightmax.com

ns2.efreightmax.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-28. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 224 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.efreightmax.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

224 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 15:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

184.107.146.20

Most recently resolved hosting IP on selected date

Successful Responses

36

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.efreightmax.com

Showing DNS history for 2026-08-28 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
36 2026-08-28 15:07 639235258803654519
228 ms 184.107.146.20
35 2026-08-28 14:49 639235248596087996
240 ms 184.107.146.20
34 2026-08-28 14:32 639235238225955920
232 ms 184.107.146.20
33 2026-08-28 14:15 639235227727862105
235 ms 184.107.146.20
32 2026-08-28 13:20 639235195230848570
228 ms 184.107.146.20
31 2026-08-28 13:03 639235184840503274
246 ms 184.107.146.20
30 2026-08-28 12:46 639235174453894956
8 ms 184.107.146.20
29 2026-08-28 12:28 639235163898672622
114 ms 184.107.146.20
28 2026-08-28 11:35 639235132147470568
218 ms 184.107.146.20
27 2026-08-28 11:18 639235121907744088
216 ms 184.107.146.20
26 2026-08-28 11:01 639235111428014262
224 ms 184.107.146.20
25 2026-08-28 10:43 639235100921813626
114 ms 184.107.146.20
24 2026-08-28 09:49 639235068670703481
215 ms 184.107.146.20
23 2026-08-28 09:32 639235058337459445
219 ms 184.107.146.20
22 2026-08-28 09:15 639235047825109146
223 ms 184.107.146.20
21 2026-08-28 08:57 639235037383229033
227 ms 184.107.146.20
20 2026-08-28 08:04 639235005619242711
9 ms 184.107.146.20
19 2026-08-28 07:47 639234995310346584
219 ms 184.107.146.20
18 2026-08-28 07:30 639234984946548933
217 ms 184.107.146.20
17 2026-08-28 07:13 639234974608077290
210 ms 184.107.146.20
16 2026-08-28 06:19 639234942529845595
212 ms 184.107.146.20
15 2026-08-28 06:02 639234932259126627
102 ms 184.107.146.20
14 2026-08-28 05:45 639234921916735988
126 ms 184.107.146.20
13 2026-08-28 05:28 639234911470038027
3 ms 184.107.146.20
12 2026-08-28 04:34 639234879588411654
4 ms 184.107.146.20
11 2026-08-28 04:17 639234869341589104
217 ms 184.107.146.20
10 2026-08-28 04:00 639234859012216675
218 ms 184.107.146.20
9 2026-08-28 03:43 639234848695364934
2002 ms 184.107.146.20
8 2026-08-28 02:50 639234816952458162
2 ms 184.107.146.20
7 2026-08-28 02:33 639234806773081598
217 ms 184.107.146.20
6 2026-08-28 02:16 639234796382955255
210 ms 184.107.146.20
5 2026-08-28 01:58 639234786015782563
226 ms 184.107.146.20
4 2026-08-28 01:05 639234753811917646
220 ms 184.107.146.20
3 2026-08-28 00:48 639234743739767811
226 ms 184.107.146.20
2 2026-08-28 00:31 639234733372362811
31 ms 184.107.146.20
1 2026-08-28 00:13 639234723048550337
211 ms 184.107.146.20