DNS response history for ns2.fullbiz.net

ns2.fullbiz.net 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 39 DNS check records, 39 successful responses, 0 failed responses, and 344 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 ns2.fullbiz.net.
Records on Selected Date

39

Historical checks stored for this nameserver on selected date

Average Latency

344 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 13:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

191.101.18.49

Most recently resolved hosting IP on selected date

Successful Responses

39

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 ns2.fullbiz.net

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
39 2026-08-26 13:04 639233455747096265
259 ms 191.101.18.49
38 2026-08-26 12:46 639233445367152284
291 ms 191.101.18.49
37 2026-08-26 12:29 639233434974187439
284 ms 191.101.18.49
36 2026-08-26 12:11 639233424567558554
286 ms 191.101.18.49
35 2026-08-26 11:54 639233414056832719
210 ms 191.101.18.49
34 2026-08-26 11:36 639233403515141099
12 ms 191.101.18.49
33 2026-08-26 10:42 639233370841350248
284 ms 191.101.18.49
32 2026-08-26 10:25 639233360361507238
298 ms 191.101.18.49
31 2026-08-26 10:07 639233350067824371
283 ms 191.101.18.49
30 2026-08-26 09:50 639233339545274518
286 ms 191.101.18.49
29 2026-08-26 09:32 639233329214918079
280 ms 191.101.18.49
28 2026-08-26 09:15 639233318749762337
231 ms 191.101.18.49
27 2026-08-26 08:58 639233308387917838
2031 ms 191.101.18.49
26 2026-08-26 08:40 639233297961740122
288 ms 191.101.18.49
25 2026-08-26 08:23 639233287487159094
201 ms 191.101.18.49
24 2026-08-26 08:06 639233276995531707
284 ms 191.101.18.49
23 2026-08-26 07:48 639233266521568229
301 ms 191.101.18.49
22 2026-08-26 07:31 639233256081047431
291 ms 191.101.18.49
21 2026-08-26 06:37 639233223620132921
324 ms 191.101.18.49
20 2026-08-26 06:19 639233213287814244
286 ms 191.101.18.49
19 2026-08-26 06:02 639233202925983161
2206 ms 191.101.18.49
18 2026-08-26 05:45 639233192644780696
281 ms 191.101.18.49
17 2026-08-26 05:28 639233182401183833
263 ms 191.101.18.49
16 2026-08-26 05:11 639233172074181051
277 ms 191.101.18.49
15 2026-08-26 04:53 639233161808421455
219 ms 191.101.18.49
14 2026-08-26 04:36 639233151357344052
283 ms 191.101.18.49
13 2026-08-26 04:19 639233141034116946
287 ms 191.101.18.49
12 2026-08-26 04:02 639233130828334142
288 ms 191.101.18.49
11 2026-08-26 03:45 639233120373450007
14 ms 191.101.18.49
10 2026-08-26 03:27 639233110066216193
285 ms 191.101.18.49
9 2026-08-26 02:34 639233078065410564
279 ms 191.101.18.49
8 2026-08-26 02:17 639233067787457832
282 ms 191.101.18.49
7 2026-08-26 02:00 639233057501801162
272 ms 191.101.18.49
6 2026-08-26 01:42 639233047089431703
277 ms 191.101.18.49
5 2026-08-26 01:25 639233036754790688
280 ms 191.101.18.49
4 2026-08-26 01:08 639233026412602472
40 ms 191.101.18.49
3 2026-08-26 00:51 639233016064066127
3 ms 191.101.18.49
2 2026-08-26 00:34 639233005922655772
272 ms 191.101.18.49
1 2026-08-26 00:16 639232995672256907
285 ms 191.101.18.49