DNS response history for ns1.ajkerbanshkhali.com

ns1.ajkerbanshkhali.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 27 DNS check records, 27 successful responses, 0 failed responses, and 353 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 ns1.ajkerbanshkhali.com.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

353 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

207.180.229.201

Most recently resolved hosting IP on selected date

Successful Responses

27

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 ns1.ajkerbanshkhali.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
27 2026-08-26 08:51 639233308387917838
40 ms 207.180.229.201
26 2026-08-26 08:34 639233297961740122
69 ms 207.180.229.201
25 2026-08-26 08:17 639233287487159094
2054 ms 207.180.229.201
24 2026-08-26 07:59 639233276995531707
22 ms 207.180.229.201
23 2026-08-26 07:42 639233266521568229
203 ms 207.180.229.201
22 2026-08-26 07:24 639233256081047431
53 ms 207.180.229.201
21 2026-08-26 06:30 639233223620132921
174 ms 207.180.229.201
20 2026-08-26 06:13 639233213287814244
58 ms 207.180.229.201
19 2026-08-26 05:56 639233202925983161
31 ms 207.180.229.201
18 2026-08-26 05:38 639233192644780696
37 ms 207.180.229.201
17 2026-08-26 05:21 639233182401183833
38 ms 207.180.229.201
16 2026-08-26 05:04 639233172074181051
43 ms 207.180.229.201
15 2026-08-26 04:47 639233161808421455
47 ms 207.180.229.201
14 2026-08-26 04:30 639233151357344052
2020 ms 207.180.229.201
13 2026-08-26 04:12 639233141034116946
37 ms 207.180.229.201
12 2026-08-26 03:55 639233130828334142
7 ms 207.180.229.201
11 2026-08-26 03:38 639233120373450007
34 ms 207.180.229.201
10 2026-08-26 03:21 639233110066216193
76 ms 207.180.229.201
9 2026-08-26 02:27 639233078065410564
53 ms 207.180.229.201
8 2026-08-26 02:10 639233067787457832
55 ms 207.180.229.201
7 2026-08-26 01:53 639233057501801162
2023 ms 207.180.229.201
6 2026-08-26 01:36 639233047089431703
21 ms 207.180.229.201
5 2026-08-26 01:19 639233036754790688
35 ms 207.180.229.201
4 2026-08-26 01:01 639233026412602472
2071 ms 207.180.229.201
3 2026-08-26 00:44 639233016064066127
34 ms 207.180.229.201
2 2026-08-26 00:27 639233005922655772
48 ms 207.180.229.201
1 2026-08-26 00:10 639232995672256907
141 ms 207.180.229.201