Historial de interrupciones de Lob

1. August 20, 2026 at 4:27 PM UTCinvestigating

   Actualmente estamos investigando un problema que afecta a los usuarios. Algunos usuarios pueden encontrar un error al intentar iniciar sesión. Nuestro equipo está trabajando activamente para identificar la causa raíz y restaurar la funcionalidad normal.

2. August 20, 2026 at 4:59 PM UTCinvestigating

   Actualmente estamos investigando un problema que afecta a los logins. Algunos usuarios pueden encontrar un error al intentar iniciar sesión. Si usted está afectado, restablecer su contraseña de la página de inicio de sesión restaurará el acceso. Por favor, elija una contraseña única que no utilice en ningún otro sitio. Nuestro equipo está trabajando activamente para restaurar la funcionalidad normal, y proporcionaremos actualizaciones a medida que se disponga de más información.

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

1. August 12, 2026 at 5:52 PM UTCinvestigating

   We are currently seeing an elevated error rate on the /v1/bulk/us_verifications endpoint. Our team is actively investigating and we will post an update as soon as we have more information.

2. August 12, 2026 at 6:04 PM UTCmonitoring

   We applied a patch and the elevated error rate on the /v1/bulk/us_verifications endpoint has resolved. Our team is continuing to actively monitor.

3. August 12, 2026 at 7:18 PM UTCresolved

   This incident has been resolved.

1. August 12, 2026 at 2:22 PM UTCidentified

   We are currently experiencing an issue affecting ingestion of USPS tracking events. All tracking events will be delayed until this issue is resolved and the backlog of data is processed. Our team is aware of the issue and actively implementing a fix.

2. August 12, 2026 at 3:29 PM UTCmonitoring

   We've resolved the issue that prevented ingestion of USPS tracking events. USPS has sent us a backfill file, and we are currently processing the skipped events. Customers should see all tracking events caught up by the end of business today.

3. August 12, 2026 at 6:05 PM UTCresolved

   This incident has been resolved.

1. July 24, 2026 at 11:27 AM UTCmonitoring

   Se ha resuelto el problema que causa 500 errores en la API de laboratorio. Seguiremos vigilando el sistema para asegurar que siga estable.

2. July 24, 2026 at 5:53 PM UTCresolved

   El problema que causa errores La API de Lob se ha resuelto.

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

1. July 10, 2026 at 5:36 PM UTCinvestigating

   We're experiencing a temporary issue across our system due to an external service outage. We're actively working on resolving this issue

2. July 10, 2026 at 6:01 PM UTCmonitoring

   The external service is gradually recovering and we're now actively monitoring the recovery

3. July 10, 2026 at 6:56 PM UTCresolved

   The external service has been resolved and all our systems are operational

1. July 8, 2026 at 5:45 PM UTCinvestigating

   We are currently experiencing an issue affecting some export creation and are actively working to resolve it.

2. July 9, 2026 at 5:48 PM UTCresolved

   The issue affecting some export requests has been resolved, and processing has returned to normal.

1. July 7, 2026 at 5:08 PM UTCinvestigating

   We are currently investigating an issue affecting HTML templates. Users may encounter errors when proofing HTML templates or when sending mailpieces that use an HTML creative. Our team is actively working to identify the root cause and restore normal functionality. We will provide updates as more information becomes available.

1. July 7, 2026 at 5:08 PM UTCinvestigating

   We are currently investigating an issue affecting HTML templates. Users may encounter errors when proofing HTML templates or when sending mailpieces that use an HTML creative. Our team is actively working to identify the root cause and restore normal functionality. We will provide updates as more information becomes available.

2. July 7, 2026 at 5:56 PM UTCresolved

   The issue causing errors in proofing HTML has been resolved, and processing has returned to normal. We will continue to monitor the system to ensure it remains stable.

1. July 3, 2026 at 5:48 AM UTCinvestigating

   We are currently experiencing elevated rendering times, which may cause delays in processing some requests. Our team is investigating the issue and will provide updates as more information becomes available.

2. July 3, 2026 at 7:41 AM UTCresolved

   The issue causing elevated rendering times has been resolved, and processing has returned to normal. We will continue to monitor the system to ensure it remains stable.

1. June 30, 2026 at 3:11 AM UTCidentified

   We experienced a temporary issue with our international address verification service this evening that caused some requests to fail. The issue has been resolved and the service is operating normally.

2. June 30, 2026 at 3:12 AM UTCresolved

   We experienced a temporary issue with our international address verification service this evening that caused some requests to fail. The issue has been resolved and the service is operating normally

1. June 18, 2026 at 10:33 PM UTCinvestigating

   Our endpoint/service is currently experiencing an outage. As a result, users may be experiencing errors, degraded performance, or inability to access certain features. Our team has identified the issue and is actively investigating the root cause.

2. June 18, 2026 at 10:58 PM UTCresolved

   The issue has resolved and API endpoints resolve as expected.

1. June 18, 2026 at 2:35 PM UTCidentified

   We identified an issue causing some API endpoints to incorrectly return 401 Unauthorized responses. This has been resolved and all endpoints are functioning as expected. impact from the issue is over.

2. June 18, 2026 at 6:57 PM UTCresolved

   We identified an issue causing some API endpoints to incorrectly return 401 Unauthorized responses. This has been resolved and all endpoints are functioning as expected.

1. June 10, 2026 at 9:50 PM UTCmonitoring

   Customers may have experienced a temporary outage related to creating letters and obtaining information about previously created letters.  The root cause has been identified and the issue resolved.

2. June 10, 2026 at 10:00 PM UTCresolved

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

1. May 20, 2026 at 4:38 PM UTCinvestigating

   We are aware of an issue affecting customers attempting to verify bank accounts with micro deposits through the Lob dashboard or API. We are investigating and working on a resolution. We apologize for the inconvenience and will provide an update as soon as we have more information.

2. May 20, 2026 at 6:56 PM UTCmonitoring

   We have implemented a mitigation that restores bank account verification for sending Checks. New bank account verification should now work as expected. If you created a bank account within the last 7 days and are still unable to complete verification, please reach out to our support team at [email protected] or visit https://help.lob.com/resources/getting-support for additional contact options. We will be providing an update in the coming week about longer-term changes to bank account verification, before they take effect. We apologize for any disruption this caused.

3. May 29, 2026 at 8:30 PM UTCresolved

   We think the impact from the issue is over.

1. May 5, 2026 at 5:34 PM UTCinvestigating

   Our rendering system is experiencing delays so proofs and thumbnails may lake longer than expected to appear in the dashboard. We have identified the issue and are actively working on a fix

2. May 5, 2026 at 6:08 PM UTCmonitoring

   Issue seem to be resolved. We are monitoring.

3. May 5, 2026 at 9:40 PM UTCresolved

   This incident has been resolved.

1. April 23, 2026 at 5:16 PM UTCinvestigating

   Our rendering system is experiencing delays so proofs and thumbnails may lake longer than expected to appear in the dashboard. We have identified the issue and are actively working on a fix

2. April 23, 2026 at 6:52 PM UTCresolved

   Our rendering system is back to being fully operational without any delays. Issue is resolved.

1. April 10, 2026 at 10:32 PM UTCidentified

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

2. April 10, 2026 at 10:32 PM UTCresolved

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

1. April 7, 2026 at 5:32 PM UTCinvestigating

   Our rendering system is experiencing delays so proofs and thumbnails may lake longer than expected to appear in the dashboard, we have identified the issue and are actively fixing it

2. April 7, 2026 at 6:46 PM UTCresolved

   All systems are operating normally. Issue is resolved.

1. March 30, 2026 at 4:52 PM UTCinvestigating

   We are currently experiencing an issue affecting new account registration on the Dashboard. Some users may be unable to create a new account at this time. Our team is aware of the issue and is actively investigating and implementing a fix.

2. March 30, 2026 at 6:51 PM UTCresolved

   The issue affecting new account registrations on the Dashboard has been resolved. Users should now be able to successfully create new accounts. We will continue to monitor the system to ensure stability.

1. March 24, 2026 at 7:42 PM UTCidentified

   Our data processing infrastructure is running behind which is causing inaccuracies in the reporting tools. Lob's QR Code Engagement visualizations in the "Mail Analytics" and "Campaigns" sections of the dashboard are missing some data that was created between Monday, March 16 and today, March 24. Only the data processing system was impacted - no original QR code scan data has been lost. Customers can still access this data if they make a GET call to Lob's APIs, or if they have webhook ingestion already set up. We've identified the issue and are actively backfilling the QR Code Engagement Chart with the missing records. We anticipate completing this backfill no later than tomorrow morning - Wednesday, March 25.

2. March 25, 2026 at 1:28 PM UTCidentified

   Our data processing infrastructure is running behind which is causing inaccuracies in the reporting tools. Lob's QR Code Engagement visualizations in the "Mail Analytics" and "Campaigns" sections of the dashboard are missing some data that was created between Monday, March 16 and Tuesday, March 24. Only the data processing system was impacted - no original QR code scan data has been lost. Customers can still access this data if they make a GET call to Lob's APIs, or if they have webhook ingestion already set up. We've identified the issue and new scan events are now visible in the QR Code Engagement Chart. We are actively backfilling scans from the outage period that are missing from the chart. We've updated our anticipated date of resolution for completing this backfill - this should be complete no later than the evening of Friday, March 27.

3. March 27, 2026 at 1:51 PM UTCresolved

   Backfills are complete. Additionally, Lob's engineering team has put improvements in place to prevent similar issues in the future, and updated our monitoring and alerting to catch similar issues if they do recur. Please reach out to [email protected] if you are still experiencing issues!