become.1 GmbH - Notice history

All systems operational

Website - Operational

100.0% uptime
May 2025 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2025
Jun 2025
Jul 2025

App - Operational

100.0% uptime
May 2025 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2025
Jun 2025
Jul 2025

API - Operational

99.89% uptime
May 2025 · 100.0%Jun · 100.0%Jul · 99.67%

Previous page

Next page

May 2025
Jun 2025
Jul 2025

Notice history

View current status

Jul 2025

Invalid vouchers
ResolvedPartial outage24 hours 29 minutes
  • ResolvedUTC

    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.

  • IdentifiedUTC

    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.

  • InvestigatingUTC

    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.

Jun 2025

AWS Account Blocked Due to High Email Bounce Rate
Resolved40 hours 21 minutes
  • ResolvedUTC

    This incident has been resolved. We will closely monitor the service to prevent this from happening again.

  • MonitoringUTC
    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.

May 2025

Phishing Warning Triggered by Default Firebase Auth Domain
Resolved94 hours 56 minutes
  • ResolvedUTC

    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.

  • MonitoringUTC

    Issue was solved and tested on our test environments. Waiting for external actions to deploy the solution to production.

  • IdentifiedUTC

    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).
    Use of Firebase’s shared default domain, which is occasionally flagged due to misuse by other applications.

MAY7
Authentication via Firebase is not Working in the become1 App
ResolvedMaintenance
  • ResolvedUTC

    Decoding of Auth Tokens is not working.

Previous

May 2025 to Jul 2025

Next