Update: Please be informed that there is no complete outage. As a proactive measure, a new Kafka broker has been provisioned and successfully attached to the existing Kafka cluster to distribute and reduce the load on the currently running brokers. There is no impact to the GCC environment at this time. We are awaiting further updates from AWS and will keep you informed accordingly.

We are working to re-route traffic to healthy zones. New resource launches are being directed away from the affected area.

A localized power issue in a specific AWS Availability Zone (mec1-az2) is affecting API stability and instance connectivity.

We are currently investigating connectivity and performance issues within the ME-CENTRAL-1 (Middle East) region.

The issue has been resolved and all services are operating normally. The disruption occurred during a planned infrastructure upgrade. We sincerely apologize for any inconvenience caused and appreciate your patience.

If you experience any further issues or have questions, please reach out to support@fareye.com.

The issue has been identified and our team is working on implementing a fix. Some users may continue to experience disruption until the resolution is fully deployed.

We are currently investigating an issue affecting the service. Our team is actively working to identify the root cause and will provide updates as more information becomes available.