Incidents reported on status page for Pimberly https://status.pimberly.com/ https://d1lppblt9t2x15.cloudfront.net/logos/ca6ece3c8607c5917ce5d3d24d76bb9f.png https://status.pimberly.com/ en https://status.pimberly.com/ Tue, 22 Apr 2025 06:45:22 +0000 https://status.pimberly.com/#5baa7dd7b46851dc24ad368b0a6d54f88c58376d140441d4309117670d7d8758 Website recovered https://status.pimberly.com/ Tue, 22 Apr 2025 06:24:56 +0000 https://status.pimberly.com/#5baa7dd7b46851dc24ad368b0a6d54f88c58376d140441d4309117670d7d8758 Website went down https://status.pimberly.com/ Tue, 08 Apr 2025 18:20:08 +0000 https://status.pimberly.com/#0215e8af0659c93578d27a4ce0d0f06db550340ea89d4d27ee2aacdbd850dc9f Website recovered https://status.pimberly.com/ Tue, 08 Apr 2025 18:18:15 +0000 https://status.pimberly.com/#0215e8af0659c93578d27a4ce0d0f06db550340ea89d4d27ee2aacdbd850dc9f Website went down https://status.pimberly.com/ Tue, 11 Mar 2025 18:17:45 +0000 https://status.pimberly.com/#0b0f965e8b360cd8961813430206b3e7d93444674355a7d9102acb2f5b8877fb Website recovered https://status.pimberly.com/ Tue, 11 Mar 2025 18:15:18 +0000 https://status.pimberly.com/#0b0f965e8b360cd8961813430206b3e7d93444674355a7d9102acb2f5b8877fb Website went down https://status.pimberly.com/ Fri, 07 Mar 2025 23:35:23 +0000 https://status.pimberly.com/#3e91d48c88eb4a79ad9fc0904dc01c12d91eb5222db0b461de1125711a4a178c Platform recovered https://status.pimberly.com/ Fri, 07 Mar 2025 23:30:23 +0000 https://status.pimberly.com/#3e91d48c88eb4a79ad9fc0904dc01c12d91eb5222db0b461de1125711a4a178c Platform went down https://status.pimberly.com/incident/503698 Wed, 29 Jan 2025 11:23:00 -0000 https://status.pimberly.com/incident/503698#566509e3eecbd206bb08d6bbfd86d77d8b1e1bed61ee1f1454a4a99f580c1442 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 support@pimberly.com. https://status.pimberly.com/incident/503698 Wed, 29 Jan 2025 10:17:00 -0000 https://status.pimberly.com/incident/503698#4bfa1b0c44076281e993f8c99968215bcb799845cfeca758d3587edab38038a5 Amazon has acknowledged an operational issue with Amazon CloudFront, and are actively investigating. Pimberly uses CloudFront to route traffic into the application, so to mitigate the errors being experienced by our users, we have completed a redeployment of our CloudFront distribution to an unaffected AWS region. We will continue to monitor closely. Users who have been affected may need to clear their browser cache if they continue to see errors. Our API and scheduled feeds and channels were not affected by this incident. https://status.pimberly.com/incident/503698 Wed, 29 Jan 2025 09:32:00 -0000 https://status.pimberly.com/incident/503698#43dd1ae2b936d1780a5cdca339ffe0d94325d84ec499110d803e6d8307ea5701 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. https://status.pimberly.com/incident/456292 Tue, 05 Nov 2024 08:50:00 -0000 https://status.pimberly.com/incident/456292#2a714fdd540e5cb1ec32a4d916a8f9700cec319d649f54b358bd7277d31ecfc3 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. https://status.pimberly.com/incident/452545 Tue, 29 Oct 2024 15:24:00 -0000 https://status.pimberly.com/incident/452545#49cedc788e02f1c2b1cba2ceb1cec8f694f9f5b923f1d5b05733411745803da8 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. https://status.pimberly.com/incident/452545 Tue, 29 Oct 2024 15:24:00 -0000 https://status.pimberly.com/incident/452545#49cedc788e02f1c2b1cba2ceb1cec8f694f9f5b923f1d5b05733411745803da8 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. https://status.pimberly.com/incident/452545 Tue, 29 Oct 2024 15:24:00 -0000 https://status.pimberly.com/incident/452545#49cedc788e02f1c2b1cba2ceb1cec8f694f9f5b923f1d5b05733411745803da8 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. https://status.pimberly.com/incident/452545 Tue, 29 Oct 2024 15:24:00 -0000 https://status.pimberly.com/incident/452545#49cedc788e02f1c2b1cba2ceb1cec8f694f9f5b923f1d5b05733411745803da8 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. https://status.pimberly.com/incident/452545 Tue, 29 Oct 2024 15:24:00 -0000 https://status.pimberly.com/incident/452545#49cedc788e02f1c2b1cba2ceb1cec8f694f9f5b923f1d5b05733411745803da8 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. https://status.pimberly.com/incident/452545 Tue, 29 Oct 2024 11:26:00 -0000 https://status.pimberly.com/incident/452545#0d2749910ccfd4be02d7c0d4fa68d6ca09a3fbce42c267142338183e26603d95 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 support@pimberly.com. https://status.pimberly.com/incident/452545 Tue, 29 Oct 2024 11:26:00 -0000 https://status.pimberly.com/incident/452545#0d2749910ccfd4be02d7c0d4fa68d6ca09a3fbce42c267142338183e26603d95 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 support@pimberly.com. https://status.pimberly.com/incident/452545 Tue, 29 Oct 2024 11:26:00 -0000 https://status.pimberly.com/incident/452545#0d2749910ccfd4be02d7c0d4fa68d6ca09a3fbce42c267142338183e26603d95 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 support@pimberly.com. https://status.pimberly.com/incident/452545 Tue, 29 Oct 2024 11:26:00 -0000 https://status.pimberly.com/incident/452545#0d2749910ccfd4be02d7c0d4fa68d6ca09a3fbce42c267142338183e26603d95 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 support@pimberly.com. https://status.pimberly.com/incident/452545 Tue, 29 Oct 2024 11:26:00 -0000 https://status.pimberly.com/incident/452545#0d2749910ccfd4be02d7c0d4fa68d6ca09a3fbce42c267142338183e26603d95 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 support@pimberly.com. https://status.pimberly.com/incident/406595 Wed, 31 Jul 2024 07:46:00 -0000 https://status.pimberly.com/incident/406595#96305d2002efeb0625d2b225630beee92534be1936d6aa5d5d82d4f9756b98ff Resolution: Engineers have fully resolved the incident through a restart of the Scheduler Services. Engineers continue to monitor the system. Steps to Mitigate: Enhanced alerting and monitoring has been added to the scheduler service. Engineers are implementing an auto restart process as part of the fail over procedures to mitigate future incidents. Update: Engineers have identified the root cause and all jobs are now being queued to be processed. We have scaled out services to address the backlog to ensure minimal impact to services. Engineers are currently investigating and resolving delays to scheduled feeds and channels. We are working on resolving the issue as a priority and will continue to provide frequent updates. Thank you for your patience. https://status.pimberly.com/incident/406595 Wed, 31 Jul 2024 07:46:00 -0000 https://status.pimberly.com/incident/406595#96305d2002efeb0625d2b225630beee92534be1936d6aa5d5d82d4f9756b98ff Resolution: Engineers have fully resolved the incident through a restart of the Scheduler Services. Engineers continue to monitor the system. Steps to Mitigate: Enhanced alerting and monitoring has been added to the scheduler service. Engineers are implementing an auto restart process as part of the fail over procedures to mitigate future incidents. Update: Engineers have identified the root cause and all jobs are now being queued to be processed. We have scaled out services to address the backlog to ensure minimal impact to services. Engineers are currently investigating and resolving delays to scheduled feeds and channels. We are working on resolving the issue as a priority and will continue to provide frequent updates. Thank you for your patience. https://status.pimberly.com/incident/219497 Sun, 18 Jun 2023 13:56:00 -0000 https://status.pimberly.com/incident/219497#7f99207ca5d82ce2264c645406ff946e611c51c96d42161e2bc07e9b0a04e1fc Please see below for our RCA of this incident. Duration: From 2:56am BST Tuesday 13th June until 9:05am on Wednesday 14th June users had intermittent issues trying to log in to Pimberly, increased error responses from our API, and delays to scheduled jobs. Root cause: The root cause has been identified as an integration between Pimberly and BigCommerce. As soon as the issue was identified we disabled the specific service and the problem ceased returning Pimberly to a fully operational state. How we will avoid in the future: We have refined a number of logging tools to ensure any similar scenarios are captured and altered to us immediately and automatically. A fix has been applied to protect against this scenario to ensure no further occurrences. Impact on customers · Users: o When the platform was up and running users could utilise all Pimberly functionality as usual o Tuesday - adhoc imports and exports were potentially delayed as they were likely caught up in the overall backlog of jobs from overnight delays · Overnight feeds and channels o Delays would have occurred to overnight jobs on both Monday night and Tuesday night, although we managed to process the vast majority throughout the day on Tuesday and everything on Wednesday o Normal access was returned at 9:05am on Wednesday morning · Sandbox was not impacted by the incident so has been fully operational throughout · No data was lost throughout this incident Any questions please either contact your account manager, support or Mike.walker@pimberly.com https://status.pimberly.com/incident/219497 Sun, 18 Jun 2023 13:56:00 -0000 https://status.pimberly.com/incident/219497#7f99207ca5d82ce2264c645406ff946e611c51c96d42161e2bc07e9b0a04e1fc Please see below for our RCA of this incident. Duration: From 2:56am BST Tuesday 13th June until 9:05am on Wednesday 14th June users had intermittent issues trying to log in to Pimberly, increased error responses from our API, and delays to scheduled jobs. Root cause: The root cause has been identified as an integration between Pimberly and BigCommerce. As soon as the issue was identified we disabled the specific service and the problem ceased returning Pimberly to a fully operational state. How we will avoid in the future: We have refined a number of logging tools to ensure any similar scenarios are captured and altered to us immediately and automatically. A fix has been applied to protect against this scenario to ensure no further occurrences. Impact on customers · Users: o When the platform was up and running users could utilise all Pimberly functionality as usual o Tuesday - adhoc imports and exports were potentially delayed as they were likely caught up in the overall backlog of jobs from overnight delays · Overnight feeds and channels o Delays would have occurred to overnight jobs on both Monday night and Tuesday night, although we managed to process the vast majority throughout the day on Tuesday and everything on Wednesday o Normal access was returned at 9:05am on Wednesday morning · Sandbox was not impacted by the incident so has been fully operational throughout · No data was lost throughout this incident Any questions please either contact your account manager, support or Mike.walker@pimberly.com https://status.pimberly.com/incident/219497 Sun, 18 Jun 2023 13:56:00 -0000 https://status.pimberly.com/incident/219497#7f99207ca5d82ce2264c645406ff946e611c51c96d42161e2bc07e9b0a04e1fc Please see below for our RCA of this incident. Duration: From 2:56am BST Tuesday 13th June until 9:05am on Wednesday 14th June users had intermittent issues trying to log in to Pimberly, increased error responses from our API, and delays to scheduled jobs. Root cause: The root cause has been identified as an integration between Pimberly and BigCommerce. As soon as the issue was identified we disabled the specific service and the problem ceased returning Pimberly to a fully operational state. How we will avoid in the future: We have refined a number of logging tools to ensure any similar scenarios are captured and altered to us immediately and automatically. A fix has been applied to protect against this scenario to ensure no further occurrences. Impact on customers · Users: o When the platform was up and running users could utilise all Pimberly functionality as usual o Tuesday - adhoc imports and exports were potentially delayed as they were likely caught up in the overall backlog of jobs from overnight delays · Overnight feeds and channels o Delays would have occurred to overnight jobs on both Monday night and Tuesday night, although we managed to process the vast majority throughout the day on Tuesday and everything on Wednesday o Normal access was returned at 9:05am on Wednesday morning · Sandbox was not impacted by the incident so has been fully operational throughout · No data was lost throughout this incident Any questions please either contact your account manager, support or Mike.walker@pimberly.com https://status.pimberly.com/incident/219497 Sun, 18 Jun 2023 13:56:00 -0000 https://status.pimberly.com/incident/219497#7f99207ca5d82ce2264c645406ff946e611c51c96d42161e2bc07e9b0a04e1fc Please see below for our RCA of this incident. Duration: From 2:56am BST Tuesday 13th June until 9:05am on Wednesday 14th June users had intermittent issues trying to log in to Pimberly, increased error responses from our API, and delays to scheduled jobs. Root cause: The root cause has been identified as an integration between Pimberly and BigCommerce. As soon as the issue was identified we disabled the specific service and the problem ceased returning Pimberly to a fully operational state. How we will avoid in the future: We have refined a number of logging tools to ensure any similar scenarios are captured and altered to us immediately and automatically. A fix has been applied to protect against this scenario to ensure no further occurrences. Impact on customers · Users: o When the platform was up and running users could utilise all Pimberly functionality as usual o Tuesday - adhoc imports and exports were potentially delayed as they were likely caught up in the overall backlog of jobs from overnight delays · Overnight feeds and channels o Delays would have occurred to overnight jobs on both Monday night and Tuesday night, although we managed to process the vast majority throughout the day on Tuesday and everything on Wednesday o Normal access was returned at 9:05am on Wednesday morning · Sandbox was not impacted by the incident so has been fully operational throughout · No data was lost throughout this incident Any questions please either contact your account manager, support or Mike.walker@pimberly.com https://status.pimberly.com/incident/219497 Sun, 18 Jun 2023 13:56:00 -0000 https://status.pimberly.com/incident/219497#7f99207ca5d82ce2264c645406ff946e611c51c96d42161e2bc07e9b0a04e1fc Please see below for our RCA of this incident. Duration: From 2:56am BST Tuesday 13th June until 9:05am on Wednesday 14th June users had intermittent issues trying to log in to Pimberly, increased error responses from our API, and delays to scheduled jobs. Root cause: The root cause has been identified as an integration between Pimberly and BigCommerce. As soon as the issue was identified we disabled the specific service and the problem ceased returning Pimberly to a fully operational state. How we will avoid in the future: We have refined a number of logging tools to ensure any similar scenarios are captured and altered to us immediately and automatically. A fix has been applied to protect against this scenario to ensure no further occurrences. Impact on customers · Users: o When the platform was up and running users could utilise all Pimberly functionality as usual o Tuesday - adhoc imports and exports were potentially delayed as they were likely caught up in the overall backlog of jobs from overnight delays · Overnight feeds and channels o Delays would have occurred to overnight jobs on both Monday night and Tuesday night, although we managed to process the vast majority throughout the day on Tuesday and everything on Wednesday o Normal access was returned at 9:05am on Wednesday morning · Sandbox was not impacted by the incident so has been fully operational throughout · No data was lost throughout this incident Any questions please either contact your account manager, support or Mike.walker@pimberly.com https://status.pimberly.com/incident/219497 Wed, 14 Jun 2023 15:35:00 -0000 https://status.pimberly.com/incident/219497#90423bf896c1e53c0b1ec5f2a3232c9beef9a87f6590c4912e474168d727b500 Ongoing monitoring of the application and database has confirmed there have been no further recurrences of the issue. The queue of jobs has now been processed and is picking up new jobs as they are generated. A full post-mortem analysis of this incident will be published in due course. https://status.pimberly.com/incident/219497 Wed, 14 Jun 2023 15:35:00 -0000 https://status.pimberly.com/incident/219497#90423bf896c1e53c0b1ec5f2a3232c9beef9a87f6590c4912e474168d727b500 Ongoing monitoring of the application and database has confirmed there have been no further recurrences of the issue. The queue of jobs has now been processed and is picking up new jobs as they are generated. A full post-mortem analysis of this incident will be published in due course. https://status.pimberly.com/incident/219497 Wed, 14 Jun 2023 15:35:00 -0000 https://status.pimberly.com/incident/219497#90423bf896c1e53c0b1ec5f2a3232c9beef9a87f6590c4912e474168d727b500 Ongoing monitoring of the application and database has confirmed there have been no further recurrences of the issue. The queue of jobs has now been processed and is picking up new jobs as they are generated. A full post-mortem analysis of this incident will be published in due course. https://status.pimberly.com/incident/219497 Wed, 14 Jun 2023 15:35:00 -0000 https://status.pimberly.com/incident/219497#90423bf896c1e53c0b1ec5f2a3232c9beef9a87f6590c4912e474168d727b500 Ongoing monitoring of the application and database has confirmed there have been no further recurrences of the issue. The queue of jobs has now been processed and is picking up new jobs as they are generated. A full post-mortem analysis of this incident will be published in due course. https://status.pimberly.com/incident/219497 Wed, 14 Jun 2023 15:35:00 -0000 https://status.pimberly.com/incident/219497#90423bf896c1e53c0b1ec5f2a3232c9beef9a87f6590c4912e474168d727b500 Ongoing monitoring of the application and database has confirmed there have been no further recurrences of the issue. The queue of jobs has now been processed and is picking up new jobs as they are generated. A full post-mortem analysis of this incident will be published in due course. https://status.pimberly.com/incident/219497 Wed, 14 Jun 2023 12:02:00 -0000 https://status.pimberly.com/incident/219497#c76fccea557d9c432a9f0f0b99721111fae3b6792376e561d6994fd81e73e47c We have identified the root cause of the ongoing issue. We are continuing to monitor overall application and database performance and scaling resources further to process the queue of pending jobs. We will provide a further update once the queue has been processed, and a full post-mortem analysis of this incident will be published in due course. https://status.pimberly.com/incident/219497 Wed, 14 Jun 2023 12:02:00 -0000 https://status.pimberly.com/incident/219497#c76fccea557d9c432a9f0f0b99721111fae3b6792376e561d6994fd81e73e47c We have identified the root cause of the ongoing issue. We are continuing to monitor overall application and database performance and scaling resources further to process the queue of pending jobs. We will provide a further update once the queue has been processed, and a full post-mortem analysis of this incident will be published in due course. https://status.pimberly.com/incident/219497 Wed, 14 Jun 2023 12:02:00 -0000 https://status.pimberly.com/incident/219497#c76fccea557d9c432a9f0f0b99721111fae3b6792376e561d6994fd81e73e47c We have identified the root cause of the ongoing issue. We are continuing to monitor overall application and database performance and scaling resources further to process the queue of pending jobs. We will provide a further update once the queue has been processed, and a full post-mortem analysis of this incident will be published in due course. https://status.pimberly.com/incident/219497 Wed, 14 Jun 2023 12:02:00 -0000 https://status.pimberly.com/incident/219497#c76fccea557d9c432a9f0f0b99721111fae3b6792376e561d6994fd81e73e47c We have identified the root cause of the ongoing issue. We are continuing to monitor overall application and database performance and scaling resources further to process the queue of pending jobs. We will provide a further update once the queue has been processed, and a full post-mortem analysis of this incident will be published in due course. https://status.pimberly.com/incident/219497 Wed, 14 Jun 2023 12:02:00 -0000 https://status.pimberly.com/incident/219497#c76fccea557d9c432a9f0f0b99721111fae3b6792376e561d6994fd81e73e47c We have identified the root cause of the ongoing issue. We are continuing to monitor overall application and database performance and scaling resources further to process the queue of pending jobs. We will provide a further update once the queue has been processed, and a full post-mortem analysis of this incident will be published in due course. https://status.pimberly.com/incident/219497 Wed, 14 Jun 2023 08:23:00 -0000 https://status.pimberly.com/incident/219497#d56bfe4e6ee57b1cdb89a35cf2aa4a09b4bb3fe4e8e059d1b77196311565202a Our engineers are continuing to investigate the root cause of the issues being experienced. Task processing for overnight jobs and ad-hoc imports and exports may be delayed but we are actively managing the queue and scaling our resources as required. https://status.pimberly.com/incident/219497 Wed, 14 Jun 2023 08:23:00 -0000 https://status.pimberly.com/incident/219497#d56bfe4e6ee57b1cdb89a35cf2aa4a09b4bb3fe4e8e059d1b77196311565202a Our engineers are continuing to investigate the root cause of the issues being experienced. Task processing for overnight jobs and ad-hoc imports and exports may be delayed but we are actively managing the queue and scaling our resources as required. https://status.pimberly.com/incident/219497 Wed, 14 Jun 2023 08:23:00 -0000 https://status.pimberly.com/incident/219497#d56bfe4e6ee57b1cdb89a35cf2aa4a09b4bb3fe4e8e059d1b77196311565202a Our engineers are continuing to investigate the root cause of the issues being experienced. Task processing for overnight jobs and ad-hoc imports and exports may be delayed but we are actively managing the queue and scaling our resources as required. https://status.pimberly.com/incident/219497 Wed, 14 Jun 2023 08:23:00 -0000 https://status.pimberly.com/incident/219497#d56bfe4e6ee57b1cdb89a35cf2aa4a09b4bb3fe4e8e059d1b77196311565202a Our engineers are continuing to investigate the root cause of the issues being experienced. Task processing for overnight jobs and ad-hoc imports and exports may be delayed but we are actively managing the queue and scaling our resources as required. https://status.pimberly.com/incident/219497 Wed, 14 Jun 2023 08:23:00 -0000 https://status.pimberly.com/incident/219497#d56bfe4e6ee57b1cdb89a35cf2aa4a09b4bb3fe4e8e059d1b77196311565202a Our engineers are continuing to investigate the root cause of the issues being experienced. Task processing for overnight jobs and ad-hoc imports and exports may be delayed but we are actively managing the queue and scaling our resources as required. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 19:30:00 -0000 https://status.pimberly.com/incident/219497#731b127d3c5d215ad9d119fdd9ed7bfaca1e9e54c42d4f144b33f849958df609 Our API and task processing services have stabilised, scheduled imports and exports are executing as normal. We are still seeing some performance issues on our core database cluster and our engineers are continuing to investigate the cause of these issues with our database provider. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 19:30:00 -0000 https://status.pimberly.com/incident/219497#731b127d3c5d215ad9d119fdd9ed7bfaca1e9e54c42d4f144b33f849958df609 Our API and task processing services have stabilised, scheduled imports and exports are executing as normal. We are still seeing some performance issues on our core database cluster and our engineers are continuing to investigate the cause of these issues with our database provider. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 19:30:00 -0000 https://status.pimberly.com/incident/219497#731b127d3c5d215ad9d119fdd9ed7bfaca1e9e54c42d4f144b33f849958df609 Our API and task processing services have stabilised, scheduled imports and exports are executing as normal. We are still seeing some performance issues on our core database cluster and our engineers are continuing to investigate the cause of these issues with our database provider. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 19:30:00 -0000 https://status.pimberly.com/incident/219497#731b127d3c5d215ad9d119fdd9ed7bfaca1e9e54c42d4f144b33f849958df609 Our API and task processing services have stabilised, scheduled imports and exports are executing as normal. We are still seeing some performance issues on our core database cluster and our engineers are continuing to investigate the cause of these issues with our database provider. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 19:30:00 -0000 https://status.pimberly.com/incident/219497#731b127d3c5d215ad9d119fdd9ed7bfaca1e9e54c42d4f144b33f849958df609 Our API and task processing services have stabilised, scheduled imports and exports are executing as normal. We are still seeing some performance issues on our core database cluster and our engineers are continuing to investigate the cause of these issues with our database provider. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 15:19:00 -0000 https://status.pimberly.com/incident/219497#a8882cf56eaf276de2a3713bb579a0ffc5098e6b9185d76a650755060980de02 Despite periods of stability, we're continuing to experience further intermittent outages affecting the Pimberly application, the API and task processing. Our engineers are continuing to investigate with our database provider in order to find a resolution. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 15:19:00 -0000 https://status.pimberly.com/incident/219497#a8882cf56eaf276de2a3713bb579a0ffc5098e6b9185d76a650755060980de02 Despite periods of stability, we're continuing to experience further intermittent outages affecting the Pimberly application, the API and task processing. Our engineers are continuing to investigate with our database provider in order to find a resolution. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 15:19:00 -0000 https://status.pimberly.com/incident/219497#a8882cf56eaf276de2a3713bb579a0ffc5098e6b9185d76a650755060980de02 Despite periods of stability, we're continuing to experience further intermittent outages affecting the Pimberly application, the API and task processing. Our engineers are continuing to investigate with our database provider in order to find a resolution. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 15:19:00 -0000 https://status.pimberly.com/incident/219497#a8882cf56eaf276de2a3713bb579a0ffc5098e6b9185d76a650755060980de02 Despite periods of stability, we're continuing to experience further intermittent outages affecting the Pimberly application, the API and task processing. Our engineers are continuing to investigate with our database provider in order to find a resolution. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 15:19:00 -0000 https://status.pimberly.com/incident/219497#a8882cf56eaf276de2a3713bb579a0ffc5098e6b9185d76a650755060980de02 Despite periods of stability, we're continuing to experience further intermittent outages affecting the Pimberly application, the API and task processing. Our engineers are continuing to investigate with our database provider in order to find a resolution. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 13:02:00 -0000 https://status.pimberly.com/incident/219497#159b0ce52e30025e21ad815b0afbfdbb08bd8b828e1e7f3cc2013f0e9096c201 Since deploying additional database resource we have seen improvements to stability over the last hour; we continue to monitor and react as required. The underlying root-cause continues to be investigated by our engineering team and our database provider. We will post further updates this afternoon. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 13:02:00 -0000 https://status.pimberly.com/incident/219497#159b0ce52e30025e21ad815b0afbfdbb08bd8b828e1e7f3cc2013f0e9096c201 Since deploying additional database resource we have seen improvements to stability over the last hour; we continue to monitor and react as required. The underlying root-cause continues to be investigated by our engineering team and our database provider. We will post further updates this afternoon. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 13:02:00 -0000 https://status.pimberly.com/incident/219497#159b0ce52e30025e21ad815b0afbfdbb08bd8b828e1e7f3cc2013f0e9096c201 Since deploying additional database resource we have seen improvements to stability over the last hour; we continue to monitor and react as required. The underlying root-cause continues to be investigated by our engineering team and our database provider. We will post further updates this afternoon. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 13:02:00 -0000 https://status.pimberly.com/incident/219497#159b0ce52e30025e21ad815b0afbfdbb08bd8b828e1e7f3cc2013f0e9096c201 Since deploying additional database resource we have seen improvements to stability over the last hour; we continue to monitor and react as required. The underlying root-cause continues to be investigated by our engineering team and our database provider. We will post further updates this afternoon. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 13:02:00 -0000 https://status.pimberly.com/incident/219497#159b0ce52e30025e21ad815b0afbfdbb08bd8b828e1e7f3cc2013f0e9096c201 Since deploying additional database resource we have seen improvements to stability over the last hour; we continue to monitor and react as required. The underlying root-cause continues to be investigated by our engineering team and our database provider. We will post further updates this afternoon. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 11:27:00 -0000 https://status.pimberly.com/incident/219497#43e7eb15460fd01fbc2e38f673c7d820f9d7c08e0804e104ddb884fde262ff97 Our engineers continue to investigate the ongoing incidents of unexpected downtime. We are in contact with our database provider who is assisting with the investigation. As a mitigation step we are deploying additional database resource, and scaling our task processing infrastructure to help process the queue of pending tasks. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 11:27:00 -0000 https://status.pimberly.com/incident/219497#43e7eb15460fd01fbc2e38f673c7d820f9d7c08e0804e104ddb884fde262ff97 Our engineers continue to investigate the ongoing incidents of unexpected downtime. We are in contact with our database provider who is assisting with the investigation. As a mitigation step we are deploying additional database resource, and scaling our task processing infrastructure to help process the queue of pending tasks. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 11:27:00 -0000 https://status.pimberly.com/incident/219497#43e7eb15460fd01fbc2e38f673c7d820f9d7c08e0804e104ddb884fde262ff97 Our engineers continue to investigate the ongoing incidents of unexpected downtime. We are in contact with our database provider who is assisting with the investigation. As a mitigation step we are deploying additional database resource, and scaling our task processing infrastructure to help process the queue of pending tasks. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 11:27:00 -0000 https://status.pimberly.com/incident/219497#43e7eb15460fd01fbc2e38f673c7d820f9d7c08e0804e104ddb884fde262ff97 Our engineers continue to investigate the ongoing incidents of unexpected downtime. We are in contact with our database provider who is assisting with the investigation. As a mitigation step we are deploying additional database resource, and scaling our task processing infrastructure to help process the queue of pending tasks. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 11:27:00 -0000 https://status.pimberly.com/incident/219497#43e7eb15460fd01fbc2e38f673c7d820f9d7c08e0804e104ddb884fde262ff97 Our engineers continue to investigate the ongoing incidents of unexpected downtime. We are in contact with our database provider who is assisting with the investigation. As a mitigation step we are deploying additional database resource, and scaling our task processing infrastructure to help process the queue of pending tasks. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 10:28:00 -0000 https://status.pimberly.com/incident/219497#2df7e192b032e43a1833eaf69670860a387f581ddaa9fff342f22f3e2e6111f3 We are continuing to investigate the issue and will post a further update before 12:30 BST. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 10:28:00 -0000 https://status.pimberly.com/incident/219497#2df7e192b032e43a1833eaf69670860a387f581ddaa9fff342f22f3e2e6111f3 We are continuing to investigate the issue and will post a further update before 12:30 BST. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 10:28:00 -0000 https://status.pimberly.com/incident/219497#2df7e192b032e43a1833eaf69670860a387f581ddaa9fff342f22f3e2e6111f3 We are continuing to investigate the issue and will post a further update before 12:30 BST. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 10:28:00 -0000 https://status.pimberly.com/incident/219497#2df7e192b032e43a1833eaf69670860a387f581ddaa9fff342f22f3e2e6111f3 We are continuing to investigate the issue and will post a further update before 12:30 BST. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 10:28:00 -0000 https://status.pimberly.com/incident/219497#2df7e192b032e43a1833eaf69670860a387f581ddaa9fff342f22f3e2e6111f3 We are continuing to investigate the issue and will post a further update before 12:30 BST. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 09:50:00 -0000 https://status.pimberly.com/incident/219497#1c41d350b0a2526b71a3877a1a8365d80232b0ca4bde51124dab7771c705d912 We're currently investigating a further occurrence of unexpected downtime affecting the Pimberly app and API. We will post a further update before 11:30 BST. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 09:50:00 -0000 https://status.pimberly.com/incident/219497#1c41d350b0a2526b71a3877a1a8365d80232b0ca4bde51124dab7771c705d912 We're currently investigating a further occurrence of unexpected downtime affecting the Pimberly app and API. We will post a further update before 11:30 BST. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 09:50:00 -0000 https://status.pimberly.com/incident/219497#1c41d350b0a2526b71a3877a1a8365d80232b0ca4bde51124dab7771c705d912 We're currently investigating a further occurrence of unexpected downtime affecting the Pimberly app and API. We will post a further update before 11:30 BST. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 09:50:00 -0000 https://status.pimberly.com/incident/219497#1c41d350b0a2526b71a3877a1a8365d80232b0ca4bde51124dab7771c705d912 We're currently investigating a further occurrence of unexpected downtime affecting the Pimberly app and API. We will post a further update before 11:30 BST. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 09:50:00 -0000 https://status.pimberly.com/incident/219497#1c41d350b0a2526b71a3877a1a8365d80232b0ca4bde51124dab7771c705d912 We're currently investigating a further occurrence of unexpected downtime affecting the Pimberly app and API. We will post a further update before 11:30 BST. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 08:59:00 -0000 https://status.pimberly.com/incident/219497#1af016ac42ee47dd093cc23d7d6718ad42a6e665b5ed4993288486f099b36204 Access to Pimberly has now been restored and the API is responding to requests as normal. Our task infrastructure is now processing the queue of jobs such as feeds and channels. We will actively monitor and scale our resources to help process the queue as quickly as possible. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 08:59:00 -0000 https://status.pimberly.com/incident/219497#1af016ac42ee47dd093cc23d7d6718ad42a6e665b5ed4993288486f099b36204 Access to Pimberly has now been restored and the API is responding to requests as normal. Our task infrastructure is now processing the queue of jobs such as feeds and channels. We will actively monitor and scale our resources to help process the queue as quickly as possible. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 08:59:00 -0000 https://status.pimberly.com/incident/219497#1af016ac42ee47dd093cc23d7d6718ad42a6e665b5ed4993288486f099b36204 Access to Pimberly has now been restored and the API is responding to requests as normal. Our task infrastructure is now processing the queue of jobs such as feeds and channels. We will actively monitor and scale our resources to help process the queue as quickly as possible. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 08:59:00 -0000 https://status.pimberly.com/incident/219497#1af016ac42ee47dd093cc23d7d6718ad42a6e665b5ed4993288486f099b36204 Access to Pimberly has now been restored and the API is responding to requests as normal. Our task infrastructure is now processing the queue of jobs such as feeds and channels. We will actively monitor and scale our resources to help process the queue as quickly as possible. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 08:59:00 -0000 https://status.pimberly.com/incident/219497#1af016ac42ee47dd093cc23d7d6718ad42a6e665b5ed4993288486f099b36204 Access to Pimberly has now been restored and the API is responding to requests as normal. Our task infrastructure is now processing the queue of jobs such as feeds and channels. We will actively monitor and scale our resources to help process the queue as quickly as possible. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 08:30:00 -0000 https://status.pimberly.com/incident/219497#fba298033d4f2c6a95596f371cdf9b06302a8896d786ae42f500022505ad2e76 We are currently investigating an issue that is preventing users from logging in to Pimberly, and that is also causing timeouts or other errors from our API. Scheduled feeds and channels are also affected. Our senior engineers are working on this as a priority. We will share our next update before 10:00 BST. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 08:30:00 -0000 https://status.pimberly.com/incident/219497#fba298033d4f2c6a95596f371cdf9b06302a8896d786ae42f500022505ad2e76 We are currently investigating an issue that is preventing users from logging in to Pimberly, and that is also causing timeouts or other errors from our API. Scheduled feeds and channels are also affected. Our senior engineers are working on this as a priority. We will share our next update before 10:00 BST. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 08:30:00 -0000 https://status.pimberly.com/incident/219497#fba298033d4f2c6a95596f371cdf9b06302a8896d786ae42f500022505ad2e76 We are currently investigating an issue that is preventing users from logging in to Pimberly, and that is also causing timeouts or other errors from our API. Scheduled feeds and channels are also affected. Our senior engineers are working on this as a priority. We will share our next update before 10:00 BST. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 08:30:00 -0000 https://status.pimberly.com/incident/219497#fba298033d4f2c6a95596f371cdf9b06302a8896d786ae42f500022505ad2e76 We are currently investigating an issue that is preventing users from logging in to Pimberly, and that is also causing timeouts or other errors from our API. Scheduled feeds and channels are also affected. Our senior engineers are working on this as a priority. We will share our next update before 10:00 BST. https://status.pimberly.com/incident/219497 Tue, 13 Jun 2023 08:30:00 -0000 https://status.pimberly.com/incident/219497#fba298033d4f2c6a95596f371cdf9b06302a8896d786ae42f500022505ad2e76 We are currently investigating an issue that is preventing users from logging in to Pimberly, and that is also causing timeouts or other errors from our API. Scheduled feeds and channels are also affected. Our senior engineers are working on this as a priority. We will share our next update before 10:00 BST.