- Detected by Pingoru
- Aug 20, 2026, 01:45 PM UTC
- Resolved
- Aug 17, 2026, 03:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Aug 20, 2026, 01:45 PM UTC
We are writing to inform you about an incident which affected users making use of sending mails. During this time, you may have experienced degraded performance in sending mails originating from our MandrillApp services. The following zones and components are currently affected: Affected Zones: All zones were affected, but only customers that are/were making use of our MandrillApp mailing services were affected. Affected Components: Classic actions - Classic actions that are making use of a MandrillApp API key in order to send out mails would fail to deliver the mail. NextGen Actions - NextGen actions that are making use of a MandrillApp API key in order to send out mails would fail to deliver the mail. The issue was quickly located and a fix has been implemented for this, which allowed the incoming mails being sent to work as expected again. We would like to apologize for the degraded performance that that has been experienced, and want to thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Aug 12, 2026, 09:18 AM UTC
- Resolved
- Aug 12, 2026, 10:52 AM UTC
- Duration
- 1h 33m
Affected: APIClassic Background ActionsClassic Endpoints
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- Aug 07, 2026, 01:27 PM UTC
- Resolved
- Aug 07, 2026, 03:10 PM UTC
- Duration
- 1h 42m
Affected: WASM
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Aug 07, 2026, 08:00 AM UTC
- Resolved
- Aug 07, 2026, 08:00 AM UTC
- Duration
- —
Affected: Classic Background Actions
Timeline · 1 update
-
resolved Aug 07, 2026, 01:30 PM UTC
Hi, We are writing to inform you of an unexpected outage on our platform. Scheduled actions were not being picked up, meaning data processing within the scheduled actions flow was not carried out on the affected zones during this period. We understand this is disruptive and sincerely apologize for any inconvenience caused. Our team treated this with the highest priority, and services have now been restored. The following zones and components were affected by this outage: Affected Zones: NL3, NL4 and NL6 Affected Components: * Scheduled actions Thank you for your patience and understanding during this critical time. We appreciate your support. Kind regards, The Support Team
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2026, 03:54 PM UTC
- Resolved
- Jul 02, 2026, 03:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 02, 2026, 03:54 PM UTC
There was an issue on the Private Cloud 13 which resulted in a partial outage regarding the Actions-JS functionalities of our platform. During this time, you may have been unable to make use of our NextGen actions, unable to log in to the runtime of your application, or intermittent responsiveness in certain areas of the platform. Affected Zones: Private Cloud 13 - Users were unable to make use of NextGen action, preventhing them from logging into the platform, or make use of other actions related functionalities. Affected Components: Actions-runtime: The use of actions in the runtime of your application were experienced as unresponsive. Resulting in errors being returned and preventing any further use of the application. Our Product department has implemented the necessary fixes in order for these issues to be resolved. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2026, 10:57 AM UTC
- Resolved
- Jul 02, 2026, 09:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 02, 2026, 10:57 AM UTC
There was an issue on the Private Cloud 12 which resulted in degraded performance regarding the Actions-JS functionalities of our platform. We are writing to inform you about a period of degraded performance that was experienced on our platform. During this time, you may have experienced slower loading times, occasional delays in processing, or intermittent responsiveness in certain areas of the platform. Affected Zones: Private Cloud 12 - Users were experiencing slowness with the usage of Actions-JS functionalities. Affected Components: Actions-runtime: The use of actions in the runtime of your application could be experienced as slow, or unresponsive. Resulting in errors being returned. Our Product department has implemented the necessary fixes in order for these issues to be resolved. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2026, 10:27 AM UTC
- Resolved
- Jul 09, 2026, 12:51 PM UTC
- Duration
- 7d 2h
Affected: Classic Background ActionsClassic BackofficeIDEPagesDataAPIActionsAPI
Timeline · 5 updates
-
investigating Jul 02, 2026, 10:27 AM UTC
private zone 18 is being affected by server issues. We are currently investigating the cause.
-
monitoring Jul 02, 2026, 02:56 PM UTC
A fix has been implemented and we are monitoring the results.
-
investigating Jul 03, 2026, 08:32 AM UTC
We see a spike in CPU usage that is causing degraded performance. We restarted the affected service as a mitigation. We are continuing to investigate the root cause
-
monitoring Jul 03, 2026, 03:52 PM UTC
Currently monitoring
-
resolved Jul 09, 2026, 12:51 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 23, 2026, 02:58 PM UTC
- Resolved
- Jun 24, 2026, 07:15 AM UTC
- Duration
- 16h 17m
Affected: PagesPagesPagesPagesPagesPagesPagesPagesPagesPagesPagesPagesPagesPagesPages
Timeline · 2 updates
-
identified Jun 23, 2026, 02:58 PM UTC
We are writing to inform you about a temporary period of degraded performance you may currently be experiencing on our platform. This is due to an outage regarding the Anthropic Claude services. 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. All zones that have the option to make use of our Betty Genius may experience delays, or unresponsiveness in the creation and generation of your Betty Genius Pages. Affected Components: Betty Genius - The generation of pages based on prompts may be unavailable, or slow in response. We understand that degraded performance can be frustrating, and we sincerely apologize for any inconvenience this may cause to your workflow. The engineers are working diligently to pinpoint the root cause and implement the necessary fixes.
-
resolved Jun 24, 2026, 07:15 AM UTC
We are happy to inform you that the performance issues on all zones have been fully resolved. The Anthropic 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 chat, or reach out to us at [email protected].
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2026, 08:54 AM UTC
- Resolved
- Jun 02, 2026, 01:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 03, 2026, 08:54 AM UTC
A Degraded performance was discovered on the public NL3 zone. 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: Public zone NL3: (Europe West Server Cluster) - Users in this geographic region may experience increased latency. Affected Components: Classic Backoffice grids - You may notice data taking longer than usual to load or refresh. Classic Endpoints - Reaching out to your endpoints may not have resolved, or resolved at a slower rate. Our Product department has taken the necessary measures to ensure the stability of the platform. In case any unexpected behaviour is still experienced, please do not hesitate to reach out to us through the chat bubble, or at [email protected]
Read the full incident report →
- Detected by Pingoru
- Mar 26, 2026, 02:47 PM UTC
- Resolved
- Mar 26, 2026, 10:52 AM UTC
- Duration
- —
Timeline · 1 update
-
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 →
- Detected by Pingoru
- Mar 26, 2026, 11:03 AM UTC
- Resolved
- Mar 26, 2026, 12:17 PM UTC
- Duration
- 1h 14m
Affected: PagesIDE
Timeline · 2 updates
Read the full incident report →
- 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
-
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.
-
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.
-
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 →
- 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 →
- Detected by Pingoru
- Nov 25, 2025, 01:02 PM UTC
- Resolved
- Nov 25, 2025, 01:20 PM UTC
- Duration
- 18m
Timeline · 2 updates
-
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.
-
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 →
Critical October 29, 2025 - Detected by Pingoru
- Oct 29, 2025, 04:30 PM UTC
- Resolved
- Oct 29, 2025, 11:15 PM UTC
- Duration
- 6h 44m
Affected: IDEIDEIDEIDEIDEIDEIDEIDEIDEIDEIDEIDEIDEIDEIDE
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Oct 06, 2025, 01:22 PM UTC
- Resolved
- Oct 06, 2025, 01:49 PM UTC
- Duration
- 27m
Timeline · 3 updates
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Oct 03, 2025, 12:26 PM UTC
- Resolved
- Oct 02, 2025, 11:30 PM UTC
- Duration
- —
Timeline · 1 update
-
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 →
Critical September 11, 2025 - Detected by Pingoru
- Sep 11, 2025, 12:18 PM UTC
- Resolved
- Sep 11, 2025, 12:49 PM UTC
- Duration
- 30m
Affected: Application creation, merging, cloning
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Aug 21, 2025, 09:03 AM UTC
- Resolved
- Aug 21, 2025, 05:00 AM UTC
- Duration
- —
Timeline · 1 update
-
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 →
- 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
-
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.
-
identified Aug 18, 2025, 03:35 PM UTC
We have identified the issue and our team is working on a fix.
-
monitoring Aug 18, 2025, 04:15 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 18, 2025, 05:48 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 18, 2025, 03:30 PM UTC
- Resolved
- Aug 18, 2025, 03:30 PM UTC
- Duration
- —
Timeline · 1 update
-
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 →
- 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
-
investigating Aug 14, 2025, 02:57 PM UTC
We’re currently investigating an issue causing stylesheets to fail to load on classic endpoints.
-
identified Aug 14, 2025, 03:07 PM UTC
The issue has been identified and a fix is being implemented.
-
identified Aug 14, 2025, 03:07 PM UTC
We are continuing to work on a fix for this issue.
-
resolved Aug 14, 2025, 03:48 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 08, 2025, 09:27 AM UTC
- Resolved
- Aug 08, 2025, 09:00 AM UTC
- Duration
- —
Timeline · 1 update
-
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 →
- Detected by Pingoru
- Jul 04, 2025, 10:05 AM UTC
- Resolved
- Jul 07, 2025, 12:31 PM UTC
- Duration
- 3d 2h
Timeline · 3 updates
-
investigating Jul 04, 2025, 10:05 AM UTC
This issue is currently being investigated.
-
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.
-
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 →
- 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
-
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.
-
investigating Jun 16, 2025, 12:57 PM UTC
We are continuing to investigate this issue.
-
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.
-
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 →