Instagram help and reporting
Use Instagram's technical-problem/help route; content or account appeals are separate.
Live Domain Check
Run a live reachability check for instagram.com. Compare the regional responses with the problem you see in Instagram.
Find Instagram help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Instagram feed, Stories, messaging, uploads and login can fail independently.
The checker above requests instagram.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Instagram action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Use Instagram's technical-problem/help route; content or account appeals are separate.
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.
Use Instagram's technical-problem/help route; content or account appeals are separate.
Open Instagram 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.
Feature, profile/post reference privately, app version, phone OS, error and timestamp.
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 Instagram.
These are troubleshooting comparisons, not claims that Instagram is currently experiencing a particular incident.
Compare a public profile in a browser with the same feature in your app; keep an unsent post or Story draft.
Use Instagram's Help Center for technical reporting; account suspension or a single removed post is not established by a website outage check.
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 Instagram seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open instagram.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 Instagram 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 Instagram support.
Run the instagram.com check and compare its original timestamps and responses with your actual error. Instagram feed, Stories, messaging, uploads and login can fail independently.
Use the official help/reporting resource linked above. Use Instagram's technical-problem/help route; content or account appeals are separate.
Compare a public profile in a browser with the same feature in your app; keep an unsent post or Story draft. Use Instagram's Help Center for technical reporting; account suspension or a single removed post is not established by a website outage check.
Feature, profile/post reference privately, app version, phone OS, error and timestamp.