System IP addresses

GAMEMONITORING uses these IP addresses to check game servers and deliver Webhook requests to your system.

Add them to your allowlist if your server, website, WAF, CDN, or bot protection limits incoming requests.

• the game server accepts requests only from allowed addresses;
• the Webhook handler is protected by a firewall, WAF, or Cloudflare;
• bot protection blocks automated requests;
• the hosting provider asks for IP addresses for network rules.

Webhook example: your handler is located at https://panel.example.com/gamemonitoring-webhook and the domain is protected by Cloudflare. Add GAMEMONITORING IP addresses to the allowlist for this domain or exact path so Cloudflare does not show a challenge and does not block Webhook POST requests.

Game server example: the firewall allows the query port only from trusted addresses. Add GAMEMONITORING IP addresses to the rule for the query port, otherwise monitoring will not be able to check online status and server state reliably.

Pass the IP addresses from the list above to your system administrator or hosting provider. The rule must allow incoming requests from these addresses to your game server or Webhook handler.

If the rule is path-based, limit it to the required endpoint, for example /gamemonitoring-webhook. If the rule is port-based, specify only the game query port or the web-server port that receives Webhook.

After changing the rules, send a test request or test Webhook and check that the request is no longer blocked.

If the check fails, inspect firewall, WAF, or Cloudflare logs. The logs should show source IP, request path, and block reason. That tells you whether the domain, path, port, or rule order is missing.

If the Webhook handler is behind Cloudflare, add GAMEMONITORING IP addresses to a rule that skips WAF checks for these requests:

1. Log in to the Cloudflare dashboard.
2. Select the required domain.
3. Open Security.
4. Select WAF.
5. Open Custom rules.
6. Click Create rule.
7. Set a clear rule name, for example Allow GAMEMONITORING.
8. In Field, select IP Source Address.
9. In Operator, select is in.
10. In Value, add the IP addresses from the list above.
11. In Choose action, select Skip.
12. In WAF components to skip, select the checks that block requests to your handler.
13. In Select order, select First.
14. Click Deploy.

If requests are still blocked after setup, check firewall or Cloudflare logs and make sure the rule applies to the correct domain and handler path.