Fastmail 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 fastmail.com. Compare the regional responses with the problem you see in Fastmail.
Find Fastmail 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
Fastmail separates webmail, mobile apps and mail-client connections. Its status page can help identify service problems, but individual delivery failures need the recipient and error context handled privately.
The checker above requests fastmail.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Fastmail action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Other checks in email & messaging: Tuta status check, mail.com status check, Mail.ru status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse messaging checks.
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Use the official help route for Fastmail; identify the specific product and action described on this page.
Open the website in your browser and compare it with the result above.
Open Fastmail 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.
Client/protocol, read/send/login step, error code and time; do not publish message bodies, recipient addresses or app passwords.
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 Fastmail.
These are troubleshooting comparisons, not claims that Fastmail is currently experiencing a particular incident.
Compare webmail access with the mail client or app that fails. Preserve unsent messages before restarting the client.
A bounced email, account-login error and failure to connect over IMAP or SMTP are different cases. Use the official support route with a redacted diagnostic rather than repeatedly sending the message.
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.
Repeat the same action in a second browser or on another available connection, keeping the item and account the same. Change one thing at a time so the result is comparable. Leave required workplace or school security controls in place.
Follow the website troubleshooting guide for connection checks. Preserve any unsent work before refreshing a form or changing a session.
Compare webmail access with the mail client or app that fails. Preserve unsent messages before restarting the client. A bounced email, account-login error and failure to connect over IMAP or SMTP are different cases. Use the official support route with a redacted diagnostic rather than repeatedly sending the message.
Use the community buttons on this page to share whether the service works for you. For help from Fastmail, use the official help/reporting resource linked above. Use the official help route for Fastmail; identify the specific product and action described on this page.
Fastmail separates webmail, mobile apps and mail-client connections. Its status page can help identify service problems, but individual delivery failures need the recipient and error context handled privately. Compare the original measurement time with the specific action that failed.
Client/protocol, read/send/login step, error code and time; do not publish message bodies, recipient addresses or app passwords.