DNS response history for ns2.jacangel.com

ns2.jacangel.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, 35 successful responses, 1 failed responses, and 163 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.jacangel.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

163 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

141.95.143.42

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.jacangel.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 12:02 639233424567558554
40 ms 141.95.143.42
35 2026-08-26 11:45 639233414056832719
106 ms 141.95.143.42
34 2026-08-26 11:27 639233403515141099
49 ms 141.95.143.42
33 2026-08-26 10:33 639233370841350248
80 ms 141.95.143.42
32 2026-08-26 10:15 639233360361507238
53 ms 141.95.143.42
31 2026-08-26 09:58 639233350067824371
50 ms 141.95.143.42
30 2026-08-26 09:41 639233339545274518
99 ms 141.95.143.42
29 2026-08-26 09:24 639233329214918079
72 ms 141.95.143.42
28 2026-08-26 09:06 639233318749762337
39 ms 141.95.143.42
27 2026-08-26 08:49 639233308387917838
36 ms 141.95.143.42
26 2026-08-26 08:31 639233297961740122
34 ms 141.95.143.42
25 2026-08-26 08:14 639233287487159094
56 ms 141.95.143.42
24 2026-08-26 07:57 639233276995531707
41 ms 141.95.143.42
23 2026-08-26 07:39 639233266521568229
36 ms 141.95.143.42
22 2026-08-26 07:22 639233256081047431
87 ms 141.95.143.42
21 2026-08-26 06:28 639233223620132921
43 ms 141.95.143.42
20 2026-08-26 06:10 639233213287814244
44 ms 141.95.143.42
19 2026-08-26 05:53 639233202925983161
48 ms 141.95.143.42
18 2026-08-26 05:36 639233192644780696
40 ms 141.95.143.42
17 2026-08-26 05:19 639233182401183833
5 ms 141.95.143.42
16 2026-08-26 05:02 639233172074181051
49 ms 141.95.143.42
15 2026-08-26 04:45 639233161808421455
83 ms 141.95.143.42
14 2026-08-26 04:27 639233151357344052
33 ms 141.95.143.42
13 2026-08-26 04:10 639233141034116946
32 ms 141.95.143.42
12 2026-08-26 03:53 639233130828334142
2013 ms 141.95.143.42
11 2026-08-26 03:36 639233120373450007
-
10 2026-08-26 03:18 639233110066216193
2017 ms 141.95.143.42
9 2026-08-26 02:25 639233078065410564
46 ms 141.95.143.42
8 2026-08-26 02:08 639233067787457832
39 ms 141.95.143.42
7 2026-08-26 01:51 639233057501801162
50 ms 141.95.143.42
6 2026-08-26 01:33 639233047089431703
67 ms 141.95.143.42
5 2026-08-26 01:16 639233036754790688
34 ms 141.95.143.42
4 2026-08-26 00:59 639233026412602472
26 ms 141.95.143.42
3 2026-08-26 00:42 639233016064066127
45 ms 141.95.143.42
2 2026-08-26 00:25 639233005922655772
55 ms 141.95.143.42
1 2026-08-26 00:08 639232995672256907
41 ms 141.95.143.42