DNS response history for ns3.azuredns.jp

ns3.azuredns.jp 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, 34 successful responses, 0 failed responses, and 454 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.azuredns.jp.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

454 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

154.16.166.5

Most recently resolved hosting IP on selected date

Successful Responses

34

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.azuredns.jp

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:44 639233370841350248
503 ms 154.16.166.5
33 2026-08-26 10:27 639233360361507238
3832 ms 154.16.166.5
32 2026-08-26 10:10 639233350067824371
245 ms 154.16.166.5
31 2026-08-26 09:52 639233339545274518
480 ms 154.16.166.5
30 2026-08-26 09:35 639233329214918079
281 ms 154.16.166.5
29 2026-08-26 09:18 639233318749762337
468 ms 154.16.166.5
28 2026-08-26 09:00 639233308387917838
689 ms 154.16.166.5
27 2026-08-26 08:43 639233297961740122
233 ms 154.16.166.5
26 2026-08-26 08:25 639233287487159094
459 ms 154.16.166.5
25 2026-08-26 08:08 639233276995531707
246 ms 154.16.166.5
24 2026-08-26 07:50 639233266521568229
458 ms 154.16.166.5
23 2026-08-26 07:33 639233256081047431
249 ms 154.16.166.5
22 2026-08-26 06:39 639233223620132921
227 ms 154.16.166.5
21 2026-08-26 06:22 639233213287814244
7 ms 154.16.166.5
20 2026-08-26 06:04 639233202925983161
451 ms 154.16.166.5
19 2026-08-26 05:47 639233192644780696
221 ms 154.16.166.5
18 2026-08-26 05:30 639233182401183833
455 ms 154.16.166.5
17 2026-08-26 05:13 639233172074181051
470 ms 154.16.166.5
16 2026-08-26 04:56 639233161808421455
339 ms 154.16.166.5
15 2026-08-26 04:39 639233151357344052
716 ms 154.16.166.5
14 2026-08-26 04:21 639233141034116946
220 ms 154.16.166.5
13 2026-08-26 04:04 639233130828334142
229 ms 154.16.166.5
12 2026-08-26 03:47 639233120373450007
602 ms 154.16.166.5
11 2026-08-26 03:30 639233110066216193
20 ms 154.16.166.5
10 2026-08-26 02:36 639233078065410564
440 ms 154.16.166.5
9 2026-08-26 02:19 639233067787457832
444 ms 154.16.166.5
8 2026-08-26 02:02 639233057501801162
230 ms 154.16.166.5
7 2026-08-26 01:45 639233047089431703
438 ms 154.16.166.5
6 2026-08-26 01:28 639233036754790688
6 ms 154.16.166.5
5 2026-08-26 01:10 639233026412602472
222 ms 154.16.166.5
4 2026-08-26 00:53 639233016064066127
442 ms 154.16.166.5
3 2026-08-26 00:36 639233005922655772
447 ms 154.16.166.5
2 2026-08-26 00:19 639232995672256907
442 ms 154.16.166.5
1 2026-08-26 00:02 639232985300872416
234 ms 154.16.166.5