DNS response history for bot.dynamics365.cn

bot.dynamics365.cn 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 35 DNS check records, 35 successful responses, 0 failed responses, and 500 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 bot.dynamics365.cn.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

500 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

39.105.123.67

Most recently resolved hosting IP on selected date

Successful Responses

35

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 bot.dynamics365.cn

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
35 2026-08-25 12:24 639232566381512620
262 ms 39.105.123.67
34 2026-08-25 12:07 639232556111768563
612 ms 39.105.123.67
33 2026-08-25 11:50 639232545839529039
543 ms 39.105.123.67
32 2026-08-25 11:33 639232535349285207
696 ms 39.105.123.67
31 2026-08-25 11:15 639232524938080723
296 ms 39.105.123.67
30 2026-08-25 10:21 639232492740373468
1092 ms 39.105.123.67
29 2026-08-25 10:04 639232482235303141
677 ms 39.105.123.67
28 2026-08-25 09:47 639232471861770303
1057 ms 39.105.123.67
27 2026-08-25 09:29 639232461630217327
325 ms 39.105.123.67
26 2026-08-25 09:12 639232451282965990
322 ms 39.105.123.67
25 2026-08-25 08:55 639232440814614938
460 ms 39.105.123.67
24 2026-08-25 08:38 639232430410720425
435 ms 39.105.123.67
23 2026-08-25 08:20 639232420003096185
1064 ms 39.105.123.67
22 2026-08-25 08:03 639232409467287444
642 ms 39.105.123.67
21 2026-08-25 07:45 639232399077195997
284 ms 39.105.123.67
20 2026-08-25 07:28 639232388731528337
437 ms 39.105.123.67
19 2026-08-25 07:11 639232378288598612
259 ms 39.105.123.67
18 2026-08-25 06:17 639232346196373643
259 ms 39.105.123.67
17 2026-08-25 06:00 639232336112370741
294 ms 39.105.123.67
16 2026-08-25 05:43 639232326146508970
907 ms 39.105.123.67
15 2026-08-25 05:27 639232316189381720
652 ms 39.105.123.67
14 2026-08-25 05:10 639232306217998913
300 ms 39.105.123.67
13 2026-08-25 04:54 639232296255744174
411 ms 39.105.123.67
12 2026-08-25 04:37 639232286095760789
594 ms 39.105.123.67
11 2026-08-25 04:20 639232276086186273
276 ms 39.105.123.67
10 2026-08-25 04:03 639232265900986425
306 ms 39.105.123.67
9 2026-08-25 03:46 639232255723518075
268 ms 39.105.123.67
8 2026-08-25 03:29 639232245484452890
641 ms 39.105.123.67
7 2026-08-25 03:12 639232235157175331
253 ms 39.105.123.67
6 2026-08-25 02:19 639232203197189095
266 ms 39.105.123.67
5 2026-08-25 02:02 639232192844564298
922 ms 39.105.123.67
4 2026-08-25 01:44 639232182496008942
557 ms 39.105.123.67
3 2026-08-25 01:27 639232172197053132
553 ms 39.105.123.67
2 2026-08-25 00:34 639232140250307418
255 ms 39.105.123.67
1 2026-08-25 00:17 639232129927860324
327 ms 39.105.123.67