DNS response history for draco2.ns22.com

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

37

Historical checks stored for this nameserver on selected date

Average Latency

280 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 12:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

95.130.171.165

Most recently resolved hosting IP on selected date

Successful Responses

37

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 draco2.ns22.com

Showing DNS history for 2026-08-30 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
37 2026-08-30 12:06 639236878057367680
48 ms 95.130.171.165
36 2026-08-30 11:49 639236867916029489
1610 ms 95.130.171.165
35 2026-08-30 11:32 639236858088772005
56 ms 95.130.171.165
34 2026-08-30 11:16 639236848158742395
44 ms 95.130.171.165
33 2026-08-30 10:59 639236838137395574
48 ms 95.130.171.165
32 2026-08-30 10:43 639236827967386881
53 ms 95.130.171.165
31 2026-08-30 10:25 639236817708615077
98 ms 95.130.171.165
30 2026-08-30 09:32 639236785770651804
2058 ms 95.130.171.165
29 2026-08-30 09:16 639236775820686373
87 ms 95.130.171.165
28 2026-08-30 08:59 639236765768339082
43 ms 95.130.171.165
27 2026-08-30 08:42 639236755602384085
46 ms 95.130.171.165
26 2026-08-30 08:25 639236745600094925
8 ms 95.130.171.165
25 2026-08-30 08:08 639236735311262753
1611 ms 95.130.171.165
24 2026-08-30 07:51 639236724996745235
57 ms 95.130.171.165
23 2026-08-30 07:34 639236714839899761
4 ms 95.130.171.165
22 2026-08-30 07:17 639236704748431488
45 ms 95.130.171.165
21 2026-08-30 07:00 639236694430128550
79 ms 95.130.171.165
20 2026-08-30 06:43 639236684143292417
47 ms 95.130.171.165
19 2026-08-30 06:26 639236673972499943
48 ms 95.130.171.165
18 2026-08-30 05:33 639236642126522802
3 ms 95.130.171.165
17 2026-08-30 05:16 639236632183518198
59 ms 95.130.171.165
16 2026-08-30 05:00 639236622289312589
1607 ms 95.130.171.165
15 2026-08-30 04:43 639236612490676525
44 ms 95.130.171.165
14 2026-08-30 04:27 639236602582494852
2 ms 95.130.171.165
13 2026-08-30 04:10 639236592511706469
46 ms 95.130.171.165
12 2026-08-30 03:53 639236582441006869
44 ms 95.130.171.165
11 2026-08-30 03:37 639236572478785089
2 ms 95.130.171.165
10 2026-08-30 03:20 639236562556749999
2056 ms 95.130.171.165
9 2026-08-30 03:03 639236552353482281
49 ms 95.130.171.165
8 2026-08-30 02:46 639236542188881607
46 ms 95.130.171.165
7 2026-08-30 02:29 639236531885440105
42 ms 95.130.171.165
6 2026-08-30 01:36 639236499922985383
49 ms 95.130.171.165
5 2026-08-30 01:19 639236489713594431
44 ms 95.130.171.165
4 2026-08-30 01:02 639236479750443901
47 ms 95.130.171.165
3 2026-08-30 00:45 639236469719936375
44 ms 95.130.171.165
2 2026-08-30 00:29 639236459579244885
51 ms 95.130.171.165
1 2026-08-30 00:12 639236449582837549
52 ms 95.130.171.165