Is Expensify Down Right Now? Check if there is a current outage ongoing.

Some users are reporting an "Oops... an error has occurred" pop-up message when accessing certain pages of an Expensify account. These users should still be able to use Expensify by closing the pop-up. We are working on resolving this pop-up as soon as possible. We apologize for the inconvenience.

Thanks for your patience! Performance is back to normal.

We are currently investigating an issue where a "Your bank account credentials have expired. Please reconnect your account to assign cards." error shows when trying to assign company cards.

We are currently investigating an issue where a "Your bank account credentials have expired. Please reconnect your account to assign cards." error shows when trying to assign company cards.

Thanks for your patience! Performance is back to normal.

We are currently investigating an issue where a 500 error occurs when trying to reconnect a card connection to Expensify

We are currently investigating an issue where a 500 error occurs when trying to reconnect a card connection to Expensify

Currently, customers using Proof Point Hosted Email Security are unable to forward receipts to receipts@expensify.com. This is being caused by an issue on the Proof Point side. If you are an affected customer, please reach out to Proof Point for a resolution.

Currently, customers using Proof Point Hosted Email Security are unable to forward receipts to receipts@expensify.com. This is being caused by an issue on the Proof Point side. If you are an affected customer, please reach out to Proof Point for a resolution.

This incident has been resolved.

We’re aware of site instability issues and are working on resolving them as soon as possible. We apologize for the inconvenience.

We’re aware of site instability issues and are working on resolving them as soon as possible. We apologize for the inconvenience.

We are performing maintenance on the Expensify Travel back end, and have temporarily disabled online bookings. Existing reservations are unaffected. Please call +1 828 731 2962 to speak with an agent for new bookings.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating issues preventing the Expensify site from loading. Thanks for your patience!

This incident has been resolved.

We are continuing to monitor for any further issues.

Chase has released a fix for the issue of importing new cards into Expensify. Please attempt to reauthorize the Chase connection by following the steps below: 1. Log into Expensify as a domain admin and head to Settings > Domain > Company Cards. 2. Click the "Import New Cards" button and follow the prompts to enter your Chase credentials. When you're done, you will be redirected back to Expensify. 3. Once you're back in Expensify, please try to assign one of the missing cards and let Concierge know if you still can't.

Chase has confirmed an issue with their connection that is blocking new Chase cards from appearing in Expensify for assignment. Chase will require work on their end to fix the issue and has provided Expensify a resolution ETA of early 2025.

The ability to view card details for virtual Expensify Cards has been restored.

The ability to view Virtual Expensify Card details has been disabled temporarily. You can continue to use your Virtual Expensify Card details if they are saved or added to a third party wallet such as Apple Pay or Android Pay. We apologize for the inconvenience.

Thanks for your patience! Support message deliverability is back to normal.

Expensify is operating with reduced support staff over the holiday period. You may experience a delayed response, but we will reply as soon as possible. Happy holidays!

This incident has been resolved.

Most PDF generation is failing and we're looking into it. All other APIs and services are working.

This incident has now been resolved. The Expensify app will update automatically on your device with the fixed version, but you can also download the update now here: https://play.google.com/store/apps/details?id=org.me.mobiexpensifyg

Our engineering team is aware of an instant crash issue affecting the most recent Android Expensify Classic app version. We are working on fixing this for customers. In the meantime, you should be able to access the web version (www.expensify.com) from a browser. Apologies for the inconvenience!

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

We have fixed the issue and are monitoring the results.

We are currently investigating reports that the site is down. You may see a "500" error when loading expensify.com or new.expensify.com. Attempts to retrieve or post data to the API will also fail.

This incident has been resolved.

The issue has been identified and engineers are working on a fix

This incident has been resolved.

An issue with uploading receipts to expenses has been identified and our team is working on a fix.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

Expensify is back up. We are monitoring.

We are currently investigating this issue.

Thanks for your patience! Performance is back to normal.

A fix has been implemented and we are monitoring the status

We are currently investigating this issue

The underlying issue was identified and remedied, and the status is back to normal.

The site is back up. We are monitoring for now.

Users have reported being unable to sign into Expensify. We are currently investigating.

We identified the root cause of the issue and have released a fix.

We are continuing to investigate this issue.

Multiple customers have reported that their employees are unable to access Expensify when logging in via SAML. We are currently investigating.

This incident has been resolved.

We are currently experiencing temporary site instability and are investigating.

This incident has been resolved.

We are continuing to work on a fix for this issue.

Our corporate card connection is temporarily down, however we are implementing a fix. Should be resolved shortly.

This incident has been resolved.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We’re aware of site instability issues and are working on resolving them as soon as possible. We apologize for the inconvenience.

This incident has been resolved.

We are investigating an issue causing the expensify.com website to be down.

Capital One has confirmed the issue is resolved.

CapitalOne is investigating the connection issues.

We are currently investigating this issue between Expensify and CapitalOne.

Thanks for your patience! Performance is back to normal.

We’re aware of site instability issues and are working on resolving them as soon as possible. We apologize for the inconvenience.

This incident has been resolved.

The cause of SAML login issues has been identified. A fix is being implemented.

Some customers have reported issues logging into Expensify via SAML SSO. We are investigating the root cause.

This incident has been resolved.

A fix has been implemented to fix issues with display and editing.

We are continuing to work on a fix for this issue.

Unreported expenses are created with a $0 total and display issues are present. Our engineers have identified the issue and are working on a fix.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

We’re aware of site instability issues and are working on resolving them as soon as possible. We apologize for the inconvenience.

This incident has been resolved.

We are continuing to work on a fix for this issue.

We are currently experiencing a service outage. Our team has identified the root cause and is taking corrective action. We apologize for the inconvenience.

This incident has been resolved.

We’re updating our Chase integration, which may cause some Chase cards to stop importing temporarily. This should be resolved soon when our updates complete.

Some new and existing Chase banking connections are currently experiencing some issues. We're investigating the root cause.

This incident is resolved. All API-based exports, syncs, and approvals are functional.

We have identified the underlying issue in a certificate chain and are working to resolve it as our highest priority.

We are currently investigating an issue affecting our integration APIs. This will affect any connection to an accounting integration or third-party API-built connection, external reporting, as well as any custom approval rules Expensify maintains.

Thanks for your patience! Performance is back to normal.

We are currently aware of an issue where some users are encountering an error when attempting to send a message via New Expensify. Our team is actively investigating and expect to have this resolved shortly. If you require any assistance, please log into your account using Expensify Classic (www.expensify.com) and contact Concierge using the chat bubble or by email at concierge@expensify.com.

For a full postmortem regarding our recent site outages, please check out [this blog post](https://use.expensify.com/blog/autopsy-of-an-outage) by our founder and CEO, David Barrett. Thank you so much for your patience! Onward and upward.

This incident has been resolved.

We’re aware of site instability issues and are working on resolving them as soon as possible. We apologize for the inconvenience.

This incident has been resolved.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We’re aware of site instability issues and are working on resolving them as soon as possible. We apologize for the inconvenience.

We have resolved the instability at this time.

We’re aware of site instability issues and are working on resolving them as soon as possible. We apologize for the inconvenience.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We’re aware of site instability issues and are working on resolving them as soon as possible. We apologize for the inconvenience.

This incident has been resolved.

We’re aware of site instability issues and are working on resolving them as soon as possible. We apologize for the inconvenience.

This incident has been resolved.

We’re aware of site instability issues and are working on resolving them as soon as possible. We apologize for the inconvenience.

This incident has been resolved.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

We are currently experiencing a service outage. Our team has identified the root cause and is taking corrective action. We apologize for the inconvenience.

This incident has been resolved.

We are continuing to work on a fix for this issue.

We are currently experiencing a service outage. Our team has identified the root cause and is taking corrective action. We apologize for the inconvenience.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

The team is working to get this resolved as quickly as possible.

We are continuing to investigate this issue.

We are currently investigating the issue.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

The team is currently investigating the issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The team is currently investigating the issue.

This issue has been resolved. Thanks for your patience!

We are currently investigating the issue.

This incident has been resolved.

We’re aware of site instability issues, and we're actively working to resolve it.

This incident has been resolved and API requests are being accepted at this time.

We're continuing to monitor and please note that API requests are disabled at this time.

We’re aware of site instability issues. You may experience some intermittent instability, and we're actively working to resolve it.

The issue has now been resolved. All affected users should now be able to sync their policies and export reports to Sage Intacct.

We are currently investigation an issue between Expensify and Sage Intacct where users are receiving only an error stating "Session Initialization Error" when syncing Expensify policies or exporting reports to Sage Intacct.