Github runner flagged as a scanner

[Björn Wedell]

We have seen situations where our status check job in a github actions workflow failed to report the status to Statuspage.io. The response from status page says something like this:

Your IP address <github runner IP-adress> has been flagged as a scanner. Scanners are not permitted. If you are seeing this message in error, please contact us at https://support.atlassian.com/contact.

I suppose this might be caused by a lot of actions reporting status, or perhaps github actions actually used for scanning. The range of IP-adresses used by github actions (executed on azure data centers) is updated once a week or so (https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners#ip-addresses), but apparently that is not enough.

Using a self-hosted runner is not a good option, since this would bring us back to maintaining our own statuspage machine, which was the reason moving to Statuspage in the first place.

[Rafael Meira]

Hey Bjorn! Happy to assist.

It is possible that the IP address of your GitHub Actions runner is being flagged as a scanner because it is making too many requests to the StatusPage.io API in a short period of time. This can happen if your GitHub Actions workflow is set up to run very frequently or if it is making multiple requests to the API for each run.

One way to avoid this issue is to implement rate limiting in your script or program that makes requests to the StatusPage.io API. This means adding a delay between requests or limiting the number of requests that are made within a certain time period. This can help prevent your IP address from being flagged as a scanner.

Alternatively, you could consider using a different IP address for your script or program to make requests to the StatusPage.io API. One way to do this would be to use a proxy server or a VPN service, which can route your requests through a different IP address. This can help to avoid the issue of your IP address being flagged as a scanner.

It is also worth considering reaching opening a formal ticket with our support team to see if they can provide any additional guidance or assistance with this issue. 

Let us know if you have any further questions.

Best,