DNS response history for ns3.belocity.com

ns3.belocity.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 29 DNS check records, 29 successful responses, 0 failed responses, and 96 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.belocity.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

96 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.117.40.198

Most recently resolved hosting IP on selected date

Successful Responses

29

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.belocity.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
29 2026-08-26 09:23 639233329214918079
23 ms 66.117.40.198
28 2026-08-26 09:06 639233318749762337
12 ms 66.117.40.198
27 2026-08-26 08:49 639233308387917838
32 ms 66.117.40.198
26 2026-08-26 08:31 639233297961740122
26 ms 66.117.40.198
25 2026-08-26 08:14 639233287487159094
63 ms 66.117.40.198
24 2026-08-26 07:56 639233276995531707
14 ms 66.117.40.198
23 2026-08-26 07:39 639233266521568229
9 ms 66.117.40.198
22 2026-08-26 07:21 639233256081047431
46 ms 66.117.40.198
21 2026-08-26 06:27 639233223620132921
35 ms 66.117.40.198
20 2026-08-26 06:10 639233213287814244
21 ms 66.117.40.198
19 2026-08-26 05:53 639233202925983161
44 ms 66.117.40.198
18 2026-08-26 05:36 639233192644780696
7 ms 66.117.40.198
17 2026-08-26 05:19 639233182401183833
23 ms 66.117.40.198
16 2026-08-26 05:01 639233172074181051
15 ms 66.117.40.198
15 2026-08-26 04:44 639233161808421455
18 ms 66.117.40.198
14 2026-08-26 04:27 639233151357344052
2037 ms 66.117.40.198
13 2026-08-26 04:10 639233141034116946
6 ms 66.117.40.198
12 2026-08-26 03:53 639233130828334142
5 ms 66.117.40.198
11 2026-08-26 03:35 639233120373450007
26 ms 66.117.40.198
10 2026-08-26 03:18 639233110066216193
53 ms 66.117.40.198
9 2026-08-26 02:25 639233078065410564
30 ms 66.117.40.198
8 2026-08-26 02:08 639233067787457832
32 ms 66.117.40.198
7 2026-08-26 01:50 639233057501801162
12 ms 66.117.40.198
6 2026-08-26 01:33 639233047089431703
37 ms 66.117.40.198
5 2026-08-26 01:16 639233036754790688
25 ms 66.117.40.198
4 2026-08-26 00:59 639233026412602472
10 ms 66.117.40.198
3 2026-08-26 00:41 639233016064066127
73 ms 66.117.40.198
2 2026-08-26 00:24 639233005922655772
41 ms 66.117.40.198
1 2026-08-26 00:07 639232995672256907
17 ms 66.117.40.198