Builder.io Outage History
5 incidents recorded over the last 365 days, 5 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Builder.io Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 1, 2026 | Issues Creating New Branches for ProjectsThe issue affecting new branch creation in Projects has been resolved. New branches are being created normally, and the service remains stable. | 38 min | Resolved |
| Aug 21, 2026 | Slightly elevated Content API latencyThis incident has been resolved. Content API p99 latency remains at normal levels, and the service is operating normally. | 2h 20m | Resolved |
| Mar 20, 2026 | Investigating elevated p99 latencyThis incident has been resolved. | 8h 0m | Resolved |
| Mar 17, 2026 | Service Distruption affecting ProjectsThis incident has been resolved. The issue affecting the creation of new branches and Projects, along with Projects that have been inactive for more than 2 hours, is no longer impacting users. All Projects and branches… | 1h 2m | Resolved |
| Dec 4, 2025 | Performance Degradation for Projects due to Upstream ProviderThe issue with the upstream provider has been fully resolved. System performance has returned to normal, and all affected services are operating as expected. | 2h 8m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Builder.io incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Builder.io Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Builder.io acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Builder.io outage in this window ran 8h, against a mean recovery of 2h 50m. If you depend on Builder.io in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.