Meta Status service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Run a live reachability check for metastatus.com. Compare the regional responses with the problem you see in Meta Status.
Find Meta Status help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Meta Status reports named business and developer products; it is not a complete dashboard for every Facebook, Instagram or WhatsApp consumer feature.
The checker above requests metastatus.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Meta Status action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
If more than one Meta service is failing for you, compare its own observations rather than extending this result to every app: Facebook status check, Instagram status check, WhatsApp status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse infrastructure checks.
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Read the named business/developer component; this is not a complete consumer-app status dashboard.
Open the website in your browser and compare it with the result above.
Open Meta Status help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Status component/incident URL, affected app/API feature, error and UTC time.
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 Meta Status.
These are troubleshooting comparisons, not claims that Meta Status is currently experiencing a particular incident.
Select the actual product/component and compare the incident description with the action that failed.
For a consumer app issue outside that scope, use that app's own Help Center and a direct app test.
A 403 Forbidden or 429 Too Many Requests 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 Meta Status seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open metastatus.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 Meta Status issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Meta Status support.
Run the metastatus.com check and compare its original timestamps and responses with your actual error. Meta Status reports named business and developer products; it is not a complete dashboard for every Facebook, Instagram or WhatsApp consumer feature.
Use the community buttons on this page to share whether the service works for you. For help from Meta Status, use the official help/reporting resource linked above. Read the named business/developer component; this is not a complete consumer-app status dashboard.
Select the actual product/component and compare the incident description with the action that failed. For a consumer app issue outside that scope, use that app's own Help Center and a direct app test.
Status component/incident URL, affected app/API feature, error and UTC time.