DNS response history for ns1.b2fly.cloud

ns1.b2fly.cloud 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 38 DNS check records, 38 successful responses, 0 failed responses, and 411 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.b2fly.cloud.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

411 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

149.28.212.92

Most recently resolved hosting IP on selected date

Successful Responses

38

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.b2fly.cloud

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
38 2026-08-26 12:32 639233434974187439
349 ms 149.28.212.92
37 2026-08-26 12:14 639233424567558554
179 ms 149.28.212.92
36 2026-08-26 11:57 639233414056832719
164 ms 149.28.212.92
35 2026-08-26 11:39 639233403515141099
163 ms 149.28.212.92
34 2026-08-26 10:44 639233370841350248
344 ms 149.28.212.92
33 2026-08-26 10:27 639233360361507238
167 ms 149.28.212.92
32 2026-08-26 10:10 639233350067824371
340 ms 149.28.212.92
31 2026-08-26 09:53 639233339545274518
339 ms 149.28.212.92
30 2026-08-26 09:35 639233329214918079
337 ms 149.28.212.92
29 2026-08-26 09:18 639233318749762337
1878 ms 149.28.212.92
28 2026-08-26 09:00 639233308387917838
342 ms 149.28.212.92
27 2026-08-26 08:43 639233297961740122
337 ms 149.28.212.92
26 2026-08-26 08:26 639233287487159094
345 ms 149.28.212.92
25 2026-08-26 08:08 639233276995531707
340 ms 149.28.212.92
24 2026-08-26 07:51 639233266521568229
335 ms 149.28.212.92
23 2026-08-26 07:33 639233256081047431
346 ms 149.28.212.92
22 2026-08-26 06:39 639233223620132921
4 ms 149.28.212.92
21 2026-08-26 06:22 639233213287814244
3 ms 149.28.212.92
20 2026-08-26 06:05 639233202925983161
748 ms 149.28.212.92
19 2026-08-26 05:47 639233192644780696
342 ms 149.28.212.92
18 2026-08-26 05:30 639233182401183833
338 ms 149.28.212.92
17 2026-08-26 05:13 639233172074181051
335 ms 149.28.212.92
16 2026-08-26 04:56 639233161808421455
924 ms 149.28.212.92
15 2026-08-26 04:39 639233151357344052
181 ms 149.28.212.92
14 2026-08-26 04:22 639233141034116946
334 ms 149.28.212.92
13 2026-08-26 04:04 639233130828334142
167 ms 149.28.212.92
12 2026-08-26 03:47 639233120373450007
345 ms 149.28.212.92
11 2026-08-26 03:30 639233110066216193
341 ms 149.28.212.92
10 2026-08-26 02:37 639233078065410564
2157 ms 149.28.212.92
9 2026-08-26 02:19 639233067787457832
334 ms 149.28.212.92
8 2026-08-26 02:02 639233057501801162
335 ms 149.28.212.92
7 2026-08-26 01:45 639233047089431703
168 ms 149.28.212.92
6 2026-08-26 01:28 639233036754790688
340 ms 149.28.212.92
5 2026-08-26 01:11 639233026412602472
909 ms 149.28.212.92
4 2026-08-26 00:53 639233016064066127
360 ms 149.28.212.92
3 2026-08-26 00:36 639233005922655772
168 ms 149.28.212.92
2 2026-08-26 00:19 639232995672256907
161 ms 149.28.212.92
1 2026-08-26 00:02 639232985300872416
337 ms 149.28.212.92