История сбоев Lob

1. 20 августа 2026 г. в 16:27 UTCinvestigating

   В настоящее время мы расследуем проблему, затрагивающую логины пользователей. Некоторые пользователи могут столкнуться с ошибкой при попытке войти в систему. Наша команда активно работает над выявлением первопричины и восстановлением нормальной функциональности.

2. 20 августа 2026 г. в 16:59 UTCinvestigating

   В настоящее время мы расследуем проблему, затрагивающую логины. Некоторые пользователи могут столкнуться с ошибкой при попытке войти в систему. Если вы пострадали, сброс пароля со страницы входа в систему восстановит доступ. Пожалуйста, выберите уникальный пароль, который вы не используете ни на одном другом сайте. Наша команда активно работает над восстановлением нормальной функциональности, и мы будем предоставлять обновления по мере поступления дополнительной информации.

Автоматический перевод официального обновления инцидента.

1. 12 августа 2026 г. в 17:52 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. 12 августа 2026 г. в 18:04 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. 12 августа 2026 г. в 19:18 UTCresolved

   This incident has been resolved.

Автоматический перевод официального обновления инцидента.

1. 12 августа 2026 г. в 14:22 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. 12 августа 2026 г. в 15:29 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. 12 августа 2026 г. в 18:05 UTCresolved

   This incident has been resolved.

1. 24 июля 2026 г. в 11:27 UTCmonitoring

   Проблема, вызывающая 500 ошибок в API лоб, была решена. Мы будем продолжать следить за системой, чтобы она оставалась стабильной.

2. 24 июля 2026 г. в 17:53 UTCresolved

   Проблема с ошибками Lob API решена.

Автоматический перевод официального обновления инцидента.

1. 10 июля 2026 г. в 17:36 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. 10 июля 2026 г. в 18:01 UTCmonitoring

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

3. 10 июля 2026 г. в 18:56 UTCresolved

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

1. 8 июля 2026 г. в 17:45 UTCinvestigating

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

2. 9 июля 2026 г. в 17:48 UTCresolved

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

1. 7 июля 2026 г. в 17:08 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. 7 июля 2026 г. в 17:08 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. 7 июля 2026 г. в 17:56 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. 3 июля 2026 г. в 05:48 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. 3 июля 2026 г. в 07:41 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. 30 июня 2026 г. в 03:11 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. 30 июня 2026 г. в 03:12 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. 18 июня 2026 г. в 22:33 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. 18 июня 2026 г. в 22:58 UTCresolved

   The issue has resolved and API endpoints resolve as expected.

1. 18 июня 2026 г. в 14:35 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. 18 июня 2026 г. в 18:57 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. 10 июня 2026 г. в 21:50 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. 10 июня 2026 г. в 22:00 UTCresolved

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

1. 20 мая 2026 г. в 16:38 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. 20 мая 2026 г. в 18:56 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. 29 мая 2026 г. в 20:30 UTCresolved

   We think the impact from the issue is over.

1. 5 мая 2026 г. в 17:34 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. 5 мая 2026 г. в 18:08 UTCmonitoring

   Issue seem to be resolved. We are monitoring.

3. 5 мая 2026 г. в 21:40 UTCresolved

   This incident has been resolved.

1. 23 апреля 2026 г. в 17:16 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. 23 апреля 2026 г. в 18:52 UTCresolved

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

1. 10 апреля 2026 г. в 22:32 UTCidentified

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

2. 10 апреля 2026 г. в 22:32 UTCresolved

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

1. 7 апреля 2026 г. в 17:32 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. 7 апреля 2026 г. в 18:46 UTCresolved

   All systems are operating normally. Issue is resolved.

1. 30 марта 2026 г. в 16:52 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. 30 марта 2026 г. в 18:51 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. 24 марта 2026 г. в 19:42 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. 25 марта 2026 г. в 13:28 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. 27 марта 2026 г. в 13:51 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!