Poe help and reporting
Include the affected bot and account/usage error.
Live Domain Check
Run a live reachability check for poe.com. Compare the regional responses with the problem you see in Poe.
Find Poe 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
Poe bot responses, account access and a specific bot's availability need different checks.
The checker above requests poe.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Poe action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse AI service checks.
Include the affected bot and account/usage error.
Open the website in your browser and compare it with the result above.
Open Poe 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.
Bot, chat feature, app/browser, usage/error message and time without private prompts.
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 Poe.
These are troubleshooting comparisons, not claims that Poe is currently experiencing a particular incident.
Compare a short request to another available bot with the failing conversation and preserve any partial response.
Check Poe Help and the account's usage state; a bot-specific error does not establish a platform outage.
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 Poe seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open poe.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 Poe 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 Poe support.
Run the poe.com check and compare its original timestamps and responses with your actual error. Poe bot responses, account access and a specific bot's availability need different checks.
Use the community buttons on this page to share whether the service works for you. For help from Poe, use the official help/reporting resource linked above. Include the affected bot and account/usage error.
Compare a short request to another available bot with the failing conversation and preserve any partial response. Check Poe Help and the account's usage state; a bot-specific error does not establish a platform outage.
Bot, chat feature, app/browser, usage/error message and time without private prompts.