# Service Outage

- Provider: [Frontegg](https://down.guide/providers/frontegg)
- Confidence: Confirmed
- Impact: Partial outage
- lasted 0m
- started 2025-05-23 17:16 UTC
- eu
- Frontegg states the impact was 2025-05-23 16:53 to 17:16 UTC (23m)
- id: DWN-4df0c67a07
- Official page: https://stspg.io/c2hg1grbv4g1

## Updates from Frontegg
### 2025-05-23 17:16 UTC: resolved
This incident has been resolved.
Timeline of Events:
16:53 UTC: DDOS attack begins
16:54 UTC: Monitoring system detects service degradation and alerts the on-call team.
17:03 UTC: On-call team identifies that a DDOS attack is ongoing.
17:10 UTC: On-call team scopes the characteristics of the attack (volume, source IPs, and traffic patterns).
17:15 UTC: The on-call team applies blocking and rate limit rules on Cloudflare to mitigate the attack.
17:16 UTC: System recovers and service is restored.

### 2025-05-28 07:14 UTC: postmortem
Root Cause Analysis \\(RCA\\): DDOS Attack Incident
‌
Incident Summary
On May 23, 2025, between 16:53 to 17:16 UTC, our service in the Europe region experienced a temporary outage due to a sophisticated DDOS attack. Despite mitigation efforts by Cloudflare, the scale and speed of the attack overwhelmed our system's autoscaling capabilities, leading to service unavailability for a short period.
‌
Timeline of Events:
\* 16:53 UTC: DDOS attack begins.
\* 16:54 UTC: Monitoring system alerts the on-call team.
\* 17:03 UTC: On-call team identifies the DDOS attack.
\* 17:10 UTC: Attack characteristics scoped.
\* 17:15 UTC: Blocking and rate limit rules applied.
\* 17:16 UTC: Service recovers.
‌
Root Cause
The attack's high volume and rapid escalation exceeded our system's ability to scale automatically in time, causing service disruption.
‌
Incident Resolution & Next Steps:
To resolve the incident, we took the following actions:
\* We successfully blocked malicious traffic and hardened our defenses.
\* Preventive measures are being implemented, including enhancing CDN, infrastructure autoscaling, automated tools to identify attacks faster, and DDOS protection in collaboration with Cloudflare.

From the builder: does your app depend on Frontegg? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=frontegg) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Frontegg.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-4df0c67a07), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.