> For the complete documentation index, see [llms.txt](https://community.peerplays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.peerplays.com/risk-register/introduction/bunker-issue/ddos-attack.md). # DDOS Attack ## Description DDOS attack will deny the User to connect with any online services, sites, and application. This is a cyber attack and it's unpredictable. If a user come across any such circumstances, the below ideas, response plan can be helpful. ## Mitigation Ideas The following ideas are listed based on the inputs from SMEs 1. Having Load balancers in place. 2. A method to detect DDOS attack while they originate. 3. Using services like **CloudFlare** to secure the internet connectivity. 4. Limit the number of connections (Reasonable counts). 5. Direct communication with ISP NOCs. 6. Keeping the Backups servers Off-premises . 7. Find a good counter-measure software to stop/fight against the attack. ## Response Plan 1. If attack has happened, the servers can be flipped to backups. 2. Communicate with marketing team depending on the services attacked. ## Responder Team In order to find the solution / to know in details about the risk that has happened, responder team is one to be communicated first. ### First Responder Team Devops Team\ **Point of contact:** Haxhi ### Second Responder Team Development Team --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://community.peerplays.com/risk-register/introduction/bunker-issue/ddos-attack.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.