Builder.io Outage History

Builder.io is up right now

Builder.io had 11 outages in the last 2 years totaling 24h 3m of downtime — averaging 0.5 incidents per month.

There were 11 Builder.io outages since August 28, 2025 totaling 24h 3m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.builder.io

Minor August 21, 2026

Slightly elevated Content API latency

Detected by Pingoru
Aug 21, 2026, 04:11 PM UTC
Resolved
Aug 21, 2026, 06:31 PM UTC
Duration
2h 20m
Affected: Content Delivery APIs
Timeline · 3 updates
  1. investigating Aug 21, 2026, 04:11 PM UTC

    We’re investigating slightly elevated p99 latency affecting the Content API. The API remains operational, but a small percentage of requests may take longer than usual. We’ll provide another update as more information becomes available.

  2. monitoring Aug 21, 2026, 05:47 PM UTC

    Content API p99 latency has returned to normal levels. We’re monitoring the service to ensure it remains stable.

  3. resolved Aug 21, 2026, 06:31 PM UTC

    This incident has been resolved. Content API p99 latency remains at normal levels, and the service is operating normally.

Read the full incident report →

Minor March 20, 2026

Investigating elevated p99 latency

Detected by Pingoru
Mar 20, 2026, 01:42 PM UTC
Resolved
Mar 20, 2026, 09:42 PM UTC
Duration
8h
Affected: Content Delivery APIs
Timeline · 6 updates
  1. investigating Mar 20, 2026, 01:42 PM UTC

    p99 latency is elevated across the Content API

  2. identified Mar 20, 2026, 03:14 PM UTC

    We have identified a likely cause of the elevated p99 latency affecting the Content API. Customers may be experiencing slow API responses and timeouts/errors. Our team is actively investigating and working on a fix. We will provide another update as soon as we have more information.

  3. monitoring Mar 20, 2026, 04:53 PM UTC

    We have identified that the elevated p99 latency on the Content API was caused by latency introduced by our upstream database provider. We are actively monitoring performance and will provide another update as soon as we have more information.

  4. identified Mar 20, 2026, 06:49 PM UTC

    We have determined that the elevated p99 latency on the Content API is caused by an issue with our upstream database provider. We are actively working with them to resolve the issue and will provide another update as soon as we have more information.

  5. identified Mar 20, 2026, 08:49 PM UTC

    We are still working with our upstream database provider to resolve the elevated p99 latency on the Content API. We will share another update as soon as information is available.

  6. resolved Mar 20, 2026, 09:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 17, 2026

Service Distruption affecting Projects

Detected by Pingoru
Mar 17, 2026, 07:17 PM UTC
Resolved
Mar 17, 2026, 08:20 PM UTC
Duration
1h 2m
Affected: Projects
Timeline · 5 updates
  1. investigating Mar 17, 2026, 07:17 PM UTC

    We are currently investigating an issue affecting the initialization of new branches and Projects, as well as Projects that have not been active in the past 2 hours. Affected users may experience delays or failures when attempting to load or run these Projects. Our engineering team is actively investigating the root cause.

  2. identified Mar 17, 2026, 07:54 PM UTC

    We have identified the root cause of the issue affecting the creation of new branches and Projects, along with Projects that have been inactive for more than 2 hours. Our engineering team is actively working on a fix. We will continue to provide updates as progress is made.

  3. monitoring Mar 17, 2026, 08:02 PM UTC

    A fix has been deployed for the issue affecting the creation of new branches and Projects, along with Projects that have been inactive for more than 2 hours. We are seeing Projects and branches functioning as expected and are actively monitoring the results. If you are still experiencing issues, please try again in a few minutes. We will provide a final update once the incident is fully resolved.

  4. monitoring Mar 17, 2026, 08:07 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Mar 17, 2026, 08:20 PM UTC

    This 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 are functioning as expected. We apologize for any inconvenience this may have caused. If you continue to experience any issues, please reach out to our support team.

Read the full incident report →

Minor December 4, 2025

Performance Degradation for Projects due to Upstream Provider

Detected by Pingoru
Dec 04, 2025, 06:27 PM UTC
Resolved
Dec 04, 2025, 08:36 PM UTC
Duration
2h 8m
Affected: ProjectsFly.io Machines API
Timeline · 3 updates
  1. identified Dec 04, 2025, 06:27 PM UTC

    We are currently experiencing performance degradation due to issues with an upstream provider. This may impact the responsiveness or availability of certain Cloud Projects. Our team is actively monitoring the situation and we will provide updates as more information becomes available.

  2. monitoring Dec 04, 2025, 07:46 PM UTC

    The upstream provider has implemented a fix for the issue causing performance degradation. We are closely monitoring the situation to ensure full stability. We will continue to provide updates as needed.

  3. resolved Dec 04, 2025, 08:36 PM UTC

    The issue with the upstream provider has been fully resolved. System performance has returned to normal, and all affected services are operating as expected.

Read the full incident report →

Major October 20, 2025

Upstream incident reported

Detected by Pingoru
Oct 20, 2025, 03:47 PM UTC
Resolved
Oct 20, 2025, 04:13 PM UTC
Duration
25m
Affected: AWS cloudfront
Timeline · 3 updates
  1. identified Oct 20, 2025, 03:47 PM UTC

    An upstream incident impacting our platform has been reported. The issue is related to AWS experiencing severe issues: https://health.aws.amazon.com/health/status

  2. identified Oct 20, 2025, 03:51 PM UTC

    The issue is related to AWS experiencing some issues: https://health.aws.amazon.com/health/status

  3. resolved Oct 20, 2025, 04:13 PM UTC

    We have implemented a temporary workaround to avoid the service which has the AWS dependency to avoid the AWS outages.

Read the full incident report →

Major October 2, 2025

Elevated Content API latency

Detected by Pingoru
Oct 02, 2025, 10:16 PM UTC
Resolved
Oct 02, 2025, 10:31 PM UTC
Duration
14m
Affected: Content Delivery APIs
Timeline · 2 updates
  1. identified Oct 02, 2025, 10:16 PM UTC

    We have identified an increase in latency from our Google Firestore database cluster. Customers may be seeing elevated instances of 429 responses.

  2. resolved Oct 02, 2025, 10:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 29, 2025

Elevated Latency on some Content API calls

Detected by Pingoru
Sep 29, 2025, 10:09 PM UTC
Resolved
Sep 29, 2025, 10:31 PM UTC
Duration
21m
Affected: Content Delivery APIs
Timeline · 2 updates
  1. investigating Sep 29, 2025, 10:09 PM UTC

    We are currently investigating this issue.

  2. resolved Sep 29, 2025, 10:31 PM UTC

    Read latency on the primary caching infrastructure became elevated and latency increased as traffic was gradually failed over to backup caching infrastructure.

Read the full incident report →

Minor September 15, 2025

New Fusion Projects failing to start

Detected by Pingoru
Sep 15, 2025, 03:39 PM UTC
Resolved
Sep 15, 2025, 05:00 PM UTC
Duration
1h 20m
Affected: ProjectsFly.io Machines API
Timeline · 2 updates
  1. identified Sep 15, 2025, 03:39 PM UTC

    A DNS issue with our infrastructure provider is preventing new Projects from being launched.

  2. resolved Sep 15, 2025, 05:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 8, 2025

Content API partial outage

Detected by Pingoru
Sep 08, 2025, 12:22 PM UTC
Resolved
Sep 08, 2025, 01:16 PM UTC
Duration
54m
Affected: Content Delivery APIs
Timeline · 3 updates
  1. investigating Sep 08, 2025, 12:22 PM UTC

    We are currently investigating this issue.

  2. monitoring Sep 08, 2025, 12:59 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Sep 08, 2025, 01:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 8, 2025

Projects: Service disruption

Detected by Pingoru
Sep 08, 2025, 07:56 AM UTC
Resolved
Sep 08, 2025, 11:53 AM UTC
Duration
3h 56m
Affected: Projects
Timeline · 2 updates
  1. identified Sep 08, 2025, 07:56 AM UTC

    We are experiencing an issue with one of our upstream providers.

  2. resolved Sep 08, 2025, 11:53 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 28, 2025

Builder Platform Service Disruption

Detected by Pingoru
Aug 28, 2025, 08:24 PM UTC
Resolved
Aug 28, 2025, 11:41 PM UTC
Duration
3h 17m
Affected: Content Delivery APIsGoogle Cloud Platform Cloud Filestore
Timeline · 7 updates
  1. investigating Aug 28, 2025, 08:24 PM UTC

    We are currently investigating a service disruption impacting the Content API service. Users may experience elevated error rates at this time. Our engineering team is actively working to identify the root cause. We will provide an update as soon as more information is available.

  2. investigating Aug 28, 2025, 08:39 PM UTC

    We are still actively investigating an incident that is impacting the Builder platform as a whole, including the Content API and related services. Our engineering team is actively working to identify the root cause and will provide updates as more information becomes available.

  3. identified Aug 28, 2025, 09:12 PM UTC

    We have identified the issue impacting the Builder platform, including the Content API and related services, and have taken steps toward recovery. Most services are now operational, though some customers may still experience intermittent issues. We will continue monitoring closely until full recovery is confirmed.

  4. identified Aug 28, 2025, 09:41 PM UTC

    We have identified the issue affecting the Builder platform as stemming from problems with an upstream provider. Our team is working with the provider to mitigate the impact. We will continue to share updates as more information becomes available.

  5. monitoring Aug 28, 2025, 10:14 PM UTC

    The Google Cloud Firestore team has addressed the underlying issue which caused the performance degradation. Traffic is now healthy across the site and APIs.

  6. monitoring Aug 28, 2025, 10:15 PM UTC

    We are continuing to monitor for any further issues.

  7. resolved Aug 28, 2025, 11:41 PM UTC

    The issue impacting the Builder platform has been fully resolved. All services are now operating normally.

Read the full incident report →