Facebook help and reporting
Meta business-service status is not a complete consumer Facebook outage dashboard.
Live Domain Check
Run a live reachability check for facebook.com. Compare the regional responses with the problem you see in Facebook.
Find Facebook help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Facebook sign-in, feed loading, posting and account restrictions need different evidence.
The checker above requests facebook.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Facebook action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Meta business-service status is not a complete consumer Facebook outage dashboard.
Compare the website entrypoint with your browser or app. This website link is separate from a provider incident dashboard.
No separate incident dashboard is linked here. Use the official product help and any current announcements it links to; this does not mean that no outage is possible.
Meta business-service status is not a complete consumer Facebook outage dashboard.
Open Facebook help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Affected feature, page/post reference, app/browser version and error time with personal details removed.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Facebook.
These are troubleshooting comparisons, not claims that Facebook is currently experiencing a particular incident.
Compare a public page with your signed-in feed and note whether one post or the whole interface fails.
Use Facebook Help for technical reports and account recovery; do not infer a consumer outage from a Meta business-only status component.
A 403 or 429 means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Facebook seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open facebook.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Facebook issue.
Compare Wi-Fi and mobile data only where you are permitted to do so. Keep required VPN, proxy and security controls in place, and record which network fails.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Facebook support.
Run the facebook.com check and compare its original timestamps and responses with your actual error. Facebook sign-in, feed loading, posting and account restrictions need different evidence.
Use the official help/reporting resource linked above. Meta business-service status is not a complete consumer Facebook outage dashboard.
Compare a public page with your signed-in feed and note whether one post or the whole interface fails. Use Facebook Help for technical reports and account recovery; do not infer a consumer outage from a Meta business-only status component.
Affected feature, page/post reference, app/browser version and error time with personal details removed.