Is familysearch.org down or not working?

What happened to familysearch.org, why did the website go down and not work? Here you can see who else is having the same problem with familysearch.org, as well as possible solutions. According to our statistics, the following most often do not work: Website, Login, Account, Mobile App.

Current status: No failures

At the moment, according to our data, familysearch.org is working fine, but single failures are possible. If familysearch.org does not work for you, then report your problem and write a comment.
Add comment

What to do if the site familysearch.org is not available? Try our guide.

familysearch.org outage reports in the last 24 hours

familysearch.org - error and failure reports, troubleshooting methods

Leave your comment describing the failure and share with other users how to solve the problem.
  • No registration required.
  • Messages with obscene language and insults, as well as breaking the law, are not allowed to be published.
  • Active links in the text of the message are not published, but displayed in plain text.
  • It is forbidden to post your own and other people's personal data: addresses, phone numbers, emails, accounts in instant messengers, etc.
rob townend - 4 days ago - Nov 17, 2024 1:51 PM
search not working properly - does not load results onto webpage even when logged in

Technical information

Main page title:
FamilySearch.org
Main page description:
Discover your family history. Explore the world’s largest collection of free family trees, genealogy records and resources.
Protocol:
https
Status code:
200
Page size:
7.6 KB
Response time:
2.379sec.
IP:
3.212.42.78
Response headers:
content-type: text/html; charset=utf-8
connection: close
date: Mon, 30 Sep 2024 21:12:47 GMT
server: Cowboy
report-to: {"group":"heroku-nel","max_age":3600,"endpoints":[{"url":"https://nel.heroku.com/reports?ts=1727730767&sid=929419e7-33ea-4e2f-85f0-7d8b7cd5cbd6&s=ivf%2Bc297coTEgLyrVR%2FPeEsMioBxKlMG36JzikajlMU%3D"}]}
reporting-endpoints: heroku-nel=https://nel.heroku.com/reports?ts=1727730767&sid=929419e7-33ea-4e2f-85f0-7d8b7cd5cbd6&s=ivf%2Bc297coTEgLyrVR%2FPeEsMioBxKlMG36JzikajlMU%3D
nel: {"report_to":"heroku-nel","max_age":3600,"success_fraction":0.005,"failure_fraction":0.05,"response_headers":["Via"]}
x-request-id: bcc6cab2-af37-4aab-bd3c-7efe2a28b084
link: <https://edge.fscdn.org/>; rel=preconnect, <https://foundry.familysearch.org/>; rel=preconnect; crossorigin, <https://sdk.split.io/>; rel=preconnect, <https://auth.split.io/>; rel=preconnect; crossorigin, <https://consent.trustarc.com/>; rel=preconnect, <https://assets.ldscdn.org/>; rel=preconnect, <https://foundry.familysearch.org/Foundry/v1/HeritageHeadings:Sans:Normal:500@en-Latn/css>; rel=preload; as=style, <https://foundry.familysearch.org/Foundry/v1/HeritageBody:Sans:Normal:400@en-Latn/css>; rel=preload; as=style, <https://foundry.familysearch.org/Foundry/v1/HeritageBody:Sans:Normal:700@en-Latn/css>; rel=preload; as=style, <https://foundry.familysearch.org/Foundry/v1/HeritageBody:Sans:Italic:400@en-Latn/css>; rel=preload; as=style, <https://foundry.familysearch.org/Foundry/v1/HeritageBody:Sans:Italic:700@en-Latn/css>; rel=preload; as=style
etag: W/"1dfb-EjYNd/HEl8XN6iKWH9+b4I5TXvw"
vary: Accept-Encoding
via: 1.1 vegur, 1.1 3adffce7dd03a16d055927ad5fa7671a.cloudfront.net (CloudFront)
content-security-policy: frame-ancestors 'self' https://*.familysearch.org https://*.familysearch.psdops.com https://*.church.brightspot.cloud
x-frame-options: SAMEORIGIN
set-cookie: fs_anid=65f16567-7467-4e97-b4d5-5053adddac48; Max-Age=31536; Path=/; Expires=Tue, 01 Oct 2024 05:58:23 GMT,fsgeo=5.45.71.54; Domain=www.familysearch.org; Path=/; Secure,fs_experiments=u%3D-anon-%2Ca%3Dshared-ui%2Cs%3D97f70402349e88f417727cc47acbde8e%2Cv%3D11111011110000000000000000011101000100111001001100110111110000010010111111111011111111101100000100111011111100001100101111110011110000000%2Cb%3D8%26a%3Dhome-react%2Cs%3D6a0acd78f639becd5469402462e78c9a%2Cv%3D0000111011010000%2Cb%3D9; Path=/; Expires=Tue, 30 Sep 2025 21:12:47 GMT; Secure; SameSite=Lax,fs_kill_switch=; Path=/; Expires=Thu, 01 Jan 1970 00:00:00 GMT,fslanguage=en; Domain=.familysearch.org; Path=/,visid_incap_2852034=TWh5kFvKS1u/hce59xvt4k0U+2YAAAAAQUIPAAAAAACmpQfW4hhTcuOp8GibbhTk; expires=Tue, 30 Sep 2025 15:34:17 GMT; HttpOnly; path=/; Domain=.familysearch.org,nlbi_2852034=y0gLN1ryPlX4P+hCFzy7qAAAAAB+GgfuuIkO3A6KZZWL+y7C; HttpOnly; path=/; Domain=.familysearch.org,incap_ses_1043_2852034=wufoD2MCYgXEYsCZHnt5Dk4U+2YAAAAAz6HSxJy0WIL5kWrjVess6Q==; path=/; Domain=.familysearch.org
x-cache: Miss from cloudfront
x-amz-cf-pop: FRA56-P10
x-amz-cf-id: pStvs-u1IP6Gja6ysO-zwXSGFGTBJp74wBwbaKBX4skkOS_rJpGMag==
x-cdn: Imperva
transfer-encoding: chunked
x-iinfo: 17-52218878-52218895 NNNN CT(116 117 0) RT(1727730765843 120) q(0 0 3 1) r(4 5) U24
DNS records:
A address3.93.111.247
ttl60
A address3.212.42.78
ttl60
MX exchangefamilysearch-org.mail.protection.outlook.com
priority10
NS valuens-1481.awsdns-57.org
NS valuens-757.awsdns-30.net
NS valuens-1938.awsdns-50.co.uk
NS valuens-285.awsdns-35.com
TXT entriesgoogle-site-verification=6KKVYhlRvHTViW2RA7A5__ZXTikT7uAf03ePMNessFo
TXT entriesv=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all
TXT entriesDynatrace-site-verification=01fe5b77-fca9-4449-ac01-bd46d84de1b9__uup9r4kddouuo79lb1gf954rr8
TXT entries1rn6c9nh4619f7grv7nr8hyz4mty5qg5
TXT entriesMS=ms62285318
TXT entriesatlassian-domain-verification=3Dqf1aq/7c1KdbsLIafbqX74I0vcW6pAbM0v6ocK8bw9/yvuWn1YDw7Kak9HK9s2
TXT entriesZOOM_verify_lMC9_ljtQY2vqNUrobjHSw
TXT entriestraction-guest=b60a6d25-4e72-413e-87e1-d2da15f38c18
TXT entriescisco-ci-domain-verification=5ab7b8e0f9d18911db10df28bc2e1b139c837cc7538703556f0d7e61f87f3784
TXT entriesValidity-Domain-Verification=Jn4wYYH/SK3Ikm59OAvLY6qpYme=
TXT entriesdropbox-domain-verification=e4s77r1l6tcc
TXT entriesgoogle-site-verification=Oshp3Lx_xob63dlDgFOHCXmtS1OVftgM3cdKjWZ3Hlc
SOA nsnamens-285.awsdns-35.com
hostmasterawsdns-hostmaster.amazon.com
serial1
refresh7200
retry900
expire1209600
minttl86400

How to solve problems with familysearch.org

Errors on the familysearch.org website can be either on the server side or on your side (client side). If there is practically nothing to be done about errors on the server side (it remains only to wait for the site to work again), then with errors on the client side it is possible to solve the problem with the availability of familysearch.org on your own.