Resolved after 9 minutes, affecting AM1 - Print Console, on August 11, 2025.
**AM1 – Printing Delay** **Date of Incident:** Aug 11, 12:43 to 12:52 PDT **Region:** AM1 **Status:** RESOLVED **Summary** On August 11 at 12:43 PDT, some users in the AM1 region experienced printing delays. A sudden spike in print jobs within a short time frame impacted performance for approximately 10 minutes. **What Happened** An unexpected surge in print job activity temporarily slowed printing services for some users in the AM1 region. **Resolution** The team quickly identified the surge in print volume and took immediate action to stabilize the service by reallocating system resources and processing the backlog of queued jobs. Normal printing performance was fully restored by 12:52 PDT. **Next Steps** * Increase proactive monitoring to detect similar issues earlier. * Implement preventive measures later this year to identify and address such scenarios before they affect performance.
Affected components
Update timeline
- resolved Aug 13, 2025, 03:27 PM UTC
Between 12:43 and 12:52 PDT, some users in the AM1 region experienced slower printing performance. This was caused by a high volume of print jobs in a very short period, which temporarily affected system performance. The issue was quickly identified and resolved, and all services were fully operational by 12:52 PDT. We apologize for the inconvenience and appreciate your patience.
- postmortem Aug 13, 2025, 03:28 PM UTC
**AM1 – Printing Delay** **Date of Incident:** Aug 11, 12:43 to 12:52 PDT **Region:** AM1 **Status:** RESOLVED **Summary** On August 11 at 12:43 PDT, some users in the AM1 region experienced printing delays. A sudden spike in print jobs within a short time frame impacted performance for approximately 10 minutes. **What Happened** An unexpected surge in print job activity temporarily slowed printing services for some users in the AM1 region. **Resolution** The team quickly identified the surge in print volume and took immediate action to stabilize the service by reallocating system resources and processing the backlog of queued jobs. Normal printing performance was fully restored by 12:52 PDT. **Next Steps** * Increase proactive monitoring to detect similar issues earlier. * Implement preventive measures later this year to identify and address such scenarios before they affect performance.
Your product runs on more than BarTender Cloud
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services