# HTTP 508 Loop Detected (Resource Limit Is Reached)

**Code:** `508` · **Category:** HTTP · **Seen on:** REST API

Either the server detected an infinite loop (WebDAV) or — much more often — a cPanel/CloudLinux host is saying your account hit its resource limits.

## Meaning

On shared hosting, “508 Resource Limit Is Reached” means LVE limits (entry processes, CPU, memory) were exceeded: too many simultaneous PHP processes, a traffic spike, bots, or slow plugins. In WebDAV, 508 means a bind/collection loop.

## Common causes

- Shared hosting entry-process (EP) limit reached by concurrent requests
- Bots/crawlers or an attack flooding the site
- Slow PHP (heavy plugins, no caching) holding processes
- WebDAV collection binding to itself

## Quick fix

1. Enable page caching so PHP runs less
2. Block abusive bots (Cloudflare, robots, rate limits)
3. Check cPanel → Resource Usage and upgrade the plan if legitimate

## Detailed fix by platform

### WordPress

1. 

```bash
# install a page-cache plugin and limit heartbeat/cron
define('DISABLE_WP_CRON', true);   // run wp-cron from a real cron job instead
```


### Apache

1. 

```apache
# .htaccess: block a bad bot by user agent
RewriteCond %{HTTP_USER_AGENT} (BadBot|AhrefsBot) [NC]
RewriteRule .* - [F,L]
```


## How to diagnose

1. **Usage** — cPanel Resource Usage graphs (EP, CPU, PMEM)
2. **Traffic** — Access logs for bursts/bots
3. **Slow pages** — Which URLs take longest?

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/http/508-loop-detected)