May <var data-var='date'>28</var>, <var data-var='time'>22:30</var> UTC Resolved - If you subscribe to Daily or Weekly Monitoring Reports, some data for May 28 will be missing. Future reports will include the recovered data. We experienced an unstable connection to a third party API blocking access to some zone files including .com. As a result, the zone data for May 28 could not be processed and surfaced into the reports. We apologise for any inconvenience this may cause and appreciate your understanding.

Monitoring reports missing data on 28th May

Apr <var data-var='date'>20</var>, <var data-var='time'>06:53</var> UTC Resolved - A fix has been deployed. As a result you may see a temporary increase in monitoring results for daily, weekly and monthly reports while historical .TOP data is populated. Mar <var data-var='date'> 5</var>, <var data-var='time'>12:34</var> UTC Identified - Root cause identified and fix in progress - We are in the process of migrating our account. Once complete we will be able to re-run the reports to get any missing data. Due to the volumes, we expect this to take a few more weeks. Jan <var data-var='date'>12</var>, <var data-var='time'>11:34</var> UTC Update - We are continuing to investigate this issue. Jan <var data-var='date'>12</var>, <var data-var='time'>09:00</var> UTC Investigating - We are currently addressing an issue where the .TOP top-level domain was temporarily marked as inactive by our upstream data provider, resulting in a brief disruption to monitoring data availability. We are working with the provider to restore access and expect normal monitoring coverage to resume within the next few days. We appreciate your patience and will share updates as they become available.

.TOP TLD Monitoring Interruption

Apr <var data-var='date'>16</var>, <var data-var='time'>10:40</var> UTC Completed - The scheduled maintenance has been completed. Apr <var data-var='date'>16</var>, <var data-var='time'>10:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr <var data-var='date'>15</var>, <var data-var='time'>11:04</var> UTC Scheduled - We need to perform an emergency database upgrade. This will impact user access to the Brand monitoring web application for up to 10 minutes. This upgrade is needed to: - Address critical vulnerabilities - Update high availability configuration This upgrade will require no modification/jobs around this timeframe. Users will need to save their work the start of the maintenance window.

Brand Monitoring maintenance

Apr <var data-var='date'>14</var>, <var data-var='time'>09:00</var> UTC Completed - The scheduled maintenance has been completed. Apr <var data-var='date'>14</var>, <var data-var='time'>08:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'>17</var>, <var data-var='time'>13:26</var> UTC Scheduled - A scheduled maintenance will take place on 14 April 2026 between 08:00 and 09:00 UTC. During this window, some BrandShelter services may be temporarily impacted. We apologise for any inconvenience this may cause.

Scheduled maintenance

Mar <var data-var='date'>31</var>, <var data-var='time'>23:00</var> UTC Resolved - Our monitoring connection was lost to the .US TLD for a short period. This only impacts our domain monitoring service and means .US TLDs may have been missing from some monitoring reports. The connection has now been restored and as a result you may see a temporary increase in monitoring results for daily, weekly and monthly reports while historical .US data is populated.

Brand Monitoring .US TLD interruption

Mar <var data-var='date'>11</var>, <var data-var='time'>11:45</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'>11</var>, <var data-var='time'>11:45</var> UTC Update - We are continuing to monitor for any further issues. Mar <var data-var='date'>11</var>, <var data-var='time'>10:50</var> UTC Monitoring - We experienced an issue affecting all clients using the BrandShelter portal. Unable to access the portal. Reason: We lost connection with a critical third party API causing pages to timeout and high load on servers. Root cause still being investigated and we are looking to enhance monitoring for future issues.

BrandShelter portal interruption (Resolved)

Mar <var data-var='date'>11</var>, <var data-var='time'>09:00</var> UTC Completed - The scheduled maintenance has been completed. Mar <var data-var='date'>11</var>, <var data-var='time'>08:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'> 5</var>, <var data-var='time'>16:10</var> UTC Scheduled - A scheduled maintenance will take place on 11 March 2026 between 08:00 and 09:00 UTC. During this window, some BrandShelter services may be temporarily impacted. Delayed processing of domain work requests Domain availability checks unavailable DNS zone publication to the default BrandShelter nameserver set unavailable (although DNS resolution is not expected to be impacted) We apologise for any inconvenience this may cause.

Scheduled Maintenance

Feb <var data-var='date'>17</var>, <var data-var='time'>16:54</var> UTC Resolved - Root Cause A capacity limitation in our API communication layer caused some requests to be processed more slowly under load, resulting in temporary delays and instability for certain platform operations. Resolution A fix was deployed on 17 February 2026 around 16:54 UTC, restoring normal service Configuration changes improved stability and reduced internal errors Additional logging was added to speed up future diagnostics Updated API service versions were rolled out progressively and monitored Feb <var data-var='date'>17</var>, <var data-var='time'>13:30</var> UTC Identified - Summary On 17 February 2026, the BrandShelter platform experienced a temporary service degradation impacting operations submitted via the web platform and the DNS API. Impact Customers may have encountered slowness or intermittent unavailability when performing various actions (but not limited to): Domain modifications DNS-related operations SSL order–related actions Other platform operations relying on API processing DNS resolution itself was not impacted. Existing DNS records continued to resolve normally throughout the incident.

Service Degradation Report (Resolved)

Feb <var data-var='date'>11</var>, <var data-var='time'>13:00</var> UTC Completed - The scheduled maintenance has been completed. Feb <var data-var='date'>11</var>, <var data-var='time'>12:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb <var data-var='date'> 9</var>, <var data-var='time'>15:19</var> UTC Scheduled - Hi everyone, A maintenance operation will take place on BrandMonitoring this Wednesday (11/02) between 12:00 and 13:00. (UTC+1) You may experience slight slowdowns during this time but no downtime. Have a good week !

[BrandMonitoring live Maintenance – Wednesday 11, 12:00 to 13:00]

Oct <var data-var='date'>30</var>, <var data-var='time'>13:00</var> UTC Completed - The scheduled maintenance has been completed. Oct <var data-var='date'>30</var>, <var data-var='time'>12:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Oct <var data-var='date'>29</var>, <var data-var='time'>13:58</var> UTC Scheduled - Dear customer, A maintenance operation will take place on BrandMonitoring this Thursday between 12:00 and 13:00. (UTC+1) You may experience slight slowdowns during this time. Please excuse any inconvenience this may cause.

[BrandMonitoring live Maintenance – Thursday, 12:00 to 13:00]

Jul <var data-var='date'>16</var>, <var data-var='time'>08:47</var> UTC Completed - The scheduled maintenance has been completed. Jul <var data-var='date'>16</var>, <var data-var='time'>08:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jul <var data-var='date'>15</var>, <var data-var='time'>13:58</var> UTC Update - We will be undergoing scheduled maintenance during this time. Jul <var data-var='date'>16</var>, <var data-var='time'>08:00</var> UTC Scheduled - Dear Customer, We will be performing a system maintenance on 2025-07-16 08:00:00 UTC. The following services may be affected and not reachable during the maintenance: WHOIS: Affected DNS resolution: NOT affected, Domains continue to resolve All other services will remain unaffected during this maintenance window. Maintenance details: START: 2025-07-16 08:00:00 UTC END: 2025-07-16 09:00:00 UTC Please excuse any inconvenience this may cause.

System maintenance on 2025-07-16 08:00:00 UTC.

Jul <var data-var='date'> 3</var>, <var data-var='time'>14:30</var> UTC Resolved - Between 17:36 UTC on 3rd July 2025 and 04:22 UTC on 4th July 2025, connections to backend systems, order processing, and brand monitoring services were unavailable. The issue has now been fully resolved.

Partial Service Disruption

Mar <var data-var='date'>25</var>, <var data-var='time'>10:00</var> UTC Completed - The scheduled maintenance has been completed. Mar <var data-var='date'>25</var>, <var data-var='time'>08:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'>12</var>, <var data-var='time'>12:28</var> UTC Scheduled - Dear Customer, We will be performing a system maintenance on 2025-03-25 08:00:00 UTC. XRRP API: Affected EPP API: Affected SOAP API: Affected XMLRPC API: Affected HTTPS API: Affected Web Interface: Affected WHOIS: Affected RDAP: Affected OT&E Environment: NOT affected, continues to be available DNS resolution: NOT affected, Domains continue to resolve vServer: NOT affected, vServer continue to be available All other services will remain unaffected during this maintenance window. Maintenance details: START: 2025-03-25 08:00:00 UTC END: 2025-03-25 10:00:00 UTC Please excuse any inconvenience this may cause

Scheduled Maintenance [March, 25th, 8-10 UTC]

Aug <var data-var='date'> 9</var>, <var data-var='time'>09:51</var> UTC Resolved - 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. Aug <var data-var='date'> 9</var>, <var data-var='time'>08:34</var> UTC Monitoring - Issue has been identified and resolution will be place within the hour. Aug <var data-var='date'> 9</var>, <var data-var='time'>06:52</var> UTC Identified - Time of Incident: Approximately 1 hour ago Current Status: 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. Impact: There will be delays in our response to tickets from non-verified users. For urgent matters, we recommend calling us! Actions Taken: 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. Next Steps: 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.

Issues with Ticket Parsing and Display for Non-Verified Users

Jul <var data-var='date'>12</var>, <var data-var='time'>12:56</var> UTC Resolved - 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. Jul <var data-var='date'>12</var>, <var data-var='time'>12:55</var> UTC Update - We are continuing to investigate this issue. Jul <var data-var='date'>12</var>, <var data-var='time'>09:09</var> UTC Update - 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 Jul <var data-var='date'>12</var>, <var data-var='time'>07:02</var> UTC Update - 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. Jul <var data-var='date'>12</var>, <var data-var='time'>05:18</var> UTC Update - 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. Jul <var data-var='date'>12</var>, <var data-var='time'>02:41</var> UTC Update - 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. Jul <var data-var='date'>12</var>, <var data-var='time'>00:45</var> UTC Investigating - 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.

Un-requested Password Reset Emails - BrandShelter Portal

Jun <var data-var='date'>20</var>, <var data-var='time'>09:57</var> UTC Resolved - 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 Jun <var data-var='date'>20</var>, <var data-var='time'>09:36</var> UTC Update - 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. Jun <var data-var='date'>20</var>, <var data-var='time'>09:07</var> UTC Identified - 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 poses no risk to the account(s) or portfolio(s). We will issue an update here no later than 09:40 UTC on 20 June 2024.

Web Portal: Not Displaying Domain Portfolio(s)

Dec <var data-var='date'>26</var>, <var data-var='time'>10:23</var> UTC Resolved - This incident has been resolved. Dec <var data-var='date'>26</var>, <var data-var='time'>10:23</var> UTC Update - We are continuing to investigate this issue. Dec <var data-var='date'>25</var>, <var data-var='time'>10:32</var> UTC Investigating - We are currently investigating this issue.

Degraded Performance on Standard Name Servers

Dec <var data-var='date'>23</var>, <var data-var='time'>09:24</var> UTC Resolved - the incident have been resolved , root cause to follow after vendor report Dec <var data-var='date'>23</var>, <var data-var='time'>04:34</var> UTC Identified - The two datacenters where the servers are located are having operations issues that is causing impact on ns1 and ns3 Dec <var data-var='date'>23</var>, <var data-var='time'>04:25</var> UTC Investigating - 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

Is BrandShelter down?

BrandShelter status is UP

Lastest published events

Monitoring reports missing data on 28th May

.TOP TLD Monitoring Interruption

Brand Monitoring maintenance

BrandShelter Services, Components and Regions

Recent BrandShelter events

Monitoring reports missing data on 28th May

.TOP TLD Monitoring Interruption

Brand Monitoring maintenance

Scheduled maintenance

Brand Monitoring .US TLD interruption

BrandShelter portal interruption (Resolved)