DNS response history for ns1.bidram.net

ns1.bidram.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 34 DNS check records, 12 successful responses, 22 failed responses, and 1414 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.bidram.net.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

1414 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

45.139.11.50

Most recently resolved hosting IP on selected date

Successful Responses

12

Checks that returned a measurable response

Failed Responses

22

Checks with no response or no returned latency

Failure Rate

65%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.bidram.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
34 2026-08-26 10:47 639233370841350248
-
33 2026-08-26 10:29 639233360361507238
1954 ms 45.139.11.50
32 2026-08-26 10:12 639233350067824371
1746 ms 45.139.11.50
31 2026-08-26 09:55 639233339545274518
-
30 2026-08-26 09:37 639233329214918079
-
29 2026-08-26 09:20 639233318749762337
-
28 2026-08-26 09:03 639233308387917838
-
27 2026-08-26 08:45 639233297961740122
-
26 2026-08-26 08:28 639233287487159094
-
25 2026-08-26 08:11 639233276995531707
-
24 2026-08-26 07:53 639233266521568229
1711 ms 45.139.11.50
23 2026-08-26 07:36 639233256081047431
-
22 2026-08-26 06:41 639233223620132921
-
21 2026-08-26 06:24 639233213287814244
-
20 2026-08-26 06:07 639233202925983161
-
19 2026-08-26 05:50 639233192644780696
-
18 2026-08-26 05:32 639233182401183833
-
17 2026-08-26 05:15 639233172074181051
-
16 2026-08-26 04:58 639233161808421455
-
15 2026-08-26 04:41 639233151357344052
3 ms 45.139.11.50
14 2026-08-26 04:24 639233141034116946
-
13 2026-08-26 04:06 639233130828334142
-
12 2026-08-26 03:49 639233120373450007
3 ms 45.139.11.50
11 2026-08-26 03:32 639233110066216193
2 ms 45.139.11.50
10 2026-08-26 02:39 639233078065410564
-
9 2026-08-26 02:22 639233067787457832
-
8 2026-08-26 02:04 639233057501801162
-
7 2026-08-26 01:47 639233047089431703
3 ms 45.139.11.50
6 2026-08-26 01:30 639233036754790688
4004 ms 45.139.11.50
5 2026-08-26 01:13 639233026412602472
1847 ms 45.139.11.50
4 2026-08-26 00:55 639233016064066127
4 ms 45.139.11.50
3 2026-08-26 00:38 639233005922655772
4004 ms 45.139.11.50
2 2026-08-26 00:21 639232995672256907
1682 ms 45.139.11.50
1 2026-08-26 00:04 639232985300872416
-