Lob Outage History

Lob's rendering system experienced delays that caused proofs and thumbnails to load slower than expected in the dashboard. The issue affected users' ability to quickly view rendered content through the platform interface. The problem was identified and resolved after 4.2 hours of active monitoring and fixes.

Lob's rendering system experienced delays causing proofs and thumbnails to load slower than expected in the dashboard, with additional impacts to webhooks and API functionality. The issue affected the dashboard's visual content delivery for 1.6 hours before being fully resolved. The rendering system was restored to normal operational status without delays.

Lob's rendering system experienced delays causing proofs and thumbnails to load slower than expected in the dashboard. The issue affected users' ability to view rendered content in a timely manner through the platform interface. The rendering system was restored to full operational status after 1.6 hours, resolving all delays.

Lob's rendering system experienced delays causing proofs and thumbnails to load slower than expected in the dashboard and API. The issue affected the Dashboard and API components for 1.4 hours before being resolved. All systems returned to normal operation after the team identified and fixed the underlying problem.

Lob experienced a 2-hour service disruption where new users were unable to complete account sign-up through the Dashboard. The issue affected account registration functionality, preventing some users from creating new accounts. The problem was resolved after the team investigated and implemented a fix, with continued monitoring to ensure system stability.

Lob's data processing infrastructure fell behind, causing QR Code Engagement visualizations in the "Mail Analytics" and "Campaigns" dashboard sections to display incomplete data from March 16-24. While the dashboard reporting was affected, customers could still access their QR code scan data through direct API calls or existing webhook integrations, as no original scan data was lost. The issue was resolved through data backfilling completed on March 27, with additional monitoring improvements implemented to prevent future occurrences.