{
  "meta": {
    "version": "v1",
    "pricing": {
      "public": {
        "label": "Public",
        "description": "Read-only API access for lightweight status checks and public integrations."
      },
      "premium": {
        "label": "Premium",
        "description": "API keys with higher hourly quotas, plus Slack, Teams, Discord, webhook, and email outage alerts across your vendor stack."
      }
    },
    "generatedAt": "2026-11-18T20:16:12.546Z"
  },
  "data": {
    "id": "incident_statuspage_frontegg_ts0y74x7qr9s",
    "slug": "frontegg-api-are-having-performance-degradation-2022-08-14",
    "title": "Api are having Performance degradation",
    "summary": "Api are having Performance degradation",
    "status": "resolved",
    "stale": false,
    "severity": "minor",
    "startedAt": "2022-08-14T23:54:50.612+00:00",
    "updatedAt": "2022-08-16T12:05:21.362+00:00",
    "resolvedAt": "2022-08-15T00:39:35.893+00:00",
    "provider": {
      "slug": "frontegg",
      "name": "Frontegg"
    },
    "affectedServices": [],
    "links": {
      "html": "/incidents/frontegg-api-are-having-performance-degradation-2022-08-14",
      "api": "/api/v1/incidents/frontegg-api-are-having-performance-degradation-2022-08-14",
      "providerHtml": "/providers/frontegg",
      "alerts": "https://outagedeck.com/account?stack=frontegg&utm_source=api&utm_medium=response&utm_campaign=api_alerts&utm_content=incident"
    },
    "impactSummary": "Frontegg reported this event with no impact level.",
    "source": {
      "id": "source_frontegg_status",
      "kind": "official_api",
      "name": "Frontegg Status",
      "checkedAt": "2026-11-18T20:10:14.846+00:00",
      "stale": false,
      "officialUrl": "https://status.frontegg.com",
      "statusPageUrl": "https://status.frontegg.com"
    },
    "updates": [
      {
        "id": "update_statuspage_frontegg_ts0y74x7qr9s_d2hwvq17vqtv",
        "status": "investigating",
        "body": "We are currently investigating this issue.",
        "createdAt": "2022-08-14T23:54:50.657+00:00"
      },
      {
        "id": "update_statuspage_frontegg_ts0y74x7qr9s_l8lr242xvhyh",
        "status": "investigating",
        "body": "We are continuing to investigate this issue.",
        "createdAt": "2022-08-15T00:00:16.289+00:00"
      },
      {
        "id": "update_statuspage_frontegg_ts0y74x7qr9s_zplj0j7h264n",
        "status": "investigating",
        "body": "We are continuing to investigate this issue.",
        "createdAt": "2022-08-15T00:23:46.322+00:00"
      },
      {
        "id": "update_statuspage_frontegg_ts0y74x7qr9s_09vs49zxjj0p",
        "status": "monitoring",
        "body": "A fix has been implemented and we are monitoring the results.",
        "createdAt": "2022-08-15T00:24:03.594+00:00"
      },
      {
        "id": "update_statuspage_frontegg_ts0y74x7qr9s_l03hdjcf9709",
        "status": "resolved",
        "body": "This incident has been resolved.",
        "createdAt": "2022-08-15T00:39:35.893+00:00"
      },
      {
        "id": "update_statuspage_frontegg_ts0y74x7qr9s_l37mc5vxkjq8",
        "status": "resolved",
        "body": "### **Executive summary:**\n\nOn August 15th, 2022 at 02:01 IST \\(UTC \\+2\\) Frontegg underwent a sophisticated DDOS subdomain organized attack. The attackers used multiple servers spread across a variety of Digital Ocean IPs. Each Server executed a low number of requests per second so our WAF did not trigger rate-limiting rules, yet it was recognized that many of the paths were related to WordPress engine's known weakness. \n\nBy 03:21 the attack had been successfully mitigated. At 04:46 a second organized attack began. The restrictions put in place by the previous attack were helpful in mitigating the second attack. By 05:30 all traffic returned to normal\n\n### **Affect:**\n\nThe incident caused a degraded performance to our API gateway. As a result, our API returned 504 and 524 errors to partial traffic over the course of the incident. The majority of these errors were returned between 02:01 IST and 02:30 IST, when our mitigation efforts began to have an effect. A majority of traffic was still able to go through without error during this time.\n\n### **Mitigation and resolution:**\n\nOur initial response to the attack was to increase our rate limiting and WAF constraints. This initial step was implemented at 02:30 IST. Once we understood the level of sophistication and distribution of the attack, we implemented changes on the application level, including a different routing mechanism and added more specific WAF constraints based on origins of the attacking traffic, which took effect by 03:21 IST.\n\n### **Preventive steps:**\n\nIn order to prevent attacks like this in the future, we are implementing a more sophisticated route blocking mechanism to our API-gateway. Additionally we have reported the incident to the cloud provider which hosted a majority of the attacking traffic, and we are consulting with our WAF provider for further guidance on preventing such attacks.",
        "createdAt": "2022-08-16T12:05:05.854+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}