DNS response history for ns2.fitiony.com

ns2.fitiony.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 45 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 ns2.fitiony.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

45 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 11:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.206.180.71

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 ns2.fitiony.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 11:59 639236878057367680
67 ms 185.206.180.71
36 2026-08-30 11:42 639236867916029489
52 ms 185.206.180.71
35 2026-08-30 11:26 639236858088772005
46 ms 185.206.180.71
34 2026-08-30 11:09 639236848158742395
51 ms 185.206.180.71
33 2026-08-30 10:53 639236838137395574
139 ms 185.206.180.71
32 2026-08-30 10:36 639236827967386881
13 ms 185.206.180.71
31 2026-08-30 10:19 639236817708615077
58 ms 185.206.180.71
30 2026-08-30 09:26 639236785770651804
18 ms 185.206.180.71
29 2026-08-30 09:09 639236775820686373
38 ms 185.206.180.71
28 2026-08-30 08:52 639236765768339082
25 ms 185.206.180.71
27 2026-08-30 08:35 639236755602384085
48 ms 185.206.180.71
26 2026-08-30 08:18 639236745600094925
28 ms 185.206.180.71
25 2026-08-30 08:01 639236735311262753
23 ms 185.206.180.71
24 2026-08-30 07:44 639236724996745235
13 ms 185.206.180.71
23 2026-08-30 07:27 639236714839899761
33 ms 185.206.180.71
22 2026-08-30 07:10 639236704748431488
38 ms 185.206.180.71
21 2026-08-30 06:53 639236694430128550
33 ms 185.206.180.71
20 2026-08-30 06:36 639236684143292417
172 ms 185.206.180.71
19 2026-08-30 06:19 639236673972499943
36 ms 185.206.180.71
18 2026-08-30 05:26 639236642126522802
82 ms 185.206.180.71
17 2026-08-30 05:10 639236632183518198
37 ms 185.206.180.71
16 2026-08-30 04:53 639236622289312589
21 ms 185.206.180.71
15 2026-08-30 04:37 639236612490676525
59 ms 185.206.180.71
14 2026-08-30 04:20 639236602582494852
64 ms 185.206.180.71
13 2026-08-30 04:03 639236592511706469
27 ms 185.206.180.71
12 2026-08-30 03:47 639236582441006869
55 ms 185.206.180.71
11 2026-08-30 03:30 639236572478785089
35 ms 185.206.180.71
10 2026-08-30 03:13 639236562556749999
10 ms 185.206.180.71
9 2026-08-30 02:56 639236552353482281
24 ms 185.206.180.71
8 2026-08-30 02:39 639236542188881607
32 ms 185.206.180.71
7 2026-08-30 02:22 639236531885440105
137 ms 185.206.180.71
6 2026-08-30 01:29 639236499922985383
25 ms 185.206.180.71
5 2026-08-30 01:12 639236489713594431
32 ms 185.206.180.71
4 2026-08-30 00:55 639236479750443901
9 ms 185.206.180.71
3 2026-08-30 00:39 639236469719936375
26 ms 185.206.180.71
2 2026-08-30 00:22 639236459579244885
24 ms 185.206.180.71
1 2026-08-30 00:05 639236449582837549
33 ms 185.206.180.71