DNS response history for ns3.bdy-eo.com

ns3.bdy-eo.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 314 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 ns3.bdy-eo.com.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

314 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

183.232.232.21

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 ns3.bdy-eo.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:43 639233297961740122
230 ms 183.232.232.21
26 2026-08-26 08:25 639233287487159094
453 ms 183.232.232.21
25 2026-08-26 08:08 639233276995531707
216 ms 183.232.232.21
24 2026-08-26 07:50 639233266521568229
227 ms 183.232.232.21
23 2026-08-26 07:33 639233256081047431
525 ms 183.232.232.21
22 2026-08-26 06:39 639233223620132921
448 ms 183.232.232.21
21 2026-08-26 06:21 639233213287814244
447 ms 183.232.232.21
20 2026-08-26 06:04 639233202925983161
403 ms 183.232.232.21
19 2026-08-26 05:47 639233192644780696
226 ms 183.232.232.21
18 2026-08-26 05:30 639233182401183833
169 ms 183.232.232.21
17 2026-08-26 05:13 639233172074181051
236 ms 183.232.232.21
16 2026-08-26 04:56 639233161808421455
213 ms 183.232.232.21
15 2026-08-26 04:38 639233151357344052
194 ms 183.232.232.21
14 2026-08-26 04:21 639233141034116946
412 ms 183.232.232.21
13 2026-08-26 04:04 639233130828334142
219 ms 183.232.232.21
12 2026-08-26 03:47 639233120373450007
247 ms 183.232.232.21
11 2026-08-26 03:29 639233110066216193
215 ms 183.232.232.21
10 2026-08-26 02:36 639233078065410564
530 ms 183.232.232.21
9 2026-08-26 02:19 639233067787457832
264 ms 183.232.232.21
8 2026-08-26 02:02 639233057501801162
540 ms 183.232.232.21
7 2026-08-26 01:45 639233047089431703
214 ms 183.232.232.21
6 2026-08-26 01:27 639233036754790688
220 ms 183.232.232.21
5 2026-08-26 01:10 639233026412602472
223 ms 183.232.232.21
4 2026-08-26 00:53 639233016064066127
529 ms 183.232.232.21
3 2026-08-26 00:36 639233005922655772
265 ms 183.232.232.21
2 2026-08-26 00:19 639232995672256907
434 ms 183.232.232.21
1 2026-08-26 00:02 639232985300872416
170 ms 183.232.232.21