DNS response history for ns1.bit-incorp.com

ns1.bit-incorp.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 34 DNS check records, 34 successful responses, 0 failed responses, and 302 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.bit-incorp.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

302 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:35

All timestamps shown in UTC

Latest Resolved IP on Selected Date

20.151.169.171

Most recently resolved hosting IP on selected date

Successful Responses

34

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.bit-incorp.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
34 2026-08-26 11:35 639233403515141099
223 ms 20.151.169.171
33 2026-08-26 10:40 639233370841350248
224 ms 20.151.169.171
32 2026-08-26 10:23 639233360361507238
226 ms 20.151.169.171
31 2026-08-26 10:05 639233350067824371
220 ms 20.151.169.171
30 2026-08-26 09:48 639233339545274518
219 ms 20.151.169.171
29 2026-08-26 09:31 639233329214918079
117 ms 20.151.169.171
28 2026-08-26 09:13 639233318749762337
113 ms 20.151.169.171
27 2026-08-26 08:56 639233308387917838
119 ms 20.151.169.171
26 2026-08-26 08:39 639233297961740122
221 ms 20.151.169.171
25 2026-08-26 08:21 639233287487159094
219 ms 20.151.169.171
24 2026-08-26 08:04 639233276995531707
220 ms 20.151.169.171
23 2026-08-26 07:46 639233266521568229
225 ms 20.151.169.171
22 2026-08-26 07:29 639233256081047431
218 ms 20.151.169.171
21 2026-08-26 06:35 639233223620132921
10 ms 20.151.169.171
20 2026-08-26 06:18 639233213287814244
219 ms 20.151.169.171
19 2026-08-26 06:00 639233202925983161
219 ms 20.151.169.171
18 2026-08-26 05:43 639233192644780696
229 ms 20.151.169.171
17 2026-08-26 05:26 639233182401183833
217 ms 20.151.169.171
16 2026-08-26 05:09 639233172074181051
131 ms 20.151.169.171
15 2026-08-26 04:52 639233161808421455
220 ms 20.151.169.171
14 2026-08-26 04:34 639233151357344052
115 ms 20.151.169.171
13 2026-08-26 04:17 639233141034116946
217 ms 20.151.169.171
12 2026-08-26 04:00 639233130828334142
221 ms 20.151.169.171
11 2026-08-26 03:43 639233120373450007
220 ms 20.151.169.171
10 2026-08-26 03:25 639233110066216193
4181 ms 20.151.169.171
9 2026-08-26 02:32 639233078065410564
124 ms 20.151.169.171
8 2026-08-26 02:15 639233067787457832
111 ms 20.151.169.171
7 2026-08-26 01:58 639233057501801162
225 ms 20.151.169.171
6 2026-08-26 01:41 639233047089431703
124 ms 20.151.169.171
5 2026-08-26 01:23 639233036754790688
219 ms 20.151.169.171
4 2026-08-26 01:06 639233026412602472
120 ms 20.151.169.171
3 2026-08-26 00:49 639233016064066127
225 ms 20.151.169.171
2 2026-08-26 00:32 639233005922655772
140 ms 20.151.169.171
1 2026-08-26 00:15 639232995672256907
221 ms 20.151.169.171