Render status
What RenderSwap did for crawlers over yesterday and today, added up across every account.
Loading the render totals
The totals did not load.
No crawler requests in the last day
Nothing was rendered and nothing was handed back to an origin in this window. The totals fill in as crawlers ask for pages.
Check a pageWhat each number counts
Rendered is the number of pages a browser opened and finished for a crawler. A page that was already stored is served without a browser, so it is not counted here, and neither is a render that failed.
Fallbacks are the requests where RenderSwap did not return a rendered page, so the crawler received the page your own server sends. They add up four causes: a page that took too long, a site that blocked the browser, any other failure, and a limit that was reached (an account's monthly allowance, its plan's domain limit, or the shared render capacity).
Failure share is the timeouts plus the blocks, divided by every render that was tried. Cache hits and allowance fallbacks are not tries, so they never move it. When nothing was tried the share has no value and the page says so instead of showing zero.
The window and what is left out
Counts are kept one row per UTC day, so the window is two whole days: yesterday and today. Today's row grows until midnight UTC, which makes the first numbers of a new day small.
The scheduled run is the job that starts once a night and queues the background work: license refreshes, domain re-checks and the cache sweep. The time it last ran sits under the totals. The totals themselves come from live crawler traffic, not from that run.
The page shows no domain, page address, account or token. Every figure is a sum over all accounts.