The translation was automatically locked due to following alerts: Could not merge the repository.
Loading…
None
String updated in the repository |
Things to check
Glossary
English | Spanish | ||
---|---|---|---|
No related strings found in the glossary. |
Loading…
None
String updated in the repository |
English | Spanish | ||
---|---|---|---|
No related strings found in the glossary. |
>
> This could be "good" in that your site has become more popular and it simply needs some improvements to respond to more readers - check your site analytics for a long-term pattern in growth. Contact your webmaster or hosting provider for guidance. Many popular blogging and Content Management Systems (CMS) platforms (Joomla, Wordpress, Drupal...) have plugins to help cache your website locally and integrate [Content Delivery Networks](https://en.wikipedia.org/wiki/Content_delivery_network), which can dramatically improve site performance and resilience. Many of the solutions below can also help performance problems as well.
>
> If you are experiencing a severe **performance problem**, your site may be the victim of a [**"distributed denial of service" attack**](https://ssd.eff.org/en/glossary/distributed-denial-service-attack) (or DDoS). Follow the steps below to mitigate such an attack:
>
> - Step 1: Contact a trusted person who can help with your website (your webmaster, the people who helped you set up your site, your internal staff or your hosting provider).
>
> - Step 2: Work with the company you bought your domain name from and change the "Time to Live" or TTL to 1 hour (you can find instructions on how to do it on the websites of many providers, like [Network Solutions](http://www.networksolutions.com/support/how-to-manage-advanced-dns-records/) or [GoDaddy](http://support.godaddy.com/help/article/680/managing-dns-for-your-domain-names)). This can help you redirect your site much faster once it comes under attack (the default is 72 hours, or three days). This setting will often be found in the "advanced" properties for your domain, sometimes part of the SRV or Service records.
>
> - Step 3: Move your site to a DDoS mitigation service. To start:
>
> - [Deflect.ca](https://deflect.ca/)
> - [Google's Project Shield](https://projectshield.withgoogle.com/landing)
> - [CloudFlare's Project Galileo](https://www.cloudflare.com/galileo)
>
> For a full list of trusted organizations that can help mitigate a DDoS attack, jump [to the final section of this workflow that addresses DDoS attacks](../ddos_end).
>
> - Step 4: As soon as you have regained control, review your needs and decide between a secure hosting provider or simply continuing with your DDoS mitigation service.