DNS response history for dns2.jdcs.jo

dns2.jdcs.jo 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 33 DNS check records, 33 successful responses, 0 failed responses, and 330 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 dns2.jdcs.jo.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

330 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

80.90.160.131

Most recently resolved hosting IP on selected date

Successful Responses

33

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 dns2.jdcs.jo

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
33 2026-08-26 10:34 639233370841350248
2039 ms 80.90.160.131
32 2026-08-26 10:17 639233360361507238
9 ms 80.90.160.131
31 2026-08-26 10:00 639233350067824371
55 ms 80.90.160.131
30 2026-08-26 09:42 639233339545274518
32 ms 80.90.160.131
29 2026-08-26 09:25 639233329214918079
2025 ms 80.90.160.131
28 2026-08-26 09:08 639233318749762337
11 ms 80.90.160.131
27 2026-08-26 08:50 639233308387917838
6 ms 80.90.160.131
26 2026-08-26 08:33 639233297961740122
36 ms 80.90.160.131
25 2026-08-26 08:15 639233287487159094
17 ms 80.90.160.131
24 2026-08-26 07:58 639233276995531707
15 ms 80.90.160.131
23 2026-08-26 07:40 639233266521568229
5 ms 80.90.160.131
22 2026-08-26 07:23 639233256081047431
8 ms 80.90.160.131
21 2026-08-26 06:29 639233223620132921
12 ms 80.90.160.131
20 2026-08-26 06:12 639233213287814244
2052 ms 80.90.160.131
19 2026-08-26 05:54 639233202925983161
9 ms 80.90.160.131
18 2026-08-26 05:37 639233192644780696
24 ms 80.90.160.131
17 2026-08-26 05:20 639233182401183833
6 ms 80.90.160.131
16 2026-08-26 05:03 639233172074181051
2019 ms 80.90.160.131
15 2026-08-26 04:46 639233161808421455
5 ms 80.90.160.131
14 2026-08-26 04:28 639233151357344052
5 ms 80.90.160.131
13 2026-08-26 04:11 639233141034116946
124 ms 80.90.160.131
12 2026-08-26 03:54 639233130828334142
38 ms 80.90.160.131
11 2026-08-26 03:37 639233120373450007
5 ms 80.90.160.131
10 2026-08-26 03:20 639233110066216193
73 ms 80.90.160.131
9 2026-08-26 02:26 639233078065410564
13 ms 80.90.160.131
8 2026-08-26 02:09 639233067787457832
2014 ms 80.90.160.131
7 2026-08-26 01:52 639233057501801162
22 ms 80.90.160.131
6 2026-08-26 01:35 639233047089431703
14 ms 80.90.160.131
5 2026-08-26 01:17 639233036754790688
28 ms 80.90.160.131
4 2026-08-26 01:00 639233026412602472
25 ms 80.90.160.131
3 2026-08-26 00:43 639233016064066127
9 ms 80.90.160.131
2 2026-08-26 00:26 639233005922655772
33 ms 80.90.160.131
1 2026-08-26 00:09 639232995672256907
96 ms 80.90.160.131