Is BrandShelter Down Right Now? Check if there is a current outage ongoing.

Dear Customers, We are pleased to inform you that the issue affecting our support platform, where tickets from non-verified users were not being parsed or displayed correctly, has now been fully resolved. What Happened: Earlier today, we experienced a bug in our support platform that caused delays in processing tickets from non-verified users. This was an unexpected issue as we have never required verification for users emailing us. Resolution: Our team worked closely with Zendesk, and the issue was identified and resolved swiftly. Normal ticket processing has resumed, and we are catching up on any delayed responses. Next Steps: We have requested a detailed postmortem from Zendesk to ensure they take steps to prevent such issues from occurring in the future. If you have any outstanding issues or if your inquiry was affected by this incident, please don’t hesitate to reach out to us again. We sincerely apologize for any inconvenience this may have caused and appreciate your understanding. If you need any further assistance, our team is here to help. Thank you for your continued trust in our support.

Issue has been identified and resolution will be place within the hour.

<b>Time of Incident:</b> Approximately 1 hour ago <b>Current Status:</b> Ongoing We are currently experiencing issues with our support platform where tickets from any non-verified users are not being parsed or displayed correctly. Please note that we have never required or been asked to verify users emailing us before, so this is an unexpected bug. <b>Impact:</b> There will be delays in our response to tickets from non-verified users. <b>For urgent matters</b>, we recommend calling us! <b>Actions Taken:</b> We have notified Zendesk of this issue and just completed a call with their support team. They have confirmed that this behavior is not normal functionality within their platform. <b>Next Steps:</b> We expect an update from Zendesk very soon and will provide more information on this status page as it becomes available. We will be requesting a postmortem from Zendesk once the issue is resolved to ensure that steps are taken to prevent similar issues in the future. Thank you for your patience as we work to resolve this issue.

Our investigations identified an error in the platform which caused the issue. The issue has been fixed and the Password Reset functionality is now fully restored after being temporarily disabled as a precaution. Please note, it is not mandatory for users to reset their current passwords as there was no data breach. We can confirm that the platform, accounts, or data have not been compromised as a result of this issue.

We are continuing to investigate this issue.

The investigation is still ongoing. While the cause of the issue is yet to be determined, we can confirm that no data was compromised or exposed. We appreciate your patience and will update the status post when more information is available

The Platform Team are continuing the investigation at this time. The Password Reset functionality remains disabled until further notice. The next update will be provided at 09:00AM UTC. We apologise for any inconvenience caused during this time and thank you for your patience and understanding.

The Platform Team are continuing to investigate the root cause of the issue. The Password Reset functionality will remain disabled until such a time the team can identify and resolve the issue. The next update will be provided at 07:00AM UTC We apologise for any inconvenience caused during this time.

The Platform Team are continuing to investigate the situation however as an interim measure, they have now disabled the Password Reset function whilst the investigation continues. The next update will be provided by 05:00AM UTC We apologise for any inconvenience caused during this time.

It has come to our attention that our system may have sent out password reset requests to many clients & users of our platform - we can confirm that the platform has encountered an error which caused this & at no point do we believe the platform or accounts have been compromised. We will update this status as soon as we can confirm a fix has been deployed to prevent such unintentional system messaging / password resets in future. The next update will be provided by 03:00AM UTC. We apologise for any inconvenience caused during this time.

The sync has been completed, all DUM and products are now being displayed correctly. Should you have ongoing issues or need assistance, please contact support and we'll come back as soon as possible

The cache sync has started which will fix the display error - this should be fully resolved within the next 30-minutes. Please contact support if there are urgent changes needed during this time and we will do these manually for you while the sync is completing.

We have identified an error in our front-end portal's ability to display domain portfolios - both in master and sub accounts. This is a read problem and has not affected the portfolios themselves. We are working to resolve this read-function now which will ensure accounts display the correct DUM. Note: this read error <b>poses no risk</b> to the account(s) or portfolio(s). We will issue an update here no later than 09:40 UTC on 20 June 2024.

This incident has been resolved.

We are continuing to investigate this issue.

We are currently investigating this issue.

the incident have been resolved , root cause to follow after vendor report

The two datacenters where the servers are located are having operations issues that is causing impact on ns1 and ns3

We are seeing reachability issues to two name servers. ns1/ns3 , if the domain is on anycast or setup using all 5 dns server there should be no impact