become.1 GmbH Status - Incident history https://become1.instatus.com become.1 GmbH Tue, 5 May 2026 14:48:00 +0000 Connection issues with .de domains Type: Incident Duration: 14 hours and 32 minutes Affected Components: API, App, Website May 5, 17:54:00 GMT+0 - Resolved - **Resolution:** The .DE registry implemented a fix at approximately **07:54 PM EDT**. Our team monitored the propagation and verified that DNS resolution returned to 100% health globally by early morning on **May 6, 2026**. May 5, 14:48:00 GMT+0 - Identified - **Summary:** On **May 5, 2026**, between **04:48 PM and 07:54 PM EDT**, users may have experienced difficulties accessing `app.become1.de` due to a global issue affecting the .DE Top-Level Domain (TLD). **Impact:** During this window, DNS queries for our domain returned `SERVFAIL` errors for many users, specifically those using security-aware DNS providers (like Google or Cloudflare). This resulted in the application being unreachable, although our internal servers and data remained fully operational and secure. **Root Cause:** The issue was identified as an **upstream failure at the .DE Registry (DENIC)**. Following a scheduled maintenance window, the registry encountered a global DNSSEC signing error. This caused external DNS resolvers to reject records for .DE domains as a security precaution. Type: Incident

Duration: 14 hours and 32 minutes

Affected Components: , ,

<p><small>May <var data-var='date'> 5</var>, <var data-var='time'>17:54:00</var> GMT+0</small><br><strong>Resolved</strong> - **Resolution:** The .DE registry implemented a fix at approximately **07:54 PM EDT**. Our team monitored the propagation and verified that DNS resolution returned to 100% health globally by early morning on **May 6, 2026**..</p> <p><small>May <var data-var='date'> 5</var>, <var data-var='time'>14:48:00</var> GMT+0</small><br><strong>Identified</strong> - **Summary:** On **May 5, 2026**, between **04:48 PM and 07:54 PM EDT**, users may have experienced difficulties accessing `app.become1.de` due to a global issue affecting the .DE Top-Level Domain (TLD). **Impact:** During this window, DNS queries for our domain returned `SERVFAIL` errors for many users, specifically those using security-aware DNS providers (like Google or Cloudflare). This resulted in the application being unreachable, although our internal servers and data remained fully operational and secure. **Root Cause:** The issue was identified as an **upstream failure at the .DE Registry (DENIC)**. Following a scheduled maintenance window, the registry encountered a global DNSSEC signing error. This caused external DNS resolvers to reject records for .DE domains as a security precaution..</p> ]]> Tue, 5 May 2026 14:48:00 +0000 https://become1.instatus.com/incident/cmotnqu5e04rlm9kzweql9igd https://become1.instatus.com/incident/cmotnqu5e04rlm9kzweql9igd Our Website ist currently unavailable Type: Incident Duration: 1 hour and 39 minutes Affected Components: API, App, Website Dec 5, 11:55:54 GMT+0 - Investigating - We are currently investigating the issue Dec 5, 11:58:42 GMT+0 - Identified - We are continuing to work on a fix for this incident. Dec 5, 13:35:14 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 39 minutes

Affected Components: , ,

<p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>11:55:54</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating the issue.</p> <p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>11:58:42</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>13:35:14</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. .</p> ]]> Fri, 5 Dec 2025 11:55:54 +0000 https://become1.instatus.com/incident/cmist6g3201111qqgik5d3qug https://become1.instatus.com/incident/cmist6g3201111qqgik5d3qug The become1.de Website shows a fake cloudflare redirect Type: Incident Duration: 2 hours and 48 minutes Affected Components: Website Nov 21, 11:00:00 GMT+0 - Investigating - Please don't klick on the cloudflare banner, we're working on a fix. Nov 21, 12:00:43 GMT+0 - Identified - We are continuing to work on a fix for this incident. Nov 21, 13:09:09 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Nov 21, 13:48:09 GMT+0 - Resolved - The issue is fixed and the Website is working like expected. We have no deeper impact discovered now. Type: Incident

Duration: 2 hours and 48 minutes

Affected Components:

<p><small>Nov <var data-var='date'> 21</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Investigating</strong> - Please don't klick on the cloudflare banner, we're working on a fix. .</p> <p><small>Nov <var data-var='date'> 21</var>, <var data-var='time'>12:00:43</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Nov <var data-var='date'> 21</var>, <var data-var='time'>13:09:09</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Nov <var data-var='date'> 21</var>, <var data-var='time'>13:48:09</var> GMT+0</small><br><strong>Resolved</strong> - The issue is fixed and the Website is working like expected. We have no deeper impact discovered now..</p> ]]> Fri, 21 Nov 2025 11:00:00 +0000 https://become1.instatus.com/incident/cmi8uibo502h6xag6n01hof5v https://become1.instatus.com/incident/cmi8uibo502h6xag6n01hof5v Invalid vouchers Type: Incident Duration: 1 day and 29 minutes Affected Components: App, API Jul 17, 13:29:08 GMT+0 - Investigating - We're currently experiencing an issue with our **automatic voucher generation** feature. When you try to create vouchers, you might see an "invalid PDF" message. This is due to a problem with our voucher provider. We sincerely apologize for any inconvenience this causes. Our team is actively working on a solution to get things back up and running as quickly as possible. Jul 18, 06:06:53 GMT+0 - Identified - We're still working to resolve the issue with automatic voucher generation. We've identified that our voucher provider recently performed a security update, and during this process, our IP address for the ordering system was no longer whitelisted. We're in contact with our provider and are awaiting a fix to re-enable our access. Jul 18, 13:58:31 GMT+0 - Resolved - All services are back up and running as usual. Thank you for your patience. We are now implementing measures to prevent incidents of this kind in the future. Type: Incident

Duration: 1 day and 29 minutes

Affected Components: ,

<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>13:29:08</var> GMT+0</small><br><strong>Investigating</strong> - We're currently experiencing an issue with our **automatic voucher generation** feature. When you try to create vouchers, you might see an "invalid PDF" message. This is due to a problem with our voucher provider. We sincerely apologize for any inconvenience this causes. Our team is actively working on a solution to get things back up and running as quickly as possible..</p> <p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>06:06:53</var> GMT+0</small><br><strong>Identified</strong> - We're still working to resolve the issue with automatic voucher generation. We've identified that our voucher provider recently performed a security update, and during this process, our IP address for the ordering system was no longer whitelisted. We're in contact with our provider and are awaiting a fix to re-enable our access..</p> <p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>13:58:31</var> GMT+0</small><br><strong>Resolved</strong> - All services are back up and running as usual. Thank you for your patience. We are now implementing measures to prevent incidents of this kind in the future..</p> ]]> Thu, 17 Jul 2025 13:29:08 +0000 https://become1.instatus.com/incident/cmd7ff80g0065hdbsp5pgytz8 https://become1.instatus.com/incident/cmd7ff80g0065hdbsp5pgytz8 AWS Account Blocked Due to High Email Bounce Rate Type: Incident Duration: 1 day, 16 hours and 21 minutes Affected Components: App Jun 16, 22:00:00 GMT+0 - Monitoring - We are currently experiencing an incident that has led to our AWS account being blocked, impacting our email sending capabilities. \*\*What Happened:\*\* An internal notification email address, previously configured in multiple locations within our system, was recently deleted. Despite its deletion, our systems continued to send a high volume of emails to this address. As a result, all emails sent to this non-existent address hard bounced. \*\*Impact:\*\* The continuous sending to the deleted email address caused our overall email bounce rate to surge, reaching approximately 22%. When the bounce rate exceeded 20%, Amazon Web Services (AWS) automatically blocked our account, preventing us from sending any further emails. \*\*Current Status:\*\* We've \*\*identified the root cause\*\* of the issue and have \*\*rectified the problem\*\* by removing the deleted email address from all configurations. We are now \*\*awaiting AWS to unblock our account\*\* so we can resume normal email operations. Jun 18, 14:21:22 GMT+0 - Resolved - This incident has been resolved. We will closely monitor the service to prevent this from happening again. Type: Incident

Duration: 1 day, 16 hours and 21 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>22:00:00</var> GMT+0</small><br><strong>Monitoring</strong> - We are currently experiencing an incident that has led to our AWS account being blocked, impacting our email sending capabilities. \*\*What Happened:\*\* An internal notification email address, previously configured in multiple locations within our system, was recently deleted. Despite its deletion, our systems continued to send a high volume of emails to this address. As a result, all emails sent to this non-existent address hard bounced. \*\*Impact:\*\* The continuous sending to the deleted email address caused our overall email bounce rate to surge, reaching approximately 22%. When the bounce rate exceeded 20%, Amazon Web Services (AWS) automatically blocked our account, preventing us from sending any further emails. \*\*Current Status:\*\* We've \*\*identified the root cause\*\* of the issue and have \*\*rectified the problem\*\* by removing the deleted email address from all configurations. We are now \*\*awaiting AWS to unblock our account\*\* so we can resume normal email operations..</p> <p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>14:21:22</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. We will closely monitor the service to prevent this from happening again. .</p> ]]> Mon, 16 Jun 2025 22:00:00 +0000 https://become1.instatus.com/incident/cmc0g428q000cks9go9h9htvz https://become1.instatus.com/incident/cmc0g428q000cks9go9h9htvz Phishing Warning Triggered by Default Firebase Auth Domain Type: Incident Duration: 3 days, 22 hours and 57 minutes Affected Components: App May 23, 07:40:00 GMT+0 - Identified - A phishing warning was reported during login to the become1 app due to the use of Firebase’s default authentication domain (\[PROJECT\_ID\].[firebaseapp.com](http://firebaseapp.com)). Use of Firebase’s shared default domain, which is occasionally flagged due to misuse by other applications. May 26, 15:35:01 GMT+0 - Monitoring - Issue was solved and tested on our test environments. Waiting for external actions to deploy the solution to production. May 27, 06:36:33 GMT+0 - Resolved - We want to inform you that the recent login and security issues reported by some users have been successfully resolved. Thanks to your timely feedback and alerts, our teams were able to respond quickly and implement a solution. The fix is already live in our production systems, and DNS updates will be fully completed within the next 24 hours. We are currently monitoring all systems closely to ensure everything continues to work smoothly and securely. Thank you again for your attention and support — your input was crucial in helping us respond swiftly and effectively. Type: Incident

Duration: 3 days, 22 hours and 57 minutes

Affected Components:

<p><small>May <var data-var='date'> 23</var>, <var data-var='time'>07:40:00</var> GMT+0</small><br><strong>Identified</strong> - A phishing warning was reported during login to the become1 app due to the use of Firebase’s default authentication domain (\[PROJECT\_ID\].[firebaseapp.com](http://firebaseapp.com)). Use of Firebase’s shared default domain, which is occasionally flagged due to misuse by other applications..</p> <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>15:35:01</var> GMT+0</small><br><strong>Monitoring</strong> - Issue was solved and tested on our test environments. Waiting for external actions to deploy the solution to production..</p> <p><small>May <var data-var='date'> 27</var>, <var data-var='time'>06:36:33</var> GMT+0</small><br><strong>Resolved</strong> - We want to inform you that the recent login and security issues reported by some users have been successfully resolved. Thanks to your timely feedback and alerts, our teams were able to respond quickly and implement a solution. The fix is already live in our production systems, and DNS updates will be fully completed within the next 24 hours. We are currently monitoring all systems closely to ensure everything continues to work smoothly and securely. Thank you again for your attention and support — your input was crucial in helping us respond swiftly and effectively..</p> ]]> Fri, 23 May 2025 07:40:00 +0000 https://become1.instatus.com/incident/cmb0r8fwi00186fs35ytd2xbn https://become1.instatus.com/incident/cmb0r8fwi00186fs35ytd2xbn Authentication via Firebase is not Working in the become1 App Type: Incident Affected Components: App May 7, 08:30:00 GMT+0 - Resolved - Decoding of Auth Tokens is not working. Type: Incident

Affected Components:

<p><small>May <var data-var='date'> 7</var>, <var data-var='time'>08:30:00</var> GMT+0</small><br><strong>Resolved</strong> - Decoding of Auth Tokens is not working..</p> ]]> Wed, 7 May 2025 08:30:00 +0000 https://become1.instatus.com/incident/cmadqs9st000j3gsq30ajuvc6 https://become1.instatus.com/incident/cmadqs9st000j3gsq30ajuvc6 Request latencies are higher than ususal Type: Incident Duration: 20 hours and 32 minutes Affected Components: API, App Jun 7, 12:01:00 GMT+0 - Identified - We identified the issue and are continuing to work on a fix for this incident. Jun 7, 17:50:38 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jun 8, 08:32:54 GMT+0 - Resolved - All issues have been resolved Type: Incident

Duration: 20 hours and 32 minutes

Affected Components: ,

<p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>12:01:00</var> GMT+0</small><br><strong>Identified</strong> - We identified the issue and are continuing to work on a fix for this incident..</p> <p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>17:50:38</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>08:32:54</var> GMT+0</small><br><strong>Resolved</strong> - All issues have been resolved .</p> ]]> Fri, 7 Jun 2024 12:01:00 +0000 https://become1.instatus.com/incident/clx4n08sb59065b9odn6mq80gl https://become1.instatus.com/incident/clx4n08sb59065b9odn6mq80gl Loading of flex invoices takes longer than expected Type: Incident Duration: 4 hours and 10 minutes Affected Components: App May 6, 09:49:00 GMT+0 - Identified - We are working on a fix and will be back to normal performance shortly. May 6, 09:59:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. May 6, 13:59:00 GMT+0 - Resolved - We resolved the issue. Further monitoring is active to prevent this to happen again. Type: Incident

Duration: 4 hours and 10 minutes

Affected Components:

<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>09:49:00</var> GMT+0</small><br><strong>Identified</strong> - We are working on a fix and will be back to normal performance shortly..</p> <p><small>May <var data-var='date'> 6</var>, <var data-var='time'>09:59:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>May <var data-var='date'> 6</var>, <var data-var='time'>13:59:00</var> GMT+0</small><br><strong>Resolved</strong> - We resolved the issue. Further monitoring is active to prevent this to happen again..</p> ]]> Mon, 6 May 2024 09:49:00 +0000 https://become1.instatus.com/incident/clwhn9pnj57245bcn1v7ik6bg0 https://become1.instatus.com/incident/clwhn9pnj57245bcn1v7ik6bg0