DNS response history for ns2.bmsbase.com

ns2.bmsbase.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-27. For this date, NameServerHistory found 25 DNS check records, 25 successful responses, 0 failed responses, and 288 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.bmsbase.com.
Records on Selected Date

25

Historical checks stored for this nameserver on selected date

Average Latency

288 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 08:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

82.165.119.121

Most recently resolved hosting IP on selected date

Successful Responses

25

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.bmsbase.com

Showing DNS history for 2026-08-27 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
25 2026-08-27 08:15 639234149799404224
61 ms 82.165.119.121
24 2026-08-27 07:57 639234139553286469
33 ms 82.165.119.121
23 2026-08-27 07:03 639234107183588293
58 ms 82.165.119.121
22 2026-08-27 06:46 639234096905435724
11 ms 82.165.119.121
21 2026-08-27 06:29 639234086579410775
21 ms 82.165.119.121
20 2026-08-27 06:12 639234076291157956
95 ms 82.165.119.121
19 2026-08-27 05:55 639234065981939454
97 ms 82.165.119.121
18 2026-08-27 05:38 639234055548642997
36 ms 82.165.119.121
17 2026-08-27 05:20 639234045267979603
50 ms 82.165.119.121
16 2026-08-27 05:03 639234034999717463
17 ms 82.165.119.121
15 2026-08-27 04:46 639234024739225358
42 ms 82.165.119.121
14 2026-08-27 04:29 639234014311170162
2037 ms 82.165.119.121
13 2026-08-27 04:11 639234003806017640
61 ms 82.165.119.121
12 2026-08-27 03:54 639233993356203030
58 ms 82.165.119.121
11 2026-08-27 03:00 639233961301716608
77 ms 82.165.119.121
10 2026-08-27 02:43 639233950834200647
31 ms 82.165.119.121
9 2026-08-27 02:26 639233940431849026
54 ms 82.165.119.121
8 2026-08-27 02:08 639233930110596398
53 ms 82.165.119.121
7 2026-08-27 01:51 639233919705434540
33 ms 82.165.119.121
6 2026-08-27 01:34 639233909452807845
52 ms 82.165.119.121
5 2026-08-27 01:17 639233899096420820
2067 ms 82.165.119.121
4 2026-08-27 00:59 639233888707824939
47 ms 82.165.119.121
3 2026-08-27 00:42 639233878461203802
2010 ms 82.165.119.121
2 2026-08-27 00:25 639233868060868209
37 ms 82.165.119.121
1 2026-08-27 00:07 639233857450922991
55 ms 82.165.119.121