<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:become1.instatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://become1.instatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://become1.instatus.com/history.atom"/>
  <title>become.1 GmbH Status - Incident history</title>
  <updated>2026-10-19T18:00:00.000+00:00</updated>
  <author>
    <name>become.1 GmbH</name>
  </author>
  
<entry>
  <id>tag:become1.instatus.com,2005:Maintenance/cmvfk7lez08sw0wqqlmhxi8qa</id>
  <published>2026-10-19T18:00:00.000+00:00</published>
  <updated>2026-10-19T18:42:52.735+00:00</updated>
  <link rel="alternate" type="text/html" href="https://become1.instatus.com/maintenance/cmvfk7lez08sw0wqqlmhxi8qa"/>
  <title>Partial Outage to the Leasy Feature </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 43 minutes</p>
    <p><strong>Affected Components:</strong> API</p>
    <p><small>Oct <var data-var='date'> 19</var>, <var data-var='time'>18:42:52</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Oct <var data-var='date'> 19</var>, <var data-var='time'>18:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 19</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are planning for a scheduled maintenance during that time..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:become1.instatus.com,2005:Incident/cmotnqu5e04rlm9kzweql9igd</id>
  <published>2026-05-05T14:48:00.000+00:00</published>
  <updated>2026-05-05T17:54:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://become1.instatus.com/incident/cmotnqu5e04rlm9kzweql9igd"/>
  <title>Connection issues with .de domains</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 hours and 32 minutes</p>
    <p><strong>Affected Components:</strong> API, App, Website</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:become1.instatus.com,2005:Incident/cmist6g3201111qqgik5d3qug</id>
  <published>2025-12-05T11:55:54.425+00:00</published>
  <updated>2025-12-05T13:35:14.837+00:00</updated>
  <link rel="alternate" type="text/html" href="https://become1.instatus.com/incident/cmist6g3201111qqgik5d3qug"/>
  <title>Our Website ist currently unavailable</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 39 minutes</p>
    <p><strong>Affected Components:</strong> API, App, Website</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>
<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'>11:55:54</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating the issue.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:become1.instatus.com,2005:Incident/cmi8uibo502h6xag6n01hof5v</id>
  <published>2025-11-21T11:00:00.000+00:00</published>
  <updated>2025-11-21T13:48:09.611+00:00</updated>
  <link rel="alternate" type="text/html" href="https://become1.instatus.com/incident/cmi8uibo502h6xag6n01hof5v"/>
  <title>The become1.de Website shows a fake cloudflare redirect</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 48 minutes</p>
    <p><strong>Affected Components:</strong> Website</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>
<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'>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'>11:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Please don&#039;t klick on the cloudflare banner, we&#039;re working on a fix. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:become1.instatus.com,2005:Incident/cmd7ff80g0065hdbsp5pgytz8</id>
  <published>2025-07-17T13:29:08.051+00:00</published>
  <updated>2025-07-18T13:58:31.414+00:00</updated>
  <link rel="alternate" type="text/html" href="https://become1.instatus.com/incident/cmd7ff80g0065hdbsp5pgytz8"/>
  <title>Invalid vouchers</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day and 29 minutes</p>
    <p><strong>Affected Components:</strong> App, API</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>
<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&#039;re still working to resolve the issue with automatic voucher generation. We&#039;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&#039;re in contact with our provider and are awaiting a fix to re-enable our access..</p>
<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&#039;re currently experiencing an issue with our **automatic voucher generation** feature. When you try to create vouchers, you might see an &quot;invalid PDF&quot; 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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:become1.instatus.com,2005:Incident/cmc0g428q000cks9go9h9htvz</id>
  <published>2025-06-16T22:00:00.000+00:00</published>
  <updated>2025-06-18T14:21:22.720+00:00</updated>
  <link rel="alternate" type="text/html" href="https://become1.instatus.com/incident/cmc0g428q000cks9go9h9htvz"/>
  <title>AWS Account Blocked Due to High Email Bounce Rate</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 16 hours and 21 minutes</p>
    <p><strong>Affected Components:</strong> App</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>
<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&#039;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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:become1.instatus.com,2005:Incident/cmb0r8fwi00186fs35ytd2xbn</id>
  <published>2025-05-23T07:40:00.000+00:00</published>
  <updated>2025-05-27T06:36:33.638+00:00</updated>
  <link rel="alternate" type="text/html" href="https://become1.instatus.com/incident/cmb0r8fwi00186fs35ytd2xbn"/>
  <title>Phishing Warning Triggered by Default Firebase Auth Domain</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 22 hours and 57 minutes</p>
    <p><strong>Affected Components:</strong> App</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>
<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'> 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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:become1.instatus.com,2005:Incident/cmadqs9st000j3gsq30ajuvc6</id>
  <published>2025-05-07T08:30:00.000+00:00</published>
  <updated>2025-05-07T08:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://become1.instatus.com/incident/cmadqs9st000j3gsq30ajuvc6"/>
  <title>Authentication via Firebase is not Working in the become1 App</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> App</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:become1.instatus.com,2005:Incident/clx4n08sb59065b9odn6mq80gl</id>
  <published>2024-06-07T12:01:00.000+00:00</published>
  <updated>2024-06-08T08:32:54.695+00:00</updated>
  <link rel="alternate" type="text/html" href="https://become1.instatus.com/incident/clx4n08sb59065b9odn6mq80gl"/>
  <title>Request latencies are higher than ususal</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 20 hours and 32 minutes</p>
    <p><strong>Affected Components:</strong> API, App</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>
<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'> 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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:become1.instatus.com,2005:Incident/clwhn9pnj57245bcn1v7ik6bg0</id>
  <published>2024-05-06T09:49:00.000+00:00</published>
  <updated>2024-05-06T13:59:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://become1.instatus.com/incident/clwhn9pnj57245bcn1v7ik6bg0"/>
  <title>Loading of flex invoices takes longer than expected</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 10 minutes</p>
    <p><strong>Affected Components:</strong> App</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>
<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'>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>

        ]]>
  </content>
</entry>

</feed>