DNS response history for ns1.bid366.com

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

33

Historical checks stored for this nameserver on selected date

Average Latency

229 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

89.116.21.225

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 ns1.bid366.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
33 2026-08-26 10:42 639233370841350248
278 ms 89.116.21.225
32 2026-08-26 10:25 639233360361507238
257 ms 89.116.21.225
31 2026-08-26 10:07 639233350067824371
257 ms 89.116.21.225
30 2026-08-26 09:50 639233339545274518
398 ms 89.116.21.225
29 2026-08-26 09:32 639233329214918079
261 ms 89.116.21.225
28 2026-08-26 09:15 639233318749762337
159 ms 89.116.21.225
27 2026-08-26 08:58 639233308387917838
254 ms 89.116.21.225
26 2026-08-26 08:41 639233297961740122
277 ms 89.116.21.225
25 2026-08-26 08:23 639233287487159094
158 ms 89.116.21.225
24 2026-08-26 08:06 639233276995531707
267 ms 89.116.21.225
23 2026-08-26 07:48 639233266521568229
258 ms 89.116.21.225
22 2026-08-26 07:31 639233256081047431
254 ms 89.116.21.225
21 2026-08-26 06:37 639233223620132921
138 ms 89.116.21.225
20 2026-08-26 06:19 639233213287814244
254 ms 89.116.21.225
19 2026-08-26 06:02 639233202925983161
255 ms 89.116.21.225
18 2026-08-26 05:45 639233192644780696
160 ms 89.116.21.225
17 2026-08-26 05:28 639233182401183833
250 ms 89.116.21.225
16 2026-08-26 05:11 639233172074181051
269 ms 89.116.21.225
15 2026-08-26 04:54 639233161808421455
278 ms 89.116.21.225
14 2026-08-26 04:36 639233151357344052
268 ms 89.116.21.225
13 2026-08-26 04:19 639233141034116946
247 ms 89.116.21.225
12 2026-08-26 04:02 639233130828334142
159 ms 89.116.21.225
11 2026-08-26 03:45 639233120373450007
274 ms 89.116.21.225
10 2026-08-26 03:27 639233110066216193
176 ms 89.116.21.225
9 2026-08-26 02:34 639233078065410564
248 ms 89.116.21.225
8 2026-08-26 02:17 639233067787457832
249 ms 89.116.21.225
7 2026-08-26 02:00 639233057501801162
271 ms 89.116.21.225
6 2026-08-26 01:43 639233047089431703
13 ms 89.116.21.225
5 2026-08-26 01:25 639233036754790688
151 ms 89.116.21.225
4 2026-08-26 01:08 639233026412602472
267 ms 89.116.21.225
3 2026-08-26 00:51 639233016064066127
266 ms 89.116.21.225
2 2026-08-26 00:34 639233005922655772
16 ms 89.116.21.225
1 2026-08-26 00:17 639232995672256907
261 ms 89.116.21.225