Can a Cloudflare worker fetch from multiple origins without hitting request limits or execution time constraints for our global users
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Can a Cloudflare worker fetch from multiple origins without hitting request limits or execution time constraints for our global users
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 2 queries…
Searches and sources
ChatGPT2 real searches · gpt-6
Cloudflare Workers limits subrequests CPU time wall time fetch multiple origins official docs 2026 Google ↗
Cloudflare Workers fetch concurrency limits outbound requests official documentation Google ↗
- Limits · developers.cloudflare.com
- Workers are no longer limited to 1000 subrequests · developers.cloudflare.com
- cloudflare-docs/src/content/docs/workers/wrangler/configuration.mdx at production · cloudflare/cloudflare-docs · github.com
- Metrics and analytics · developers.cloudflare.com
- Fetch · developers.cloudflare.com
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
Cloudflare Workers limits subrequests CPU time wall time fetch multiple origins official docs 2026 OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
Cloudflare Workers fetch concurrency limits outbound requests official documentation OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 |