Mintlify: Updates and preview deployments being delayed
GitHub outage, Jul 21, 2026 · 15 vendors, 19 incidents
Mintlify’s incident blames GitHub as the cause. (hop 1, posted +6 h 43 min vs GitHub’s own post)
“…not able to update their docs Root Cause: Updates failed due to a hitting a rate limit on Github Time Range: 4:40 AM - 8:00 AM PST Impact: Customers were not able to update their docs Root Cause: Upda…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["GitHub<br/>posted 10:31 UTC"]:::root
before["Posted before GitHub did<br/>1 vendor, 1 blamed GitHub<br/>Semaphore"]:::blames
root --> before
h1["Within an hour<br/>2 vendors, 2 blamed GitHub<br/>HashiCorp, Terraform Cloud (HCP)"]:::blames
root --> h1
later["Later<br/>1 vendor, 1 blamed GitHub<br/>Mintlify"]:::blames
root --> later
p0["Anthropic<br/>posted −20 min, did not name GitHub"]:::timing
root -.-> p0
k0["Bolt.new, Cursor<br/>−16 min to +7 h 14 min"]:::hop2
p0 -->|"blamed Anthropic"| k0
me["Mintlify (this incident)<br/>posted +6 h 43 min"]:::me
later --- meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Affected components: Updates
Timeline of updates
- investigating
We're investigating delays or stalls in documentation updates
- resolved
Impact: Customers were not able to update their docs Root Cause: Updates failed due to a hitting a rate limit on Github Time Range: 4:40 AM - 8:00 AM PST
Impact, status and times are the vendor’s own, as last archived. View on status.mintlify.com (opens in new tab).