When content on your website changes, your purge setup will take care of refreshing external caching systems and CDNs.
Status
Purgers
Drupal Varnish 0
Drupal Varnish 1
Next Varnish 0
Next Varnish 1
AE Next Varnish 0
AE Next Varnish 1
You have more than 3 purgers active on one system. This introduces the risk of congesting Drupal as multiple purgers are clearing external caches. It is highly recommended is to simplify your caching architecture if possible.
Capacity
40
Your system can invalidate 40 items when you're processing through webserver-initiated requests. Under ideal conditions - for example via Drush - the capacity would be 100.
Queuers
Drush p:queue-add
Core tags queuer
Purge block(s)
You have multiple queuers populating the queue.
Page cache max age
1 hour
TTL settings under 24 hours are dangerous, as sudden traffic increases will quickly reach your webserver(s) and can make Drupal slow.
Processors
Drush p:queue-work
Drush p:invalidate
Cron processor
Late runtime processor
Purge block(s)
You have multiple processors working the queue.
Queue size
0
Your queue is empty!
Configure logging behavior
Cache Invalidation

Each layer of caching on top of your site is cleared by a purger. Purgers are provided by third-party modules and support one or more types of cache invalidation.

Caching layer Path U Tag P R Url E D
Drupal Origin     Supported          
    Supported          
    Supported          
    Supported          
    Supported          
    Supported          
    Supported          
               
Public Endpoint                

The queue holds items that need refreshing, hold your mouse over the column titles for more details.

Queuers Queue Processors