DNS response history for ns3.bjmmedia.com

ns3.bjmmedia.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-25. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 306 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 ns3.bjmmedia.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

306 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

67.225.210.152

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 ns3.bjmmedia.com

Showing DNS history for 2026-08-25 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-25 09:42 639232471861770303
135 ms 67.225.210.152
27 2026-08-25 09:25 639232461630217327
113 ms 67.225.210.152
26 2026-08-25 09:08 639232451282965990
114 ms 67.225.210.152
25 2026-08-25 08:50 639232440814614938
121 ms 67.225.210.152
24 2026-08-25 08:33 639232430410720425
226 ms 67.225.210.152
23 2026-08-25 08:16 639232420003096185
116 ms 67.225.210.152
22 2026-08-25 07:58 639232409467287444
227 ms 67.225.210.152
21 2026-08-25 07:41 639232399077195997
2122 ms 67.225.210.152
20 2026-08-25 07:23 639232388731528337
231 ms 67.225.210.152
19 2026-08-25 07:06 639232378288598612
232 ms 67.225.210.152
18 2026-08-25 06:12 639232346196373643
128 ms 67.225.210.152
17 2026-08-25 05:55 639232336112370741
151 ms 67.225.210.152
16 2026-08-25 05:39 639232326146508970
114 ms 67.225.210.152
15 2026-08-25 05:22 639232316189381720
228 ms 67.225.210.152
14 2026-08-25 05:06 639232306217998913
112 ms 67.225.210.152
13 2026-08-25 04:49 639232296255744174
237 ms 67.225.210.152
12 2026-08-25 04:32 639232286095760789
226 ms 67.225.210.152
11 2026-08-25 04:15 639232276086186273
232 ms 67.225.210.152
10 2026-08-25 03:59 639232265900986425
232 ms 67.225.210.152
9 2026-08-25 03:42 639232255723518075
2129 ms 67.225.210.152
8 2026-08-25 03:24 639232245484452890
231 ms 67.225.210.152
7 2026-08-25 03:07 639232235157175331
116 ms 67.225.210.152
6 2026-08-25 02:14 639232203197189095
220 ms 67.225.210.152
5 2026-08-25 01:57 639232192844564298
114 ms 67.225.210.152
4 2026-08-25 01:40 639232182496008942
111 ms 67.225.210.152
3 2026-08-25 01:22 639232172197053132
110 ms 67.225.210.152
2 2026-08-25 00:29 639232140250307418
230 ms 67.225.210.152
1 2026-08-25 00:12 639232129927860324
3 ms 67.225.210.152