Add rate limiting to mitigate bot-triggered autoscaling

未关闭
#57 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
冷清

调研方向

No source files or tests are named. Start by inspecting the Render service configuration and autoscaling settings, then compare the available rate-limiting options mentioned in the issue; done means an agreed mitigation is configured and burst traffic no longer causes unnecessary autoscaling.

由索引模型根据 Issue 内容生成。

描述

Summary

Render logs from 2026-03-26 show automated scraping from a single IP (178.22.106.230) causing burst traffic patterns that likely triggered the autoscaler to scale up to 2 instances on March 25.

Evidence

  • Spoofed user-agent: Claims Chrome 130 on Nexus 5 / Android 6.0 — a 2013 device on an unsupported OS. Almost certainly a bot.
  • Burst pattern: ~13 requests in 10 seconds, then ~20+ requests in 2 minutes from the same IP.
  • Autoscale event: Render scaled from 1 → 2 instances on March 25 at 3:39 PM, likely triggered by similar burst traffic.
  • Additional scanner traffic observed from Censys (CensysInspect/1.1) and two IPs with identical unusual user-agents (Firefox 120 on 32-bit Linux).

Impact

  • Unnecessary autoscaling costs on Render Starter plan
  • No actual performance or availability issue — response times remained 3-15ms

Suggested mitigations

  • Add rate limiting (e.g., Render's built-in rate limiting, or Cloudflare in front)
  • Consider bot detection / user-agent filtering for obviously spoofed clients
  • Review Render autoscaling thresholds to avoid scaling on low-volume bot bursts
主要语言
TypeScript
星标
1.6k
派生
202
PR 合并指标
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

CopilotKit/OpenGenerativeUI 的其他 Issue

查看 CopilotKit/OpenGenerativeUI 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。