Is Bouncer Down Right Now? Check if there is a current outage ongoing.

Hello, The incident has been finally resolved. All previously affected services (both App and BouncerShield) are up and running. Thank you so much for your patience, and we are very sorry for the inconvenience! Kind Regardd Radek

We have identified that while Bouncer App works fine, Bouncer Shield is not working properly. We are waiting for the AWS team to help.

We have implemented a temporary solution, and the application is again available to the users. We are monitoring the situation. We are very sorry for the inconvenience!

While waiting for AWS, we are exploring a temporary solution to enable the Bouncer App.

We are waiting for the AWS support team to investigate the issue. We will keep you updated.

Bouncer's App is unavailable due to AWS issue. We are working with AWS Team to get it resolved as soon as possible. No other services are affected.

Bouncer App started to experience the issues at 21:02 UTC. Due to that, the App was not available to not logged-in users. The issue was caused by AWS mistake. At 00:00 UTC, the issue has been resolved with the assistance of the AWS support team. We are currently monitoring the performance of the application. We are very sorry for the inconvenience!

The incident was resolved in 16 minutes, and the system is fully operational.

Bouncer was experiencing interim issues for SingleEmail verification within an app, and for API. Some customers integrated with API might have experienced 503 and 504 status codes for some API requests.

System is fully operational. Both when it comes to coverage and the performance.

Our product department is still resolving the root problem and determining why Spamhaus is blocking our IPs. Still, the good news is we have managed to restore the full operational efficiency of the system, so currently, Bouncer is able to verify emails of all providers. If you hit any issues, please let us know: support@usebouncer.com

Our team has been working hard to solve the issue. Situation is stabilised, however system’s capacity is still reduced.

Part of our infrastructure is unable to verify certain types of email addresses. Because of that higher than normal percentage of results with "unknown" status will be returned, and overall system throughput will be lower until this issue is resolved.

Issue has been resolved.

The system and API are stable now. The root cause has been identified. An issue with the DNS resolving library was causing one of the services to crash.

The issue has been identified and a fix is being implemented.

We are going through temporary problems with API stability, which may result in verification errors. The entire team is working on a solution as soon as possible. We will keep you updated on the progress.

This incident has been fully resolved.

Root cause has been found and eliminated. Our team will continue to monitor situation and take steps to prevent such events in the future. DNS misconfiguration caused unusually high load on our API which in turn caused it's failures. This problem has been fixed.

From 6PM UTC Bouncer's API rest endpoints returned response 503 Service Unavailable for most of the requests. Results were also affected returning higher % of unknown statuses during that time. Our team is investigating the issue.

From 5:15 to 5:17PM CEST Bouncer's API and APP rest endpoints returned response 503 Service Unavailable for most of the requests. Incident was cause by configuration error of used development framework which caused unavailability of authentication/authorisation infrastructure.

From 2:15 to 2:39PM CEST Bouncer's services returned response 503 Service Unavailable for requests related to list processing and toxicity check. Incident was cause by configuration error of used development framework which caused unavailability of services responsible of list processing.

Certificate of our vendor BlackBox expired which caused errors when uploading files to Toxicity Check functionality.

From 12:59 to 1:30PM Bouncer's API returned response 503 Service Unavailable for approximately half of the requests during that time. Incident was cause by configuration error and steps have been taken to prevent similar situations. In cases like this due to our distributed architecture retry on request with status code 503 would most likely be processed without error.