DNS response history for ns2.filelan.com

ns2.filelan.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-26. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 245 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.filelan.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

245 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

75.61.95.3

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 ns2.filelan.com

Showing DNS history for 2026-08-26 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-26 11:41 639233403515141099
246 ms 75.61.95.3
34 2026-08-26 10:46 639233370841350248
243 ms 75.61.95.3
33 2026-08-26 10:29 639233360361507238
242 ms 75.61.95.3
32 2026-08-26 10:12 639233350067824371
246 ms 75.61.95.3
31 2026-08-26 09:55 639233339545274518
246 ms 75.61.95.3
30 2026-08-26 09:37 639233329214918079
250 ms 75.61.95.3
29 2026-08-26 09:20 639233318749762337
245 ms 75.61.95.3
28 2026-08-26 09:02 639233308387917838
251 ms 75.61.95.3
27 2026-08-26 08:45 639233297961740122
246 ms 75.61.95.3
26 2026-08-26 08:28 639233287487159094
239 ms 75.61.95.3
25 2026-08-26 08:10 639233276995531707
251 ms 75.61.95.3
24 2026-08-26 07:53 639233266521568229
243 ms 75.61.95.3
23 2026-08-26 07:35 639233256081047431
250 ms 75.61.95.3
22 2026-08-26 06:41 639233223620132921
305 ms 75.61.95.3
21 2026-08-26 06:24 639233213287814244
238 ms 75.61.95.3
20 2026-08-26 06:07 639233202925983161
239 ms 75.61.95.3
19 2026-08-26 05:49 639233192644780696
247 ms 75.61.95.3
18 2026-08-26 05:32 639233182401183833
424 ms 75.61.95.3
17 2026-08-26 05:15 639233172074181051
255 ms 75.61.95.3
16 2026-08-26 04:58 639233161808421455
252 ms 75.61.95.3
15 2026-08-26 04:41 639233151357344052
250 ms 75.61.95.3
14 2026-08-26 04:23 639233141034116946
240 ms 75.61.95.3
13 2026-08-26 04:06 639233130828334142
239 ms 75.61.95.3
12 2026-08-26 03:49 639233120373450007
253 ms 75.61.95.3
11 2026-08-26 03:32 639233110066216193
240 ms 75.61.95.3
10 2026-08-26 02:38 639233078065410564
240 ms 75.61.95.3
9 2026-08-26 02:21 639233067787457832
3 ms 75.61.95.3
8 2026-08-26 02:04 639233057501801162
238 ms 75.61.95.3
7 2026-08-26 01:47 639233047089431703
248 ms 75.61.95.3
6 2026-08-26 01:30 639233036754790688
236 ms 75.61.95.3
5 2026-08-26 01:12 639233026412602472
243 ms 75.61.95.3
4 2026-08-26 00:55 639233016064066127
240 ms 75.61.95.3
3 2026-08-26 00:38 639233005922655772
244 ms 75.61.95.3
2 2026-08-26 00:21 639232995672256907
253 ms 75.61.95.3
1 2026-08-26 00:04 639232985300872416
247 ms 75.61.95.3