DNS response history for ns2.fancm.com

ns2.fancm.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 36 DNS check records, 36 successful responses, 0 failed responses, and 297 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.fancm.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

297 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 11:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

15.235.102.123

Most recently resolved hosting IP on selected date

Successful Responses

36

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.fancm.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
36 2026-08-30 11:50 639236867916029489
6 ms 15.235.102.123
35 2026-08-30 11:33 639236858088772005
9 ms 15.235.102.123
34 2026-08-30 11:16 639236848158742395
214 ms 15.235.102.123
33 2026-08-30 11:00 639236838137395574
224 ms 15.235.102.123
32 2026-08-30 10:43 639236827967386881
214 ms 15.235.102.123
31 2026-08-30 10:26 639236817708615077
109 ms 15.235.102.123
30 2026-08-30 09:33 639236785770651804
103 ms 15.235.102.123
29 2026-08-30 09:16 639236775820686373
113 ms 15.235.102.123
28 2026-08-30 08:59 639236765768339082
6 ms 15.235.102.123
27 2026-08-30 08:42 639236755602384085
5 ms 15.235.102.123
26 2026-08-30 08:25 639236745600094925
2127 ms 15.235.102.123
25 2026-08-30 08:09 639236735311262753
211 ms 15.235.102.123
24 2026-08-30 07:51 639236724996745235
107 ms 15.235.102.123
23 2026-08-30 07:34 639236714839899761
3 ms 15.235.102.123
22 2026-08-30 07:18 639236704748431488
3 ms 15.235.102.123
21 2026-08-30 07:01 639236694430128550
2119 ms 15.235.102.123
20 2026-08-30 06:43 639236684143292417
216 ms 15.235.102.123
19 2026-08-30 06:26 639236673972499943
219 ms 15.235.102.123
18 2026-08-30 05:33 639236642126522802
2105 ms 15.235.102.123
17 2026-08-30 05:17 639236632183518198
219 ms 15.235.102.123
16 2026-08-30 05:00 639236622289312589
220 ms 15.235.102.123
15 2026-08-30 04:43 639236612490676525
2 ms 15.235.102.123
14 2026-08-30 04:27 639236602582494852
2 ms 15.235.102.123
13 2026-08-30 04:11 639236592511706469
216 ms 15.235.102.123
12 2026-08-30 03:54 639236582441006869
215 ms 15.235.102.123
11 2026-08-30 03:37 639236572478785089
216 ms 15.235.102.123
10 2026-08-30 03:20 639236562556749999
3 ms 15.235.102.123
9 2026-08-30 03:04 639236552353482281
179 ms 15.235.102.123
8 2026-08-30 02:47 639236542188881607
111 ms 15.235.102.123
7 2026-08-30 02:30 639236531885440105
220 ms 15.235.102.123
6 2026-08-30 01:36 639236499922985383
109 ms 15.235.102.123
5 2026-08-30 01:19 639236489713594431
212 ms 15.235.102.123
4 2026-08-30 01:03 639236479750443901
215 ms 15.235.102.123
3 2026-08-30 00:46 639236469719936375
219 ms 15.235.102.123
2 2026-08-30 00:29 639236459579244885
2 ms 15.235.102.123
1 2026-08-30 00:12 639236449582837549
216 ms 15.235.102.123