Historial de interrupciones de Certify

1. 26 de octubre de 2026 a las 19:59 UTCinvestigating

   Debido a la migración retardada del centro de datos con nuestro proveedor SFTP, ShareTru, el host sftp.certify.com está actualmente fuera de línea. Cualquier transferencia automatizada de datos, como sincronización de usuarios, sincronizaciones de proyectos o exportaciones de informes de gastos, el aprovechamiento de sftp.certify.com no funcionará como programado hasta que el servicio sea devuelto en línea por nuestro proveedor. Tenga en cuenta que todas las transferencias de datos de la tarjeta de crédito corporativa han sido migradas a un nuevo servicio SFTP en sftp.expense.certify.com, y no son impactadas por este problema. Además, algunas organizaciones pueden aprovechar el nuevo servicio SFTP (sftp.expense.certify.com) para la transferencia de datos. sftp.expense.certify.com no está afectado por este problema.

Traducido automáticamente desde la actualización oficial del incidente.

1. 29 de mayo de 2026 a las 15:41 UTCinvestigating

   We are currently investigating an issue impacting receipt OCR processing times.

2. 29 de mayo de 2026 a las 17:14 UTCresolved

   The issue has been resolved and OCR receipt processing has returned to normal. Thank you for your patience while we addressed this issue.

1. 8 de mayo de 2026 a las 0:04 UTCinvestigating

   We are currently investigating an issue which is preventing users from logging in to the application.

2. 8 de mayo de 2026 a las 0:18 UTCresolved

   The issue has been resolved and users are now able to log in.

1. 22 de diciembre de 2025 a las 0:54 UTCinvestigating

   We are currently investigating an issue which is preventing users from logging in to the Emburse Professional and Certify AP applications.

2. 22 de diciembre de 2025 a las 1:25 UTCresolved

   We have identified and corrected the authentication issue and all users are now able to log in.

1. 30 de octubre de 2025 a las 13:13 UTCinvestigating

   We are aware of and investigating an issue which is preventing some corporate/commercial credit card files from importing transactions to user Wallets. We will provide an update on our investigation no later than 1:00pm US Eastern time today.

2. 30 de octubre de 2025 a las 17:35 UTCidentified

   We have identified the issue and continue to investigate the root cause. We will provide additional updates as soon as the impacted credit card files resume processing.

3. 30 de octubre de 2025 a las 20:58 UTCmonitoring

   This issue preventing credit card files from importing transactions has been resolved and new credit card files are processing. We are working to process the backlog of files which failed to import transactions during the incident and will provide a final update once all files have been processed.

4. 31 de octubre de 2025 a las 22:06 UTCmonitoring

   New commercial credit card files continue to import successfully. We are continuing to process the backlog of credit card files which failed to import between October 24th and October 30th. Work to process the backlog will continue through the weekend and we will provide further updates as soon as the backlog has been fully processed.

5. 3 de noviembre de 2025 a las 16:52 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 3 de noviembre de 2025 a las 16:55 UTCresolved

   All pending credit card files have been processed and transactions have been imported to users' Wallets. All new credit card files continue to import successfully and the core issue has been resolved. We thank you for your patience while we addressed this matter.

1. 22 de agosto de 2025 a las 14:49 UTCinvestigating

   We are aware of an issue impacting email notifications and are investigating. Please note that email notifications for password recovery and multi-factor authentication remain operational.

2. 22 de agosto de 2025 a las 16:52 UTCidentified

   This issue impacting email notifications has been identified and a fix is being deployed. We will notify all customers once the issue has been fully resolved.

3. 22 de agosto de 2025 a las 18:45 UTCresolved

   The fix has been deployed and should no longer be impacting users. We will continue to monitor and provide additional updates if necessary.

1. 24 de abril de 2025 a las 13:59 UTCidentified

   We have identified an issue which may impact a customer's custom export file when attempting to manually download the file from the Accounts Payable Report. A fix for this issue is currently in testing and we anticipate this matter will be resolved by the end of the day, April 24th.

2. 25 de abril de 2025 a las 12:48 UTCresolved

   This issue has been resolved and impacted customers may resume downloading export files from the Accounts Payable Report. Thank you for your patience.

1. 15 de abril de 2025 a las 15:22 UTCinvestigating

   We are currently investigating an issue which is preventing some users from emailing receipts to their Wallets. While we investigate this issue, users are encouraged to leverage direct receipt upload or use our mobile app to add receipts to their Wallets.

2. 15 de abril de 2025 a las 15:49 UTCmonitoring

   We've identified and corrected the issue preventing receipts from importing via email. Receipts emailed during the incident will import within the next 30 minutes as we work to clear the backlog of pending receipt imports.

3. 15 de abril de 2025 a las 15:57 UTCresolved

   All receipts emailed during the incident have been successfully imported to the impacted users' Wallets. We apologize for this inconvenience and thank you for your patience while we addressed this issue.

1. 11 de marzo de 2025 a las 16:39 UTCinvestigating

   We are currently investigating an issue which is delaying the import of receipts emailed to [email protected]. In the interim, customers are encouraged to upload the receipts directly to their Wallet via desktop upload, or use the Mobile App.

2. 11 de marzo de 2025 a las 17:23 UTCmonitoring

   The issue impacting receipts emailed to [email protected] has been remediated and we are continuing to monitor the situation closely

3. 11 de marzo de 2025 a las 20:19 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 11 de marzo de 2025 a las 20:20 UTCresolved

   This issue has been resolved and all emailed receipt functionality has resumed normal processing.

1. 21 de febrero de 2025 a las 12:20 UTCinvestigating

   We are currently investigating an issue which is preventing all users from logging in to the Emburse Professional application. We will provide updates as soon as they become available. We apologize for this inconvenience.

2. 21 de febrero de 2025 a las 13:00 UTCmonitoring

   The issue has been remediated and users are able to log in. We are continuing to monitor the situation.

3. 21 de febrero de 2025 a las 13:36 UTCresolved

   This incident has been resolved. All users can access the application without issue.

1. 19 de noviembre de 2024 a las 15:47 UTCinvestigating

   End users submitting out-of-pocket expenses in a non-native currency are currently unable to retrieve FX rates. We are working diligently with our FX provider to restore this service as quickly as possible. Please note that any expenses incurred in a non-native currency and imported from an integrated credit card program will not be affected

2. 19 de noviembre de 2024 a las 15:48 UTCidentified

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

3. 19 de noviembre de 2024 a las 17:14 UTCresolved

   Our FX provider has restored our service and expense conversions are functioning as expected.

1. 19 de julio de 2024 a las 15:37 UTCidentified

   We are continuing to assess the impact caused by a defect in a third party cybersecurity service, which is impacting applications worldwide. As a result, Certify users may be experiencing increased latency while navigating our application.

2. 20 de julio de 2024 a las 13:06 UTCmonitoring

   The incident has been resolved, however we are continuing to monitor closely.

3. 22 de julio de 2024 a las 13:33 UTCresolved

   This incident has been resolved.

1. 31 de mayo de 2024 a las 18:58 UTCinvestigating

   Emburse are aware of a present Certify Expense site outage and are investigating.

2. 31 de mayo de 2024 a las 19:18 UTCidentified

   The issue has been identified and we are working on a resolution.

3. 31 de mayo de 2024 a las 20:38 UTCmonitoring

   A fix has been applied, and we are monitoring results.

4. 31 de mayo de 2024 a las 20:39 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 31 de mayo de 2024 a las 22:14 UTCresolved

   The incident has been resolved. Thank you for your patience.

1. 7 de septiembre de 2023 a las 14:46 UTCinvestigating

   We are investigating the issue.

2. 7 de septiembre de 2023 a las 19:32 UTCinvestigating

   We are continuing to investigate this issue.

3. 7 de septiembre de 2023 a las 19:32 UTCresolved

   This incident has been resolved.

1. 7 de agosto de 2023 a las 16:14 UTCinvestigating

   We are currently investigating this issue.

2. 7 de agosto de 2023 a las 21:33 UTCresolved

   This incident has been resolved.

1. 7 de julio de 2023 a las 20:12 UTCinvestigating

   We are currently investigating an issue which is preventing some users from accessing Certify.

2. 10 de julio de 2023 a las 14:12 UTCresolved

   This incident is resolved.

1. 7 de julio de 2023 a las 20:07 UTCinvestigating

   We are currently investigating this issue.

2. 7 de julio de 2023 a las 20:09 UTCinvestigating

   We are continuing to investigate this issue.

3. 7 de julio de 2023 a las 20:12 UTCresolved

   This incident has been resolved.

1. 7 de junio de 2023 a las 21:00 UTCinvestigating

   We are currently investigating this issue.

2. 7 de junio de 2023 a las 21:45 UTCinvestigating

   We are continuing to investigate this issue.

3. 7 de junio de 2023 a las 21:50 UTCresolved

   This incident has been resolved.

1. 30 de mayo de 2023 a las 17:11 UTCidentified

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

2. 30 de mayo de 2023 a las 17:56 UTCresolved

   The incident has been resolved.

1. 22 de abril de 2023 a las 14:06 UTCinvestigating

   We are currently investigating this issue.

2. 22 de abril de 2023 a las 18:45 UTCinvestigating

   We are continuing to investigate this issue.

3. 22 de abril de 2023 a las 18:46 UTCresolved

   This incident has been resolved.