{"@attributes":{"version":"2.0"},"channel":{"title":"SR2\u00ae Cloud Status","link":"https:\/\/status.sr2.uk\/","description":"Incident history","generator":"github.com\/cstate","language":"en","lastBuildDate":"Tue, 14 Apr 2026 00:00:00 +0000","item":[{"title":"Updated .de verification requirements","link":"https:\/\/status.sr2.uk\/issues\/2026-04-14-de-verification-requirements\/","pubDate":"Tue, 14 Apr 2026 00:00:00 +0000","guid":"https:\/\/status.sr2.uk\/issues\/2026-04-14-de-verification-requirements\/","category":{},"description":"<p>In order to comply with NIS2, DENIC, the registry for .de, has introduced new registrant verification requirements,\neffective April 14, 2026.<\/p>\n<h2 id=\"whats-changing\">What\u2019s changing<\/h2>\n<p><strong>Risk-based verification can result in domain deletion.<\/strong><\/p>\n<p>DENIC will begin flagging potentially invalid or suspicious registrant data and require it to be verified.<\/p>\n<p>Here&rsquo;s how the process will work:<\/p>\n<p>When a registrant&rsquo;s data is flagged, they will receive an email requesting that they use the link provided to upload the verification documents.\nIf they don&rsquo;t provide the verification documents within 30 days:<\/p>\n<ul>\n<li>Their domain(s) will be suspended (DNS will stop working).<\/li>\n<li>Their domain(s) will enter a 90-day quarantine period.<\/li>\n<\/ul>\n<p>During the 90-day quarantine, they can complete verification to lift the suspension and reactivate their domain.\nIf verification is not completed within 90 days, all associated domain names <strong>will be permanently deleted<\/strong>.<\/p>\n<h2 id=\"how-to-correct-inaccurate-data\">How to correct inaccurate data<\/h2>\n<p>Once a registrant has been flagged for verification, any inaccurate data can be corrected by processing:<\/p>\n<ul>\n<li>an owner change (in cases where the email address must be changed or the registrant name must be substantially modified)<\/li>\n<li>a contact update (in cases where a minor change to the registrant name or other data must be made)<\/li>\n<\/ul>\n<p>Once the data has been updated, the new data must be verified within the original 30-day period.\nFailed email verification may trigger risk-based verification.<\/p>\n<p>Starting April 14, 2026, if a registrant fails to complete email verification, it may trigger an expedited risk-based verification process:<\/p>\n<ul>\n<li>The registrant will have 7 days (rather than 30) to provide the requested verification documents.<\/li>\n<li>After 7 days, the domain will be suspended and enter the 90-day quarantine period if verification has not been completed.<\/li>\n<li>At the end of the 90-day quarantine period, all associated domain names will be permanently deleted.<\/li>\n<\/ul>\n<h2 id=\"get-support\">Get support<\/h2>\n<p>If you receive an email asking you to verify your details and do not know how to proceed, reach out to our support service\nby emailing <a href=\"mailto:contact@sr2.uk\">contact@sr2.uk<\/a>.<\/p>\n"},{"title":"[Resolved] WhatsApp Message Send Issue","link":"https:\/\/status.sr2.uk\/issues\/2026-03-25-whatsapp-issue-banned-accounts\/","pubDate":"Wed, 25 Mar 2026 03:00:00 +0000","guid":"https:\/\/status.sr2.uk\/issues\/2026-03-25-whatsapp-issue-banned-accounts\/","category":"2026-03-31 16:15:00","description":"<p><strong>Resolved<\/strong>: This issue appears to only affect cases where no conversation history exists with the contact the message\nis sent to.\nDue to the nature of the helpdesk, messages are only sent to users that have already sent a message to the helpdesk, so\nwe do not believe this issue will affect our users.\nWe encourage you to get in touch if you do see any issues with your WhatsApp channel however we are no longer monitoring\nthis situation closely.\n\n  <span class=\"faded\">(16:15 UTC \u2014 Mar 31)<\/span>\n\n<\/p>\n<p><strong>Monitoring<\/strong>: We are not aware of this issue affecting any helpdesk currently however we continue to monitor.\nA fix has been found by the upstream project and will be rolled out once released formally.\n\n  <span class=\"faded\">(15:00 UTC \u2014 Mar 27)<\/span>\n\n<\/p>\n<p><strong>Monitoring<\/strong>: We have been made aware of an issue with the WhatsApp integration that we use where for some accounts,\nmostly accounts that have been banned and subsequently unbanned, users are noticing errors on message send.\nA fix is being investigated by the integration developer.\nTechnical details can be followed on GitHub at <a href=\"https:\/\/github.com\/WhiskeySockets\/Baileys\/issues\/2441\">https:\/\/github.com\/WhiskeySockets\/Baileys\/issues\/2441<\/a>.\n\n  <span class=\"faded\">(03:00 UTC \u2014 Mar 25)<\/span>\n\n<\/p>\n"},{"title":"New Status Page","link":"https:\/\/status.sr2.uk\/issues\/2026-03-17-new-status-page\/","pubDate":"Tue, 17 Mar 2026 12:00:00 +0000","guid":"https:\/\/status.sr2.uk\/issues\/2026-03-17-new-status-page\/","category":{},"description":"<p>We have deployed this new status page that will allow us to keep you better informed during incidents and outages.<\/p>\n<p>If you would like to see the old status page with the live monitoring details, this can now be found at\n<a href=\"https:\/\/livestatus.sr2.uk\/\">https:\/\/livestatus.sr2.uk\/<\/a>.<\/p>\n"},{"title":".at Org field now determines registrant type","link":"https:\/\/status.sr2.uk\/issues\/2026-03-12-at-org-field\/","pubDate":"Thu, 12 Mar 2026 00:00:00 +0000","guid":"https:\/\/status.sr2.uk\/issues\/2026-03-12-at-org-field\/","category":{},"description":"<h2 id=\"whats-changing\">What&rsquo;s changing<\/h2>\n<p>Effective immediately, the Org field for .at domains is optional.\nIt should be completed only for legal entities, as it determines the registrant type.\nIf data is provided in the Org field, the registrant will automatically be classified as a legal entity.\nAs a result, their contact details will be displayed in the public WHOIS.<\/p>\n<p>When submitting registrant data for a new registration, owner change, or contact update, the Org field must be left\nblank if the registrant is a private individual.<\/p>\n<h2 id=\"get-support\">Get support<\/h2>\n<p>If you have a .at registration and do not know how to proceed, reach out to our support service\nby emailing <a href=\"mailto:contact@sr2.uk\">contact@sr2.uk<\/a>.<\/p>\n"},{"title":"[Resolved] WhatsApp introducing usernames","link":"https:\/\/status.sr2.uk\/issues\/2025-12-01-whatsapp-usernames\/","pubDate":"Mon, 01 Dec 2025 12:00:00 +0000","guid":"https:\/\/status.sr2.uk\/issues\/2025-12-01-whatsapp-usernames\/","category":"2026-03-17 20:00:00","description":"<p><em>Update<\/em> - We have deployed updates to the WhatsApp channel and currently do not expect that there will be issues\nsending and receiving messages.<\/p>\n<p>&ndash; 2026-03-17<\/p>\n<p><em>Investigating<\/em> - We&rsquo;re aware that WhatsApp have begun rolling out a new feature replacing phone numbers with usernames.\nWe are monitoring this rollout and making updates to our integration as it evolves, but we expect there to be minor\ndisruptions to service until the roll out is complete.<\/p>\n<p>&ndash; 2025-12-01<\/p>\n"}]}}