DNS response history for bjdns3.mediatek.com

bjdns3.mediatek.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-29. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 259 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 bjdns3.mediatek.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

259 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-29 10:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

36.110.107.41

Most recently resolved hosting IP on selected date

Successful Responses

29

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 bjdns3.mediatek.com

Showing DNS history for 2026-08-29 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
29 2026-08-29 10:30 639235956590882003
162 ms 36.110.107.41
28 2026-08-29 09:36 639235924465736791
162 ms 36.110.107.41
27 2026-08-29 09:19 639235914430611197
176 ms 36.110.107.41
26 2026-08-29 09:03 639235904343784853
160 ms 36.110.107.41
25 2026-08-29 08:46 639235894201078068
160 ms 36.110.107.41
24 2026-08-29 08:29 639235884233447452
2157 ms 36.110.107.41
23 2026-08-29 08:12 639235874142207309
158 ms 36.110.107.41
22 2026-08-29 07:55 639235863974652466
158 ms 36.110.107.41
21 2026-08-29 07:38 639235853716243436
567 ms 36.110.107.41
20 2026-08-29 07:22 639235843614494759
160 ms 36.110.107.41
19 2026-08-29 07:04 639235833401459551
160 ms 36.110.107.41
18 2026-08-29 06:47 639235823220464528
162 ms 36.110.107.41
17 2026-08-29 06:30 639235812997510905
274 ms 36.110.107.41
16 2026-08-29 05:37 639235781101962521
276 ms 36.110.107.41
15 2026-08-29 05:20 639235771207673260
159 ms 36.110.107.41
14 2026-08-29 05:04 639235761047429642
161 ms 36.110.107.41
13 2026-08-29 04:47 639235750964347246
165 ms 36.110.107.41
12 2026-08-29 04:30 639235740923490874
172 ms 36.110.107.41
11 2026-08-29 04:13 639235730842894399
162 ms 36.110.107.41
10 2026-08-29 03:57 639235720760084717
163 ms 36.110.107.41
9 2026-08-29 03:40 639235710843666743
161 ms 36.110.107.41
8 2026-08-29 03:23 639235700733510561
171 ms 36.110.107.41
7 2026-08-29 03:06 639235690509906192
151 ms 36.110.107.41
6 2026-08-29 02:49 639235680156673501
251 ms 36.110.107.41
5 2026-08-29 02:32 639235669720606443
152 ms 36.110.107.41
4 2026-08-29 01:38 639235637451417084
152 ms 36.110.107.41
3 2026-08-29 01:21 639235627307383453
266 ms 36.110.107.41
2 2026-08-29 01:04 639235616906386856
168 ms 36.110.107.41
1 2026-08-29 00:46 639235606582912691
161 ms 36.110.107.41