DNS response history for ns2.bmeplus.com

ns2.bmeplus.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 28 DNS check records, 28 successful responses, 0 failed responses, and 427 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.bmeplus.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

427 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.30.127.12

Most recently resolved hosting IP on selected date

Successful Responses

28

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.bmeplus.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
28 2026-08-27 09:15 639234181105879568
391 ms 103.30.127.12
27 2026-08-27 08:57 639234170713214496
375 ms 103.30.127.12
26 2026-08-27 08:40 639234160341037652
339 ms 103.30.127.12
25 2026-08-27 08:23 639234149799404224
382 ms 103.30.127.12
24 2026-08-27 08:05 639234139553286469
355 ms 103.30.127.12
23 2026-08-27 07:11 639234107183588293
357 ms 103.30.127.12
22 2026-08-27 06:54 639234096905435724
388 ms 103.30.127.12
21 2026-08-27 06:37 639234086579410775
369 ms 103.30.127.12
20 2026-08-27 06:20 639234076291157956
353 ms 103.30.127.12
19 2026-08-27 06:03 639234065981939454
2232 ms 103.30.127.12
18 2026-08-27 05:45 639234055548642997
379 ms 103.30.127.12
17 2026-08-27 05:28 639234045267979603
390 ms 103.30.127.12
16 2026-08-27 05:11 639234034999717463
191 ms 103.30.127.12
15 2026-08-27 04:54 639234024739225358
354 ms 103.30.127.12
14 2026-08-27 04:37 639234014311170162
378 ms 103.30.127.12
13 2026-08-27 04:19 639234003806017640
355 ms 103.30.127.12
12 2026-08-27 04:02 639233993356203030
367 ms 103.30.127.12
11 2026-08-27 03:08 639233961301716608
338 ms 103.30.127.12
10 2026-08-27 02:51 639233950834200647
359 ms 103.30.127.12
9 2026-08-27 02:34 639233940431849026
385 ms 103.30.127.12
8 2026-08-27 02:16 639233930110596398
475 ms 103.30.127.12
7 2026-08-27 01:59 639233919705434540
377 ms 103.30.127.12
6 2026-08-27 01:42 639233909452807845
395 ms 103.30.127.12
5 2026-08-27 01:25 639233899096420820
356 ms 103.30.127.12
4 2026-08-27 01:07 639233888707824939
239 ms 103.30.127.12
3 2026-08-27 00:50 639233878461203802
364 ms 103.30.127.12
2 2026-08-27 00:33 639233868060868209
351 ms 103.30.127.12
1 2026-08-27 00:15 639233857450922991
372 ms 103.30.127.12