DNS response history for b.ns.3dresearch.com

b.ns.3dresearch.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 35 DNS check records, 35 successful responses, 0 failed responses, and 328 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 b.ns.3dresearch.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

328 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:53

All timestamps shown in UTC

Latest Resolved IP on Selected Date

199.102.77.100

Most recently resolved hosting IP on selected date

Successful Responses

35

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 b.ns.3dresearch.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
35 2026-08-26 11:53 639233414056832719
342 ms 199.102.77.100
34 2026-08-26 11:35 639233403515141099
26 ms 199.102.77.100
33 2026-08-26 10:40 639233370841350248
223 ms 199.102.77.100
32 2026-08-26 10:23 639233360361507238
335 ms 199.102.77.100
31 2026-08-26 10:06 639233350067824371
336 ms 199.102.77.100
30 2026-08-26 09:49 639233339545274518
230 ms 199.102.77.100
29 2026-08-26 09:31 639233329214918079
7 ms 199.102.77.100
28 2026-08-26 09:14 639233318749762337
224 ms 199.102.77.100
27 2026-08-26 08:56 639233308387917838
336 ms 199.102.77.100
26 2026-08-26 08:39 639233297961740122
233 ms 199.102.77.100
25 2026-08-26 08:22 639233287487159094
8 ms 199.102.77.100
24 2026-08-26 08:04 639233276995531707
255 ms 199.102.77.100
23 2026-08-26 07:47 639233266521568229
334 ms 199.102.77.100
22 2026-08-26 07:29 639233256081047431
361 ms 199.102.77.100
21 2026-08-26 06:35 639233223620132921
2358 ms 199.102.77.100
20 2026-08-26 06:18 639233213287814244
347 ms 199.102.77.100
19 2026-08-26 06:01 639233202925983161
245 ms 199.102.77.100
18 2026-08-26 05:43 639233192644780696
235 ms 199.102.77.100
17 2026-08-26 05:26 639233182401183833
7 ms 199.102.77.100
16 2026-08-26 05:09 639233172074181051
367 ms 199.102.77.100
15 2026-08-26 04:52 639233161808421455
226 ms 199.102.77.100
14 2026-08-26 04:35 639233151357344052
338 ms 199.102.77.100
13 2026-08-26 04:17 639233141034116946
7 ms 199.102.77.100
12 2026-08-26 04:00 639233130828334142
233 ms 199.102.77.100
11 2026-08-26 03:43 639233120373450007
245 ms 199.102.77.100
10 2026-08-26 03:26 639233110066216193
344 ms 199.102.77.100
9 2026-08-26 02:33 639233078065410564
332 ms 199.102.77.100
8 2026-08-26 02:15 639233067787457832
7 ms 199.102.77.100
7 2026-08-26 01:58 639233057501801162
337 ms 199.102.77.100
6 2026-08-26 01:41 639233047089431703
2 ms 199.102.77.100
5 2026-08-26 01:24 639233036754790688
7 ms 199.102.77.100
4 2026-08-26 01:07 639233026412602472
2007 ms 199.102.77.100
3 2026-08-26 00:49 639233016064066127
226 ms 199.102.77.100
2 2026-08-26 00:32 639233005922655772
356 ms 199.102.77.100
1 2026-08-26 00:15 639232995672256907
9 ms 199.102.77.100