Pimberly Outage History

Pimberly is up right now

Pimberly had 5 outages in the last 2 years totaling 1h 51m of downtime — averaging 0.2 incidents per month.

There were 5 Pimberly outages since November 5, 2024 totaling 1h 51m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.pimberly.com

Minor January 29, 2025

Intermittent login issues a...

Detected by Pingoru
Jan 29, 2025, 09:32 AM UTC
Resolved
Jan 29, 2025, 11:23 AM UTC
Duration
1h 51m
Affected: EU Web App
Timeline · 2 updates
  1. 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.

  2. 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].

Read the full incident report →

Minor November 5, 2024

Increase in queueing channe...

Detected by Pingoru
Nov 05, 2024, 08:50 AM UTC
Resolved
Nov 05, 2024, 08:50 AM UTC
Duration
—
Affected: Services (Export Service)
Timeline · 1 update
  1. 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.

Read the full incident report →