Betty Blocks Outage History

Betty Blocks is up right now

Betty Blocks had 30 outages in the last 2 years totaling 95h 8m of downtime — averaging 1.2 incidents per month.

There were 30 Betty Blocks outages since May 31, 2024 totaling 95h 8m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.bettyblocks.com

Critical March 26, 2026

Major outage on CA4

Detected by Pingoru
Mar 26, 2026, 02:47 PM UTC
Resolved
Mar 26, 2026, 10:52 AM UTC
Duration
Timeline · 1 update
  1. resolved Mar 26, 2026, 02:47 PM UTC

    Affected Components: All Betty Blocks endpoints were unreachable between 11:52 AM and 12:06 PM CET.

Read the full incident report →

Minor February 17, 2026

Degraded performance on NL3

Detected by Pingoru
Feb 17, 2026, 12:22 PM UTC
Resolved
Feb 17, 2026, 01:05 PM UTC
Duration
43m
Affected: Classic Background Actions
Timeline · 2 updates
  1. identified Feb 17, 2026, 12:22 PM UTC

    We are writing to inform you about a temporary period of degraded performance you may currently be experiencing on our platform. Our team is aware of this issue and is actively working to identify and resolve it as quickly as possible. During this time, you may experience slower loading times, occasional delays in processing, or intermittent responsiveness in certain areas of the platform. The following zones and components are currently affected: Affected Zones: NL3: West europe cluster - Users in this geographic region may experience increased latency. Affected Components: Expression resolving: Classic expressions - You may notice an increased amount of expressions trying to resolve themselves at a slower rate. We understand that degraded performance can be frustrating, and we sincerely apologize for any inconvenience this may cause to your workflow. Our engineers are working diligently to pinpoint the root cause and implement the necessary fixes.

  2. resolved Feb 17, 2026, 01:05 PM UTC

    We are happy to announce that the outage affecting the zone NL3 has now been fully resolved, and all services are back online. Thank you so much for your patience and understanding during this challenging time. We know this disruption was significant, and we truly appreciate your support. Our team is now conducting thorough checks to ensure the stability and performance of the platform. If you experience any further issues, please do not hesitate to contact our support team via the chat, or at [email protected]

Read the full incident report →

Minor February 16, 2026

Degraded performance on NL6

Detected by Pingoru
Feb 16, 2026, 12:47 PM UTC
Resolved
Feb 16, 2026, 04:02 PM UTC
Duration
3h 15m
Affected: Classic Background Actions
Timeline · 3 updates
  1. identified Feb 16, 2026, 12:47 PM UTC

    We are writing to inform you about a temporary period of degraded performance you may currently be experiencing on our platform. Our team is aware of this issue and is actively working to identify and resolve it as quickly as possible. During this time, you may experience slower loading times, occasional delays in processing, or intermittent responsiveness in certain areas of the platform. The following zones and components are currently affected: Affected Zones: NL6: West europe cluster - Users in this geographic region may experience increased latency. Affected Components: Expression resolving: Classic expressions - You may notice an increased amount of expressions trying to resolve themselves at a slower rate. We understand that degraded performance can be frustrating, and we sincerely apologize for any inconvenience this may cause to your workflow. Our engineers are working diligently to pinpoint the root cause and implement the necessary fixes.

  2. monitoring Feb 16, 2026, 02:35 PM UTC

    We are pleased to report that we have implemented some initial fixes that have resulted in improvements to the performance on public NL6 zone. You may notice improvement in speed regarding resolving expressions. However, we are still actively working on fully resolving the underlying issue and restoring optimal performance across all mentioned zone(s) and component(s). We will continue to monitor the situation closely and provide further updates as needed.

  3. resolved Feb 16, 2026, 04:02 PM UTC

    We are happy to inform you that the performance issues on the NL6 zone have now been fully resolved. Our team has implemented the necessary fixes, and you should now be experiencing normal performance across all zones and components. Thank you for your patience and understanding during this period. We appreciate your support. If you continue to experience any performance issues, please do not hesitate to contact our support team via the support chat, or at [email protected].

Read the full incident report →

Notice November 27, 2025

Notice: Shai Hulut v2

Detected by Pingoru
Nov 27, 2025, 02:53 PM UTC
Resolved
Nov 27, 2025, 02:53 PM UTC
Duration
Affected: My Betty Blocks portalAPIAPIAPIAPIAPIAPIAPIAPIAPIAPIAPIAPIAPIAPIAPIAPIIDEBlock StoreIDEPagesIDEIDEIDEIDEIDEIDEPagesPagesDataAPIPagesPagesPagesPagesPagesPagesIDEIDEIDEIDEIDEDataAPIDataAPIActionsAPIDataAPIDataAPIDataAPIDataAPIDataAPIIDEDataAPIPagesPagesPagesPagesPagesActionsAPIActionsAPIIDEActionsAPIActionsAPIActionsAPIActionsAPIActionsAPIPagesActionsAPIDataAPIDataAPIDataAPIDataAPIDataAPIActionsAPIActionsAPIActionsAPIActionsAPIActionsAPIActionsAPI
Timeline · 1 update

Read the full incident report →

Minor November 25, 2025

Degraded performance on NL1

Detected by Pingoru
Nov 25, 2025, 01:02 PM UTC
Resolved
Nov 25, 2025, 01:20 PM UTC
Duration
18m
Timeline · 2 updates
  1. investigating Nov 25, 2025, 01:02 PM UTC

    We are writing to inform you about a temporary period of degraded performance which you may have experienced on our platform. Our team is aware of this issue and has taken immediate action to resolve this as soon as we could. During this time, you may have experienced slower loading times, occasional delays in processing, or intermittent responsiveness in certain areas of the platform. The following zones and components were affected: Affected Zones: - NL1 Affected Components: Classic Endpoints & Classic Backoffice records: Users are having trouble uploading or retrieving files or assets from their applications. We understand that degraded performance can be frustrating, and we apologise for any inconvenience this may have caused to your workflow. Thank you for your patience and understanding.

  2. resolved Nov 25, 2025, 01:20 PM UTC

    We are happy to inform you that the performance issues on the NL1 zone have been fully resolved. Our team has implemented the necessary fixes, and you should now be experiencing normal performance across all zones and components. Thank you for your patience and understanding during this period. We appreciate your support. If you continue to experience any performance issues, please do not hesitate to contact our support team via Intercom.

Read the full incident report →

Major October 6, 2025

Partial outage for Betty Blocks classic functionalities

Detected by Pingoru
Oct 06, 2025, 01:22 PM UTC
Resolved
Oct 06, 2025, 01:49 PM UTC
Duration
27m
Timeline · 3 updates
  1. investigating Oct 06, 2025, 01:22 PM UTC

    We are writing to inform you that our platform is currently experiencing an unexpected outage. This means that applications running on the below-mentioned zones are temporarily unavailable, and you may not be able to access our services. We understand this is disruptive, and we sincerely apologize for any inconvenience this may cause. Our team is working with the highest priority on this to identify the root cause of the issue and restore services as quickly as possible. The following zones and components are currently affected by this outage: Affected Zones: Private zone 19 Affected Components: Classic Background Actions: The Classic actions of your application may be unavailable. Classic Logs: The Classic logs of your application may be unavailable. Our highest priority is to bring our services back online as quickly and safely as possible. We have dedicated engineers working to resolve this issue.

  2. monitoring Oct 06, 2025, 01:33 PM UTC

    We have successfully restored the issues regarding Classic Background actions, Classic logs, and Classic Backoffice related functionalities. We are continuing to work urgently to bring all services back to full operation. We will provide another update within the next hour, as we monitor the behaviour of these services.

  3. resolved Oct 06, 2025, 01:49 PM UTC

    We are happy to announce that the outage affecting the zone 19 has now been fully resolved, and all services are back online. We want to thank you for your patience and understanding during this challenging time. We know this disruption was significant, and we appreciate your support. If you experience any further issues, please do not hesitate to contact our support team via Intercom.

Read the full incident report →

Notice October 3, 2025

Unable to authenticate when using the Betty Authentication Profile

Detected by Pingoru
Oct 03, 2025, 12:26 PM UTC
Resolved
Oct 02, 2025, 11:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Oct 03, 2025, 12:26 PM UTC

    We are writing to inform you that our platform was experiencing an unexpected outage. This means that applications running on the below-mentioned zones were temporarily unavailable, and you may not have been able to access our services. The following zones and components were affected by this outage: Affected Zones: - All zones are affected. Affected Components: Betty Blocks Authentication profile: runtime of the application - The functionality to log into the runtime of the application (your_application.betty.app) was unavailable. The issue has been mitigated and resolved by our Product department. All functionalities are available for use again. Thank you so much for your patience and understanding. If you experience any further issues, please do not hesitate to contact our support team via Intercom, or reach out to us via [email protected].

Read the full incident report →

Notice August 21, 2025

Custom domains being unavailable

Detected by Pingoru
Aug 21, 2025, 09:03 AM UTC
Resolved
Aug 21, 2025, 05:00 AM UTC
Duration
Timeline · 1 update
  1. resolved Aug 21, 2025, 09:03 AM UTC

    Hi, We are writing to inform you that, we have encountered an issue regarding custom domains not working as expected. We have promptly responded to this, and has resolved the issue. Allowing custom domains to behave as usual again.

Read the full incident report →

Major August 18, 2025

Betty Blocks assets failing to load on all US region zones (us2, ca4 and private zones 10, 13 and 17)

Detected by Pingoru
Aug 18, 2025, 03:30 PM UTC
Resolved
Aug 18, 2025, 05:48 PM UTC
Duration
2h 17m
Affected: IDEIDEIDEIDEIDE
Timeline · 4 updates
  1. investigating Aug 18, 2025, 03:30 PM UTC

    We are currently experiencing issues with uploaded files and public files. Some files may not load or be accessible.

  2. identified Aug 18, 2025, 03:35 PM UTC

    We have identified the issue and our team is working on a fix.

  3. monitoring Aug 18, 2025, 04:15 PM UTC

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

  4. resolved Aug 18, 2025, 05:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 18, 2025

Betty Blocks Assets failing to load

Detected by Pingoru
Aug 18, 2025, 03:30 PM UTC
Resolved
Aug 18, 2025, 03:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Aug 19, 2025, 09:52 AM UTC

    We are writing to inform you about the following: Recently, there was an issue regarding obtaining and fetching assets coming from the Betty Blocks asset domain. This caused customer applications to no longer make use of assets that are hosted on our Betty Blocks Asset domain. All applications are able to access the asset provider again.

Read the full incident report →

Major August 14, 2025

Classic Betty Blocks stylesheets failing to load on NL3 and NL4 zone

Detected by Pingoru
Aug 14, 2025, 02:57 PM UTC
Resolved
Aug 14, 2025, 03:48 PM UTC
Duration
50m
Affected: Classic EndpointsClassic Endpoints
Timeline · 4 updates
  1. investigating Aug 14, 2025, 02:57 PM UTC

    We’re currently investigating an issue causing stylesheets to fail to load on classic endpoints.

  2. identified Aug 14, 2025, 03:07 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Aug 14, 2025, 03:07 PM UTC

    We are continuing to work on a fix for this issue.

  4. resolved Aug 14, 2025, 03:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 8, 2025

Notice: Actions and Monitoring reset

Detected by Pingoru
Aug 08, 2025, 09:27 AM UTC
Resolved
Aug 08, 2025, 09:00 AM UTC
Duration
Timeline · 1 update
  1. resolved Aug 08, 2025, 09:27 AM UTC

    We are writing to inform you about an upcoming upgrade to our hosting services. As part of this upgrade, the historical metrics for your Classic Actions and Monitoring pages will be cleared. Once your actions run again for the first time after the upgrade, new metrics will begin to populate automatically. This change is required to ensure compatibility with the upgraded system and to provide improved performance moving forward.

Read the full incident report →

Minor July 4, 2025

Creating file properties does not work on NL1

Detected by Pingoru
Jul 04, 2025, 10:05 AM UTC
Resolved
Jul 07, 2025, 12:31 PM UTC
Duration
3d 2h
Timeline · 3 updates
  1. investigating Jul 04, 2025, 10:05 AM UTC

    This issue is currently being investigated.

  2. investigating Jul 04, 2025, 11:27 AM UTC

    We are writing to inform you about a temporary period of degraded performance you may currently be experiencing on our platform. Our team is aware of this issue and is actively working to identify and resolve it as quickly as possible. During this time, you may experience slower loading times, occasional delays in processing, or intermittent responsiveness in certain areas of the platform. The following zones and components are currently affected: Affected Zones: - NL1 We are still identifying the affected components. The impact appears to be minimal, so you may not notice any significant difference. We will continue to keep you updated.

  3. resolved Jul 07, 2025, 12:31 PM UTC

    We would like to inform you that the issue related to creating file properties and uploading files in your application on the NL1 zone has been mitigated. If you are still experiencing any issues with creating file properties or uploading files, please contact us at [email protected] or reach out to us via the chat.

Read the full incident report →

Major June 16, 2025

Partial Outage on NL3, NL4, and NL6

Detected by Pingoru
Jun 16, 2025, 12:43 PM UTC
Resolved
Jun 16, 2025, 02:28 PM UTC
Duration
1h 44m
Affected: DataAPIActionsAPIDataAPIDataAPIActionsAPIActionsAPI
Timeline · 4 updates
  1. investigating Jun 16, 2025, 12:43 PM UTC

    We are writing to inform you that our platform is currently experiencing an unexpected outage. This means that applications running on the below-mentioned zones can be temporarily unavailable, and you may not be able to access our services. We understand this is disruptive, and we sincerely apologize for any inconvenience this may cause. Our team is working with the highest priority on this to identify the root cause of the issue and restore services as quickly as possible. The following zones and components are currently affected by this outage: Affected Zones: - Public zone NL3 - Public zone NL4 - Public zone NL6 Affected Components: - Data API - Requesting information could result in an error. - Actions API - Attempting to compile your actions could result in an Artifact Storage Error.

  2. investigating Jun 16, 2025, 12:57 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jun 16, 2025, 02:10 PM UTC

    The Product department has successfully restored the issue regarding the partial outage on the public NL3, NL4, and NL6 zones. It is now possible to be able to compile your actions again, and your application should no longer return the error you are experiencing. Please note that this implementation might take time to take effect. We will be continuing to monitor its behaviour and will provide another update when all services are working as expected again.

  4. resolved Jun 16, 2025, 02:28 PM UTC

    We are happy to announce that the outage affecting the zone(s) NL3, NL4, and NL6 have now been fully resolved, and all services are back online. In case you experience any further issues, please do not hesitate to contact our support team via Intercom, or at [email protected].

Read the full incident report →

Minor May 19, 2025

Degraded performance on NL6 Zone, 17-05-2025

Detected by Pingoru
May 19, 2025, 12:49 PM UTC
Resolved
May 19, 2025, 12:49 PM UTC
Duration
Affected: ActionsAPI
Timeline · 1 update
  1. resolved May 19, 2025, 12:49 PM UTC

    Resolved - Hi, We are writing to inform you about a temporary period of degraded performance on the NL6 zone. During this time, you may have experienced scheduled actions that skipped or stopped running since May 17th. We understand that degraded performance can be frustrating, and we sincerely apologize for any inconvenience this may have caused to your workflow. Thank you for your patience and understanding in this matter. Kind regards, The Support Team

Read the full incident report →

Major May 15, 2025

Outage on NL4

Detected by Pingoru
May 15, 2025, 07:15 AM UTC
Resolved
May 15, 2025, 07:45 AM UTC
Duration
30m
Affected: Classic Background ActionsClassic EndpointsClassic BackofficeActionsAPI
Timeline · 2 updates
  1. identified May 15, 2025, 08:58 AM UTC

    The issue has been identified and a fix is being implemented.

  2. resolved May 15, 2025, 12:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 1, 2025

Outage on Private Zone 1

Detected by Pingoru
Apr 01, 2025, 09:37 AM UTC
Resolved
Apr 01, 2025, 10:20 AM UTC
Duration
42m
Affected: Classic Background ActionsClassic EndpointsClassic Backoffice
Timeline · 3 updates
  1. identified Apr 01, 2025, 10:01 AM UTC

    We are currently experiencing an issue that prevents applications from functioning. Backoffice functionalities and frontend runtime may be unavailable. Our team is actively working on a resolution.

  2. monitoring Apr 01, 2025, 10:06 AM UTC

    The Product department has implemented a fix to the zone. This resulted in application backoffices and frontend pages to be available again. We are monitoring the stability of the zone.

  3. resolved Apr 01, 2025, 10:20 AM UTC

    The incident has been resolved.

Read the full incident report →

Critical March 17, 2025

Bettyblocks.com Unreachable on Private Zone 10

Detected by Pingoru
Mar 17, 2025, 07:21 PM UTC
Resolved
Mar 17, 2025, 04:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Mar 17, 2025, 07:21 PM UTC

    Earlier today, bettyblocks.com on Private Zone 10 experienced an outage, displaying a 503 status code and the message “This website is under heavy load.” The issue resolved itself within 15 minutes without intervention. We are continuing to monitor for any further disruptions.

Read the full incident report →

Critical March 17, 2025

File upload outage.

Detected by Pingoru
Mar 17, 2025, 12:08 PM UTC
Resolved
Mar 17, 2025, 08:00 AM UTC
Duration
Timeline · 1 update
  1. resolved Mar 17, 2025, 12:08 PM UTC

    We experienced an outage with file uploads via the Backoffice and frontend across all Betty Blocks zones. Attempts to upload files resulted in connection errors due to an issue with our assets provider. This issue has now been fully resolved, and file uploads are functioning as expected. We apologize for any inconvenience and appreciate your patience

Read the full incident report →

Minor March 14, 2025

NoSuchKey Error on uploaded files

Detected by Pingoru
Mar 14, 2025, 04:18 PM UTC
Resolved
Mar 11, 2025, 11:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Mar 14, 2025, 04:18 PM UTC

    Due to a bug with our assets provider, you may experience issues with recently uploaded files. This issue only occurs when a file is deleted and immediately re-uploaded, for example regenerating a PDF via the back office or a Betty5 action. This may cause the upload to fail and result in a NoSuchKey error. We have implemented a fix to prevent this issue from recurring. To resolve this issue for existing files, please re-upload or regenerate the file. We sincerely apologize for any inconvenience this may cause. Thank you for your understanding.

Read the full incident report →