DNS response history for ns3.e-2j.com

ns3.e-2j.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 36 DNS check records, 36 successful responses, 0 failed responses, and 898 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 ns3.e-2j.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

898 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

118.151.163.36

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 ns3.e-2j.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
36 2026-08-26 11:59 639233414056832719
1304 ms 118.151.163.36
35 2026-08-26 11:41 639233403515141099
1186 ms 118.151.163.36
34 2026-08-26 10:46 639233370841350248
1128 ms 118.151.163.36
33 2026-08-26 10:29 639233360361507238
1076 ms 118.151.163.36
32 2026-08-26 10:12 639233350067824371
1486 ms 118.151.163.36
31 2026-08-26 09:54 639233339545274518
1086 ms 118.151.163.36
30 2026-08-26 09:37 639233329214918079
515 ms 118.151.163.36
29 2026-08-26 09:20 639233318749762337
1079 ms 118.151.163.36
28 2026-08-26 09:02 639233308387917838
1101 ms 118.151.163.36
27 2026-08-26 08:45 639233297961740122
1082 ms 118.151.163.36
26 2026-08-26 08:27 639233287487159094
1133 ms 118.151.163.36
25 2026-08-26 08:10 639233276995531707
1077 ms 118.151.163.36
24 2026-08-26 07:53 639233266521568229
1103 ms 118.151.163.36
23 2026-08-26 07:35 639233256081047431
650 ms 118.151.163.36
22 2026-08-26 06:41 639233223620132921
1080 ms 118.151.163.36
21 2026-08-26 06:24 639233213287814244
493 ms 118.151.163.36
20 2026-08-26 06:06 639233202925983161
491 ms 118.151.163.36
19 2026-08-26 05:49 639233192644780696
1074 ms 118.151.163.36
18 2026-08-26 05:32 639233182401183833
498 ms 118.151.163.36
17 2026-08-26 05:15 639233172074181051
1072 ms 118.151.163.36
16 2026-08-26 04:58 639233161808421455
1079 ms 118.151.163.36
15 2026-08-26 04:41 639233151357344052
1082 ms 118.151.163.36
14 2026-08-26 04:23 639233141034116946
1127 ms 118.151.163.36
13 2026-08-26 04:06 639233130828334142
495 ms 118.151.163.36
12 2026-08-26 03:49 639233120373450007
497 ms 118.151.163.36
11 2026-08-26 03:32 639233110066216193
493 ms 118.151.163.36
10 2026-08-26 02:38 639233078065410564
1075 ms 118.151.163.36
9 2026-08-26 02:21 639233067787457832
1073 ms 118.151.163.36
8 2026-08-26 02:04 639233057501801162
1074 ms 118.151.163.36
7 2026-08-26 01:47 639233047089431703
493 ms 118.151.163.36
6 2026-08-26 01:29 639233036754790688
497 ms 118.151.163.36
5 2026-08-26 01:12 639233026412602472
1073 ms 118.151.163.36
4 2026-08-26 00:55 639233016064066127
494 ms 118.151.163.36
3 2026-08-26 00:38 639233005922655772
490 ms 118.151.163.36
2 2026-08-26 00:21 639232995672256907
504 ms 118.151.163.36
1 2026-08-26 00:04 639232985300872416
1078 ms 118.151.163.36