Records on Selected Date

53

Historical checks stored for this nameserver on selected date

Average Latency

354 ms

Calculated from available response records

Latest Check on Selected Date

2026-05-22 23:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

96.8.119.222

Most recently resolved hosting IP on selected date

Successful Responses

53

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.capital-chronicle.com

Showing DNS history for 2026-05-22 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
53 2026-05-22 23:06 639150872487681036
230 ms 96.8.119.222
52 2026-05-22 22:50 639150863263688363
4 ms 96.8.119.222
51 2026-05-22 22:35 639150853938419890
2116 ms 96.8.119.222
50 2026-05-22 22:19 639150844663560087
221 ms 96.8.119.222
49 2026-05-22 22:03 639150834978459775
228 ms 96.8.119.222
48 2026-05-22 21:47 639150824668816853
2115 ms 96.8.119.222
47 2026-05-22 20:30 639150779378992045
224 ms 96.8.119.222
46 2026-05-22 20:15 639150769706500947
4 ms 96.8.119.222
45 2026-05-22 19:58 639150760145923579
3 ms 96.8.119.222
44 2026-05-22 19:43 639150750960685442
223 ms 96.8.119.222
43 2026-05-22 19:27 639150741045426389
3 ms 96.8.119.222
42 2026-05-22 19:10 639150729730465132
225 ms 96.8.119.222
41 2026-05-22 17:52 639150683963074350
110 ms 96.8.119.222
40 2026-05-22 17:36 639150674165716797
2 ms 96.8.119.222
39 2026-05-22 17:20 639150664700608548
222 ms 96.8.119.222
38 2026-05-22 17:04 639150655174932769
2 ms 96.8.119.222
37 2026-05-22 16:48 639150645126847399
221 ms 96.8.119.222
36 2026-05-22 16:31 639150634894823967
225 ms 96.8.119.222
35 2026-05-22 15:14 639150589091003176
233 ms 96.8.119.222
34 2026-05-22 14:58 639150579470870680
237 ms 96.8.119.222
33 2026-05-22 14:42 639150569525766007
237 ms 96.8.119.222
32 2026-05-22 14:25 639150559403177136
121 ms 96.8.119.222
31 2026-05-22 14:07 639150548871742300
231 ms 96.8.119.222
30 2026-05-22 13:50 639150538076800591
2118 ms 96.8.119.222
29 2026-05-22 12:31 639150491759654836
2 ms 96.8.119.222
28 2026-05-22 12:15 639150482438354436
229 ms 96.8.119.222
27 2026-05-22 12:00 639150473207157122
118 ms 96.8.119.222
26 2026-05-22 11:44 639150463398480648
2119 ms 96.8.119.222
25 2026-05-22 11:28 639150453578114902
231 ms 96.8.119.222
24 2026-05-22 11:11 639150443412733010
249 ms 96.8.119.222
23 2026-05-22 09:54 639150397310134726
233 ms 96.8.119.222
22 2026-05-22 09:38 639150387696185045
242 ms 96.8.119.222
21 2026-05-22 09:22 639150377916309374
118 ms 96.8.119.222
20 2026-05-22 09:05 639150367939992669
234 ms 96.8.119.222
19 2026-05-22 08:48 639150357684444742
234 ms 96.8.119.222
18 2026-05-22 08:31 639150347197669662
2123 ms 96.8.119.222
17 2026-05-22 07:11 639150299340567733
233 ms 96.8.119.222
16 2026-05-22 06:53 639150288830585567
233 ms 96.8.119.222
15 2026-05-22 06:36 639150278354500946
235 ms 96.8.119.222
14 2026-05-22 06:18 639150268017999571
233 ms 96.8.119.222
13 2026-05-22 06:01 639150257011624460
117 ms 96.8.119.222
12 2026-05-22 05:43 639150245778157881
239 ms 96.8.119.222
11 2026-05-22 04:23 639150198183302617
236 ms 96.8.119.222
10 2026-05-22 04:05 639150187606955695
2 ms 96.8.119.222
9 2026-05-22 03:47 639150176868272366
234 ms 96.8.119.222
8 2026-05-22 03:28 639150165425087742
232 ms 96.8.119.222
7 2026-05-22 03:11 639150153935936530
119 ms 96.8.119.222
6 2026-05-22 02:52 639150142528129935
237 ms 96.8.119.222
5 2026-05-22 01:31 639150094397030210
234 ms 96.8.119.222
4 2026-05-22 01:13 639150083115025582
229 ms 96.8.119.222
3 2026-05-22 00:54 639150071726870327
14 ms 96.8.119.222
2 2026-05-22 00:35 639150060452341025
3 ms 96.8.119.222
1 2026-05-22 00:16 639150049171398520
238 ms 96.8.119.222