DNS response history for ns1.billionmark.com

ns1.billionmark.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 33 DNS check records, 33 successful responses, 0 failed responses, and 363 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.billionmark.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

363 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

67.18.64.171

Most recently resolved hosting IP on selected date

Successful Responses

33

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.billionmark.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
33 2026-08-26 10:42 639233370841350248
300 ms 67.18.64.171
32 2026-08-26 10:24 639233360361507238
305 ms 67.18.64.171
31 2026-08-26 10:07 639233350067824371
8 ms 67.18.64.171
30 2026-08-26 09:50 639233339545274518
276 ms 67.18.64.171
29 2026-08-26 09:32 639233329214918079
139 ms 67.18.64.171
28 2026-08-26 09:15 639233318749762337
248 ms 67.18.64.171
27 2026-08-26 08:58 639233308387917838
261 ms 67.18.64.171
26 2026-08-26 08:40 639233297961740122
587 ms 67.18.64.171
25 2026-08-26 08:23 639233287487159094
293 ms 67.18.64.171
24 2026-08-26 08:05 639233276995531707
151 ms 67.18.64.171
23 2026-08-26 07:48 639233266521568229
275 ms 67.18.64.171
22 2026-08-26 07:30 639233256081047431
146 ms 67.18.64.171
21 2026-08-26 06:37 639233223620132921
258 ms 67.18.64.171
20 2026-08-26 06:19 639233213287814244
283 ms 67.18.64.171
19 2026-08-26 06:02 639233202925983161
546 ms 67.18.64.171
18 2026-08-26 05:45 639233192644780696
2149 ms 67.18.64.171
17 2026-08-26 05:28 639233182401183833
286 ms 67.18.64.171
16 2026-08-26 05:11 639233172074181051
144 ms 67.18.64.171
15 2026-08-26 04:53 639233161808421455
290 ms 67.18.64.171
14 2026-08-26 04:36 639233151357344052
258 ms 67.18.64.171
13 2026-08-26 04:19 639233141034116946
244 ms 67.18.64.171
12 2026-08-26 04:02 639233130828334142
272 ms 67.18.64.171
11 2026-08-26 03:44 639233120373450007
124 ms 67.18.64.171
10 2026-08-26 03:27 639233110066216193
571 ms 67.18.64.171
9 2026-08-26 02:34 639233078065410564
294 ms 67.18.64.171
8 2026-08-26 02:17 639233067787457832
8 ms 67.18.64.171
7 2026-08-26 01:59 639233057501801162
14 ms 67.18.64.171
6 2026-08-26 01:42 639233047089431703
136 ms 67.18.64.171
5 2026-08-26 01:25 639233036754790688
7 ms 67.18.64.171
4 2026-08-26 01:08 639233026412602472
135 ms 67.18.64.171
3 2026-08-26 00:50 639233016064066127
549 ms 67.18.64.171
2 2026-08-26 00:33 639233005922655772
2137 ms 67.18.64.171
1 2026-08-26 00:16 639232995672256907
291 ms 67.18.64.171