DNS response history for dc2.xeonbd.com

dc2.xeonbd.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-24. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 30 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 dc2.xeonbd.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

30 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 06:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.108.140.140

Most recently resolved hosting IP on selected date

Successful Responses

30

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 dc2.xeonbd.com

Showing DNS history for 2026-08-24 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
30 2026-08-24 06:16 639231488109699360
14 ms 103.108.140.140
29 2026-08-24 06:16 639231488109699360
14 ms 173.212.240.186
28 2026-08-24 05:23 639231456772510692
79 ms 103.108.140.140
27 2026-08-24 05:23 639231456772510692
79 ms 173.212.240.186
26 2026-08-24 05:07 639231447084631185
112 ms 173.212.240.186
25 2026-08-24 05:07 639231447084631185
112 ms 103.108.140.140
24 2026-08-24 04:51 639231437208519473
46 ms 173.212.240.186
23 2026-08-24 04:51 639231437208519473
46 ms 103.108.140.140
22 2026-08-24 04:34 639231427209627490
5 ms 103.108.140.140
21 2026-08-24 04:34 639231427209627490
5 ms 173.212.240.186
20 2026-08-24 03:42 639231395791246644
4 ms 103.108.140.140
19 2026-08-24 03:42 639231395791246644
4 ms 173.212.240.186
18 2026-08-24 03:26 639231386075551458
18 ms 103.108.140.140
17 2026-08-24 03:26 639231386075551458
18 ms 173.212.240.186
16 2026-08-24 03:09 639231376208713791
6 ms 103.108.140.140
15 2026-08-24 03:09 639231376208713791
6 ms 173.212.240.186
14 2026-08-24 02:52 639231366170589276
5 ms 103.108.140.140
13 2026-08-24 02:52 639231366170589276
5 ms 173.212.240.186
12 2026-08-24 02:00 639231334732159368
21 ms 103.108.140.140
11 2026-08-24 02:00 639231334732159368
21 ms 173.212.240.186
10 2026-08-24 01:44 639231325035670078
14 ms 103.108.140.140
9 2026-08-24 01:44 639231325035670078
14 ms 173.212.240.186
8 2026-08-24 01:27 639231315132253837
15 ms 173.212.240.186
7 2026-08-24 01:27 639231315132253837
15 ms 103.108.140.140
6 2026-08-24 01:11 639231305014280808
36 ms 173.212.240.186
5 2026-08-24 01:11 639231305014280808
36 ms 103.108.140.140
4 2026-08-24 00:18 639231273779380675
48 ms 103.108.140.140
3 2026-08-24 00:18 639231273779380675
48 ms 173.212.240.186
2 2026-08-24 00:02 639231264180839154
28 ms 103.108.140.140
1 2026-08-24 00:02 639231264180839154
28 ms 173.212.240.186