<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rate-Limits on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/rate-limits/</link><description>Recent content in Rate-Limits on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 17 Sep 2026 15:22:47 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/rate-limits/index.xml" rel="self" type="application/rss+xml"/><item><title>GitLab.com rate limits go subscription-tiered starting Oct 19, 2026</title><link>https://curadevops.metacog.co.kr/insights/2026-09-17-rate-limits-on-gitlab-com-are-changing/</link><pubDate>Thu, 17 Sep 2026 15:22:47 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-17-rate-limits-on-gitlab-com-are-changing/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>CI/CD — Act:&lt;/strong> Unauthenticated GitLab.com API requests will be hard-capped at 60/hour per IP starting October 19, 2026 — automation running against paid accounts without credentials is also affected. Audit all pipelines and scripts for unauthenticated GitLab.com calls and ensure they use authenticated tokens before October 19; a preview enforcement window runs October 7 and 14.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> Rate limits will align with subscription tier (Free on October 19, Premium/Ultimate in January 2027), which may expose gaps in how teams authenticate automation or whether the org&amp;rsquo;s tier is adequate. Schedule a review of GitLab.com subscription tier and org-wide authentication standards before October 19.&lt;/li>
&lt;/ul></description></item></channel></rss>