DNS response history for ns2.christuccbaltimore.org

ns2.christuccbaltimore.org 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 30 DNS check records, 30 successful responses, 0 failed responses, and 525 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.christuccbaltimore.org.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

525 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

152.160.251.150

Most recently resolved hosting IP on selected date

Successful Responses

30

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.christuccbaltimore.org

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
30 2026-08-26 09:46 639233339545274518
115 ms 152.160.251.150
29 2026-08-26 09:29 639233329214918079
265 ms 152.160.251.150
28 2026-08-26 09:12 639233318749762337
221 ms 152.160.251.150
27 2026-08-26 08:54 639233308387917838
115 ms 152.160.251.150
26 2026-08-26 08:37 639233297961740122
2406 ms 152.160.251.150
25 2026-08-26 08:20 639233287487159094
114 ms 152.160.251.150
24 2026-08-26 08:02 639233276995531707
190 ms 152.160.251.150
23 2026-08-26 07:44 639233266521568229
248 ms 152.160.251.150
22 2026-08-26 07:27 639233256081047431
123 ms 152.160.251.150
21 2026-08-26 06:33 639233223620132921
115 ms 152.160.251.150
20 2026-08-26 06:16 639233213287814244
9 ms 152.160.251.150
19 2026-08-26 05:58 639233202925983161
19 ms 152.160.251.150
18 2026-08-26 05:41 639233192644780696
509 ms 152.160.251.150
17 2026-08-26 05:24 639233182401183833
487 ms 152.160.251.150
16 2026-08-26 05:07 639233172074181051
141 ms 152.160.251.150
15 2026-08-26 04:50 639233161808421455
2130 ms 152.160.251.150
14 2026-08-26 04:33 639233151357344052
473 ms 152.160.251.150
13 2026-08-26 04:15 639233141034116946
10 ms 152.160.251.150
12 2026-08-26 03:58 639233130828334142
460 ms 152.160.251.150
11 2026-08-26 03:41 639233120373450007
262 ms 152.160.251.150
10 2026-08-26 03:24 639233110066216193
2008 ms 152.160.251.150
9 2026-08-26 02:30 639233078065410564
128 ms 152.160.251.150
8 2026-08-26 02:13 639233067787457832
228 ms 152.160.251.150
7 2026-08-26 01:56 639233057501801162
24 ms 152.160.251.150
6 2026-08-26 01:39 639233047089431703
17 ms 152.160.251.150
5 2026-08-26 01:22 639233036754790688
2250 ms 152.160.251.150
4 2026-08-26 01:04 639233026412602472
238 ms 152.160.251.150
3 2026-08-26 00:47 639233016064066127
190 ms 152.160.251.150
2 2026-08-26 00:30 639233005922655772
144 ms 152.160.251.150
1 2026-08-26 00:13 639232995672256907
2114 ms 152.160.251.150