Pimberly Outage History
Pimberly is up right nowPingoru has recorded 49 incidents for Pimberly: 46 in the last 12 months and 3 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 15 | 32 of 720 (5%) |
| May 2026 | 11 | 0 of 744 (0%) |
| June 2026 | 4 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 3 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 533 (0%) |
Incidents, newest first
Minor August 14, 2026 Marketing Website recovered –
Started Aug 14, 2026, 12:18 PM UTC· resolved Aug 14, 2026, 12:18 PM UTC
No vendor updates were posted for this incident.
Minor August 6, 2026 EU Platform recovered –
Started Aug 06, 2026, 03:40 PM UTC· resolved Aug 06, 2026, 03:40 PM UTC
No vendor updates were posted for this incident.
Minor June 9, 2026 US Platform recovered –
Started Jun 09, 2026, 05:36 PM UTC· resolved Jun 09, 2026, 05:36 PM UTC
No vendor updates were posted for this incident.
Minor January 29, 2025 Intermittent login issues and errors 1h 51m EU Web App
Started Jan 29, 2025, 09:32 AM UTC· resolved Jan 29, 2025, 11:23 AM UTC
- investigating Jan 29, 2025, 09:32 AM UTC
We're aware that some users are experiencing intermittent issues when attempting to log into Pimberly at indigo.pimberly.com and next.pimberly.com. Our engineering team is actively investigating this issue, including whether it is related to wider reports of current disruptions to Amazon Web Services (AWS). Scheduled feeds and channels and the Pimberly API are not affected by this issue. We are treating this matter as a priority and will provide updates as more information becomes available.
- resolved Jan 29, 2025, 11:23 AM UTC
Amazon has identified the root cause of the issue and are putting mitigations in place as they work towards a full recovery. Since we redeployed our CloudFront distribution, we've continued to monitor the application and we're no longer seeing the errors that were occurring earlier. Any users who are still seeing errors should clear their browser cache before trying again. For further assistance, please contact our support team via help.pimberly.com or [email protected].
Minor November 5, 2024 Increase in queueing channel jobs – Services (Export Service)
Started Nov 05, 2024, 08:50 AM UTC· resolved Nov 05, 2024, 08:50 AM UTC
- resolved Nov 05, 2024, 08:50 AM UTC
Update: 11:46am Our development team has released a fix for this issue and jobs are being processed. Jobs will still queue until the backlog is cleared We're currently investigating delays to channel execution caused by a queue that has developed overnight. Our engineering team is working to resolve the issue as a priority. Admin users can see their queued jobs by going to Admin > Running Jobs. We will provide further updates as the issue is resolved.
Minor October 29, 2024 Heavy Database Load 3h 58m Services (Import Service), Services (Export Service), Services (Batch Service), Services (Image Service) and 1 more
Started Oct 29, 2024, 11:26 AM UTC· resolved Oct 29, 2024, 03:24 PM UTC
- investigating Oct 29, 2024, 11:26 AM UTC
We are currently experiencing high database loads on our Pimberly platform, which may be causing slower than usual performance or occasional errors. We apologize for the inconvenience this may cause and want to assure you that we are actively investigating the issue with our development team. Our top priority is ensuring the stability and reliability of your Pimberly experience, and we are working diligently to identify the root cause of this issue and implement a solution as soon as possible. In the meantime, please be aware that some features or functionality may be temporarily unavailable. We will provide updates on our progress and notify you once the issue has been resolved. Thank you for your patience and understanding. If you have any questions or concerns, please don't hesitate to reach out to our support team at [email protected].
- resolved Oct 29, 2024, 03:24 PM UTC
Database load is now returning to normal. We'll continue to monitor and make further adjustments and modifications to ensure a stable and reliable platform. Thank you for your patience while we investigated and resolved this issue.