DNS response history for ns1.bismon.com

ns1.bismon.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 354 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.bismon.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

354 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.78.103.197

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 ns1.bismon.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:38 639233403515141099
353 ms 203.78.103.197
34 2026-08-26 10:43 639233370841350248
187 ms 203.78.103.197
33 2026-08-26 10:26 639233360361507238
365 ms 203.78.103.197
32 2026-08-26 10:09 639233350067824371
167 ms 203.78.103.197
31 2026-08-26 09:52 639233339545274518
332 ms 203.78.103.197
30 2026-08-26 09:34 639233329214918079
365 ms 203.78.103.197
29 2026-08-26 09:17 639233318749762337
376 ms 203.78.103.197
28 2026-08-26 08:59 639233308387917838
364 ms 203.78.103.197
27 2026-08-26 08:42 639233297961740122
360 ms 203.78.103.197
26 2026-08-26 08:25 639233287487159094
370 ms 203.78.103.197
25 2026-08-26 08:07 639233276995531707
367 ms 203.78.103.197
24 2026-08-26 07:50 639233266521568229
385 ms 203.78.103.197
23 2026-08-26 07:32 639233256081047431
381 ms 203.78.103.197
22 2026-08-26 06:38 639233223620132921
185 ms 203.78.103.197
21 2026-08-26 06:21 639233213287814244
359 ms 203.78.103.197
20 2026-08-26 06:04 639233202925983161
377 ms 203.78.103.197
19 2026-08-26 05:46 639233192644780696
351 ms 203.78.103.197
18 2026-08-26 05:29 639233182401183833
181 ms 203.78.103.197
17 2026-08-26 05:12 639233172074181051
355 ms 203.78.103.197
16 2026-08-26 04:55 639233161808421455
200 ms 203.78.103.197
15 2026-08-26 04:38 639233151357344052
170 ms 203.78.103.197
14 2026-08-26 04:20 639233141034116946
179 ms 203.78.103.197
13 2026-08-26 04:03 639233130828334142
383 ms 203.78.103.197
12 2026-08-26 03:46 639233120373450007
2202 ms 203.78.103.197
11 2026-08-26 03:29 639233110066216193
184 ms 203.78.103.197
10 2026-08-26 02:35 639233078065410564
3 ms 203.78.103.197
9 2026-08-26 02:18 639233067787457832
364 ms 203.78.103.197
8 2026-08-26 02:01 639233057501801162
379 ms 203.78.103.197
7 2026-08-26 01:44 639233047089431703
364 ms 203.78.103.197
6 2026-08-26 01:27 639233036754790688
364 ms 203.78.103.197
5 2026-08-26 01:10 639233026412602472
366 ms 203.78.103.197
4 2026-08-26 00:52 639233016064066127
363 ms 203.78.103.197
3 2026-08-26 00:35 639233005922655772
168 ms 203.78.103.197
2 2026-08-26 00:18 639232995672256907
353 ms 203.78.103.197
1 2026-08-26 00:01 639232985300872416
171 ms 203.78.103.197