Просмотр новости
Найдите то, что Вас интересует
Спутники
РН
SpaceX
Роскосмос
NASA
СпутникиРНSpaceXРоскосмосNASA
Hello,
We trigger CircleCI pipelines from GitHub-hosted automation using the API v2 endpoint:
POST https://circleci.com/api/v2/project/github/<org>/<repo>/pipeline
The vast majority of requests succeed, but occasionally we receive the following response:
<TITLE>ERROR: The request could not be satisfied</TITLE>
</HEAD><BODY>
<H1>403 ERROR</H1>
<H2>The request could not be satisfied.</H2>
<HR noshade size="1px">
Request blocked.
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
<BR clear="all">
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
<BR clear="all">
<HR noshade size="1px">
<PRE>
Generated by cloudfront (CloudFront)
A few observations:
The failures appear to happen randomly and are difficult to reproduce consistently.
The CircleCI token is valid and unchanged.
The same request succeeds immediately before and after the failure.
The response is HTML generated by CloudFront rather than the normal CircleCI API JSON response.
We are calling the API from GitHub-hosted runners.
In some cases there may be multiple pipeline trigger requests occurring around the same time.
When these incidents occur, the CircleCI status page reports all systems as operational and does not indicate any ongoing incident.
We recently discovered that roughly a total of 2% of our requests receive a CloudFront 403 (“Request blocked — We can’t connect to the server for this app or website at this time”).
We have a total of ~1,600 POST requests to https://circleci.com/api/v2/project/github/<org>/<repo>/pipeline over the week, ranging from ~28 requests/hour on average during working hours (07:00–19:00 UTC, Mon–Fri), with peaks reaching ~80 requests/hour.
Looking at the timestamps, the 403s are not uniformly distributed: the majority cluster between 15:40 and 19:30 UTC, which coincides with peak overlap between European and US East Coast business hours. Outside that window we see very few failures (but we also have less activity).
Our main questions are:
Does CircleCI have any documented recommendations or hard limits regarding API request rates, burst sizes, or concurrent pipeline trigger requests that customers should follow when triggering pipelines using the API?
Is there anything in our usage pattern above — 80 req/hour peak, all originating from GitHub Actions runner IPs — that would be expected to trigger CloudFront edge blocking?
Thanks.
1 post - 1 participant
Read full topic
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | Breaking Changes: Config Compilation Updates — September 21, 2026 | 0 | 14.42 | 11-06-2026 |
| 2 | Lingering apt timeouts after Ubuntu incident | 0 | 8.98 | 04-05-2026 |
| 3 | API Change: Pipeline Error Response Format Update | 0 | 9.16 | 21-09-2026 |
| 4 | CircleCI build policy enforcement - but no ability to change it without service tier upgrade? | 0 | 6.54 | 20-05-2026 |
| 5 | GitHub Webhook Secret Exposure — Action Required for GitHub OAuth Projects | 0 | 11.65 | 14-04-2026 |
| 6 | Intermittent pipeline inconsistencies when running parallel jobs with shared dependencies | 0 | 7.54 | 19-06-2026 |
| 7 | Missing docs - V2 API tests endpoint | 0 | 14.38 | 21-08-2026 |
| 8 | Post Incident Report: Oct 6, 2026 - Delays in pipelines, workflows, UI data, and notifications | 0 | 12.35 | 07-10-2026 |
| 9 | OAuth 2.0 API Access with Dynamic Client Registration | 0 | 9.68 | 12-08-2026 |
| 10 | Fix failing workflows with Claude Code, directly from the CircleCI UI | 0 | 15.94 | 06-08-2026 |