Bluesky help and reporting
Bluesky's official support page lists support@bsky.app; the social app is bsky.app.
Live Domain Check
Run a live reachability check for bsky.app. Compare the regional responses with the problem you see in Bluesky.
Find Bluesky 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
Bluesky's social app uses bsky.app. The similarly named bluesky.app is a different website and should not be used to judge Bluesky availability.
The checker above requests bsky.app from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Bluesky action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse social app checks.
Bluesky's official support page lists support@bsky.app; the social app is bsky.app.
Open the website in your browser and compare it with the result above.
Bluesky’s official support page lists support@bsky.app for help requests. Describe the actual app problem rather than the similarly named bluesky.app website.
Handle, affected feed/post action, client/version and timestamp; never include an app password or recovery details.
The correct social-app entrypoint is bsky.app.
These are troubleshooting comparisons, not claims that Bluesky is currently experiencing a particular incident.
Compare timeline loading with opening one public profile or post on bsky.app.
If publishing fails, check whether the post appeared before sending it again; use Bluesky's official support page for account or technical issues.
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 Bluesky seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open bsky.app 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 Bluesky 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 Bluesky support.
Run the bsky.app check and compare its original timestamps and responses with your actual error. Bluesky's social app uses bsky.app. The similarly named bluesky.app is a different website and should not be used to judge Bluesky availability.
Use the community buttons on this page to share whether the service works for you. For help from Bluesky, use the official help/reporting resource linked above. Bluesky's official support page lists support@bsky.app; the social app is bsky.app.
Compare timeline loading with opening one public profile or post on bsky.app. If publishing fails, check whether the post appeared before sending it again; use Bluesky's official support page for account or technical issues.
Handle, affected feed/post action, client/version and timestamp; never include an app password or recovery details.