Duration: 1 day, 12 hours and 51 minutes

Affected Components: Clerk → Core services → Authentication & User

Aug 4, 23:03:58 GMT+0
Investigating - We are currently investigating an increase in latency and errors in our FAPI and BAPI services..

Aug 4, 23:14:01 GMT+0
Identified - We've identified the issue with our upstream provider and are working on resolution..

Aug 4, 23:40:50 GMT+0
Resolved - We've resolved the issue with our upstream provider..

Aug 4, 23:29:11 GMT+0
Monitoring - Our upstream provider has applied a fix and we've seen latency and errors subside. We continue to monitor the situation..

Duration: 2 days, 5 hours and 57 minutes

Affected Components: Clerk → Core services → Account Portal, Clerk → Core services → Authentication & User, Clerk → Core services → Webhooks, Clerk → Core services → Machine authentication

Aug 1, 10:04:57 GMT+0
Resolved - All systems are operational.

Aug 1, 10:04:02 GMT+0
Identified - Elevated error rate across all service.

Duration: 1 day, 4 hours and 33 minutes

Affected Components: Resend → General API

Jul 30, 20:00:00 GMT+0
Identified - We have identified the issue with domain verifications both through the dashboard and public API..

Jul 30, 21:25:00 GMT+0
Resolved - We have resolved the underlying issue, and service has resumed. Domain verification has been restored, and affected verifications were re-triggered..

Duration: 16 days and 1 hour

Affected Components: Resend → Email Events, Resend → Email Sending → Single Email, Resend → General API, Resend → Email Sending → Batch Emails

Jul 30, 16:23:00 GMT+0
Resolved - We have resolved the underlying issue, and sending test emails from resend.dev: http://resend.dev has resumed..

Jul 30, 09:58:00 GMT+0
Identified - Performance degradation when sending test emails from the resend.dev: http://resend.dev domain, which is causing the API to return a validation error stating that the domain is not verified..

Duration:

Affected Components: Resend → General API, Resend → Email Events, Resend → Email Sending → Single Email, Resend → Email Sending → Batch Emails

Jul 30, 00:00:00 GMT+0
Investigating - We are currently investigating increased latency in contact-related webhook deliveries. At this time, you may experience delays in receiving contact events on your webhook endpoints..

Jul 31, 02:00:00 GMT+0
Monitoring - We are still noticing increased latency in contact-related webhook deliveries. Events can be delayed by up to 8 hours before being delivered. We have identified the issue and implemented infrastructure changes to process the backlog faster..

Aug 1, 00:00:00 GMT+0
Resolved - The backlog is gone, and all delayed contact webhooks have been delivered. Delivery latency has now recovered. The new infrastructure configurations prevent this same issue from happening again..

Duration: 7 hours and 14 minutes

Affected Components: Resend → General API, Resend → Email Sending → Single Email, Resend → Email Sending → Batch Emails

Jul 29, 21:14:58 GMT+0
Resolved - Between 20:15 and 20:16 UTC, a brief database disruption caused elevated error rates for approximately 45 seconds. During this window, requests to the Resend API, SMTP relay, and dashboard may have returned 5xx errors or timed out. The issue resolved automatically at 20:16 UTC and all services have been operating normally since. Any request that failed during this window can be safely retried. Emails that had already been accepted before the disruption were not lost. They were delivered normally. Broadcasts were not affected..

Duration: 3 days, 11 hours and 55 minutes

Affected Components: Resend → Email Sending → Single Email, Resend → General API, Resend → Email Sending → Batch Emails

Jul 29, 16:24:01 GMT+0
Identified - We have identified the issue and we are working on a fix now..

Jul 29, 16:34:06 GMT+0
Monitoring - The fix has been pushed and we are now monitoring the situation..

Jul 29, 17:39:32 GMT+0
Resolved - We have resolved the underlying issue and service has been resumed..

Jul 29, 16:15:37 GMT+0
Identified - We have identified the issue and we are working on a fix now..

Jul 29, 16:19:45 GMT+0
Identified - We have identified the issue and we are working on a fix now..

Duration: 26 days, 7 hours and 5 minutes

Affected Components: Neo4j → Aura API (api.neo4j.io)

Jul 23, 10:52:38 GMT+0
Investigating - We are currently investigating an issue at this time..

Jul 23, 11:08:11 GMT+0
Investigating - We are working with engineering teams and making progress with the investigations at the current time..

Jul 23, 11:24:53 GMT+0
Investigating - We are working with engineering teams and continuing to make progress with the investigations at the current time..

Jul 23, 11:38:29 GMT+0
Identified - We have identified the cause of the current issue and are actively working on the fix currently..

Jul 23, 11:53:35 GMT+0
Identified - We are deploying the first part of the fix and continue actively working on rolling out the full solution. We expect an ETA in the order of 1hour from now..

Jul 23, 12:11:34 GMT+0
Identified - We have identified the subset of instances impacted and continue to deploy the fix at this time..

Jul 23, 12:32:09 GMT+0
Identified - We have deployed a configuration fix and are now working to resolve the subset of instances impacted..

Jul 23, 12:49:35 GMT+0
Identified - With the configuration fix deployed, we are continuing to resolve the subset of instances still impacted..

Jul 23, 13:09:59 GMT+0
Identified - We are continuing to resolve the subset of instances still impacted..

Jul 23, 13:35:17 GMT+0
Identified - We are continuing to resolve the subset of instances still impacted..

Jul 23, 14:07:31 GMT+0
Identified - We are continuing to resolve the subset of instances still impacted..

Jul 23, 14:27:59 GMT+0
Identified - We continue to resolve the subset of instances which are still impacted..

Jul 23, 14:44:47 GMT+0
Monitoring - We continue to resolve the subset of instances which are still impacted..

Jul 23, 15:03:13 GMT+0
Monitoring - AuraDB Virtual Dedicated Cloud and AuraDB Business Critical should all now be fixed. We continue to resolve the subset of instances which are still impacted for AuraDB Professional and Free..

Jul 23, 15:29:02 GMT+0
Monitoring - We continue to resolve the subset of instances which are still impacted for AuraDB Professional and Free..

Jul 23, 15:57:10 GMT+0
Monitoring - We continue to resolve the subset of instances that are still impacted for AuraDB Professional and Free..

Jul 23, 16:32:12 GMT+0
Monitoring - We continue to resolve the subset of instances that are still impacted for AuraDB Professional and Free.

Jul 23, 17:01:05 GMT+0
Monitoring - We continue to fix a subset of instances that are still impacted for AuraDB Professional and Free.

Jul 23, 17:31:23 GMT+0
Monitoring - We continue to fix a small subset of instances that are still impacted under the AuraDB Professional and Free tiers..

Jul 23, 18:07:39 GMT+0
Monitoring - We addressed the issue in all AuraDB Professional instances. Aura Free can still be affected. We will continue to monitor and fix the remaining databases..

Jul 23, 19:39:48 GMT+0
Monitoring - We continue to fix a small subset of Free instances that are still impacted..

Jul 23, 22:28:38 GMT+0
Monitoring - We are continuing to monitor for any further issues..

Jul 24, 01:02:47 GMT+0
Monitoring - We are continuing to monitor for any further issues..

Jul 24, 02:56:04 GMT+0
Monitoring - We are continuing to monitor the situation closely for any further issues..

Jul 24, 06:00:10 GMT+0
Monitoring - We are continuing to monitor the situation closely for any further issues..

Jul 24, 08:30:32 GMT+0
Monitoring - We are continuing to monitor for any further issues..

Jul 24, 12:59:12 GMT+0
Monitoring - All identified instances have been fix, continuing to monitor. Contact customer support for any further issues..

Jul 24, 15:56:10 GMT+0
Resolved - All fixes have been deployed and issue is now marked as resolved..

Jul 29, 21:58:35 GMT+0
Resolved - ### **What happened** On Thursday, Jul 23, 2026 10:33 UTC a configuration change was deployed to Aura that unintentionally altered how memory allocations were calculated for database instances. As a result, a subset of instances received insufficient memory, causing some database instances to become unavailable or unable to complete updates. The adjusted memory allocation led to out-of-memory conditions, causing database instances to repeatedly restart due to insufficient memory resources or become stuck updating. This issue affected instances across multiple cloud providers and multiple product tiers. Once the issue was identified, we immediately reverted the configuration change, preventing any additional instances from receiving the incorrect configuration. A corrected configuration was deployed to production by Thursday, Jul 23, 2026 11:56 UTC. However, database instances that had already received the incorrect configuration required individual recovery actions before they could return to normal operation. By Thursday Jul 23, 2026 17:59 UTC, all known customer-impacting database instances had been recovered. Monitoring continued through the following day, with the incident fully resolved on Friday, Jul 24, 2026 16:30 UTC. ### **How the service was affected** The primary customer impact was that several AuraDB database instances became unavailable or entered a degraded state. Affected instances were unable to complete routine software updates and, in some cases, repeatedly restarted because insufficient memory had been allocated. * **Service availability:** Customer impact varied by service tier. AuraDB Professional instances, which do not provide High Availability, experienced the greatest level of service disruption, with a subset becoming unavailable and unable to process reads or writes. For affected AuraDB Business Critical and Virtual Dedicated Cloud \(VDC\) instances, the impact was generally limited to a temporary loss of fault tolerance while service availability was maintained. In a smaller number of cases, Business Critical and VDC instances also became unavailable. * **Stuck updates**: Additional instances remained available but were stuck in an "Updating" state, which blocked customer-initiated operations such as resizes or configuration changes. * **Cross-platform scope**: The impact spanned all three supported cloud providers and multiple regions, affecting customers globally. Customer Support cases were raised and our team triaged and manually recovered affected instances in priority order. The majority of AuraDB instances continued to operate normally. Customer impact was fully mitigated through the configuration revert and targeted manual recovery of each affected instance. ### **What we are doing now** We have carried out a thorough analysis of this incident and have identified the following actions: * **Prevention** * **Improved deployment validation:** We are strengthening our release validation process to better identify configuration changes. * **Component decoupling**: We are evaluating improvements to the sequencing of component deployments to reduce the risk of unintended changes being included in releases. * **Progressive rollout strategy**: We are reviewing the rollout process for the affected components, to bring them in line with the rollout controls used for other critical components. * **Detection** * **Better alerting**: We are enhancing our monitoring to detect abnormal increases in failure rates \(such as loss of fault tolerance or availability\) more quickly and reliably. * **Mitigation** * **Safer configuration deployment:** We are improving how production configuration changes are deployed so they can be disabled or rolled back more quickly without requiring a broader software release. * **Faster manual recovery tooling**: We are improving our recovery tooling to reduce the time required to identify and manually recover affected instances. We recognize the disruption this incident caused and apologize for the impact to affected customers. We have completed the immediate corrective actions, and the longer-term improvements described above are already underway to reduce the likelihood and impact of similar incidents in the future..

Duration: 8 hours

Affected Components: Resend → Email Sending → Batch Emails, Resend → Email Events, Resend → Email Sending → Single Email, Resend → General API

Jul 22, 19:43:00 GMT+0
Identified - We have identified an issue with creating API keys and domains and we are working on a fix now..

Jul 22, 19:51:00 GMT+0
Resolved - We have resolved the underlying issue and service has been resumed..

Duration: 2 days, 8 hours and 24 minutes

Affected Components: Clerk → Core services → Account Portal, Clerk → Core services → Authentication & User, Clerk → Core services → Webhooks, Clerk → Core services → Machine authentication

Jul 16, 13:27:03 GMT+0
Investigating - We're continuing to investigate..

Jul 16, 13:04:44 GMT+0
Investigating - Reports of 429 error responses from API endpoints.

Jul 16, 14:01:08 GMT+0
Resolved - We have confirmed that error rates have returned to baseline..

Jul 16, 13:08:07 GMT+0
Investigating - We're continuing to investigate..

Jul 16, 13:45:31 GMT+0
Monitoring - We've deployed a fix and are seeing error rates decrease. We are monitoring..

Duration: 1 day and 21 hours

Affected Components: Resend → Email Events, Resend → Email Sending → Single Email, Resend → General API, Resend → Email Sending → Batch Emails

Jul 16, 12:30:00 GMT+0
Resolved - We have resolved the underlying issue and service has been resumed..

Jul 16, 11:45:00 GMT+0
Identified - We have identified increased error rates on the dashboard correlated with an upstream provider incident. We're shipping improvements to contain the errors..

Duration: 1 hour and 29 minutes

Affected Components: Clerk → Core services → Authentication & User, Clerk → Core services → Account Portal

Jul 16, 07:56:30 GMT+0
Investigating - There is increased latency on our APIs. We are investigating..

Jul 16, 07:58:00 GMT+0
Resolved - There was a service degradation on our caching layer that affected the latency of our APIs. The caching layer is back to normal and latency dropped to normal levels..

Duration: 2 days, 5 hours and 27 minutes

Affected Components: Resend → Email Sending → Single Email, Resend → General API, Resend → Email Sending → Batch Emails

Jul 10, 14:14:35 GMT+0
Resolved - We have resolved the underlying issue and service has been resumed..

Jul 10, 13:21:07 GMT+0
Investigating - We're noticing increased API latency across different endpoints, causing delays in email sending..

Jul 10, 13:31:11 GMT+0
Identified - We have identified the issue and are deploying a fix now. The team is monitoring. Latency has recovered, but we're keeping this incident open for the next few minutes to monitor downstream services..

Jul 10, 13:53:56 GMT+0
Monitoring - The deployment has been completed, and we're still monitoring. Latency has stabilized since 13:38 UTC..

Duration: 5 hours and 22 minutes

Affected Components: Clerk → Core services → Account Portal

Jul 9, 20:38:10 GMT+0
Investigating - We are observing evaluated errors in account portal and actively investigating the source of the problem.

Jul 9, 20:43:32 GMT+0
Resolved - The underlying issue has been identified and the Account Portal is now fully functioning again..

Duration: 14 hours and 19 minutes

Affected Components: Clerk → Core services → Webhooks

Jul 1, 17:12:21 GMT+0
Investigating - We are investigating delays in webhook delivery. We have deployed mitigations and are continuing to monitor..

Jul 1, 17:26:41 GMT+0
Resolved - We have identified the cause of the delays and our mitigations have been successful. We are continuing to monitor webhook delivery..

Duration: 23 days, 12 hours and 47 minutes

Affected Components: Neo4j → Aura API (api.neo4j.io)

Jun 24, 09:14:35 GMT+0
Resolved - This incident has been resolved..

Jun 23, 11:25:47 GMT+0
Identified - Aura console is experiencing some intermittent errors: "Our system is experiencing problems right now. try again later or contact support if the problem persists." This may require you to reload or wait longer for navigating in the console Operations and the Aura API remain unaffected We are actively working on a fix.

Jun 23, 13:03:27 GMT+0
Identified - We are continuing to investigate a fix for the issue.

Jun 23, 13:39:43 GMT+0
Identified - We are continuing to work on a fix for this issue..

Jun 23, 15:43:38 GMT+0
Monitoring - We are deploying a change. We will monitor and update..

Jun 23, 19:27:53 GMT+0
Monitoring - Continuing to monitor the deployed changes. Next update expected 6/24/2026 10am UTC..

Jun 24, 09:14:24 GMT+0
Monitoring - We have checked and confirm that the issue is now fully addressed..

Jul 10, 14:50:24 GMT+0
Resolved - ## What Happened At approximately 12:00 UTC on January 22, 2026, users encountered intermittent error banners within the Aura console displaying, "We're having a problem. Try again.," which occurred alongside 500 errors from console API endpoints. These disruptions were transient and caused by internal API timing out during the TLS handshake process, typically resolving within about 10 seconds or following a page refresh ## How the service was affected The Aura Console and Aura API experienced degraded performance, which manifested as intermittent error banners within the Aura console UI. An investigation identified the root cause as high CPU usage and throttling within the console API. This issue was primarily driven by repeated large entity listings and expensive reconciler requests To address the issue, targeted fixes were successfully deployed to both the Aura console and Aura API. This was followed by adjustments to the resource configuration to increase operational headroom and ensure stability ## What are we doing now The following reactive and proactive measures have been implemented to reduce the likelihood of similar incidents: * Developed a monitoring dashboard to observe request drops based on internal API log data to implement automated monitoring and alerting to catch issues before they occur * Implemented a staggered delay between paginated reconciler requests to mitigate high resource consumption and improve API stability * Enhanced infrastructure aware resources calculations to improve performance * Introduced a new filter for queries based on service tiers to optimize CPU overhead for each calls performed by the reconciler * Deactivated redundant request middleware processing to optimize API calls.

Duration: 2 hours and 8 minutes

Affected Components: Clerk → Core services → Account Portal, Clerk → Core services → Authentication & User

Jun 18, 18:26:00 GMT+0
Investigating - SVGs are not loading properly, the team is investigating a fix.

Jun 18, 20:13:00 GMT+0
Monitoring - A fix has been deployed and we're seeing improved rates of resolution on the SVGs.

Jun 18, 20:23:37 GMT+0
Resolved - A fix has been published and confirmed it's now resolving SVGs correctly.

Duration: 47 minutes

Affected Components: Memorang Hub

May 26, 21:46:36 GMT+0
Investigating - We are currently investigating this incident..

May 26, 22:13:35 GMT+0
Monitoring - A fix has been deployed and we are monitoring to ensure that issue is completely resolved.

May 26, 22:33:41 GMT+0
Resolved - This incident has been resolved..

Duration: 2 days, 19 hours and 1 minute

Affected Components: Clerk → Core services → Authentication & User, Clerk → Core services → Account Portal, Clerk → Core services → Webhooks, Clerk → Core services → Machine authentication

May 26, 22:00:12 GMT+0
Investigating - We have deployed a fix and are observing rapid decline in error rates. We continue to monitor the situation..

May 26, 22:08:05 GMT+0
Monitoring - We have deployed a fix for this issue and our services appear to have returned to normal operation. We continue to monitor..

May 26, 22:26:10 GMT+0
Resolved - The root cause has been identified and addressed. We will continue to monitor going forward..

May 26, 21:19:09 GMT+0
Investigating - We are investigating elevated 500s affecting a subset of our API responses..

May 26, 21:32:24 GMT+0
Investigating - We have implemented remediation for our session service. We are still investigating remediation for the Dashboard and backend API..

May 26, 21:47:33 GMT+0
Investigating - We are deploying a mitigation for the Dashboard and Backend API.

May 26, 21:53:42 GMT+0
Investigating - We are continuing to work to deploy a mitigation for the backend API and Dashboard issues..

Duration: 5 days, 18 hours and 56 minutes

Affected Components: Clerk → Core services → Account Portal

May 11, 15:00:40 GMT+0
Investigating - Some customers are encountering an issue where the root route at the Accounts Portal is returning 404 and not redirecting to the appropriate page..

May 11, 15:30:04 GMT+0
Monitoring - We have deployed a mitigation and are observing..

May 11, 17:19:37 GMT+0
Resolved - The issue has been resolved..

Duration: 9 days, 2 hours and 22 minutes

Affected Components: Clerk → Core services → Authentication & User

May 8, 11:02:35 GMT+0
Investigating - We are currently investigating an issue where Clerk JS cannot be downloaded, preventing sign in or sign up when using Clerk components. We believe this is related to DNS clerk.[your_domain].com "clerk.[your_domain].com": http://clerk.domain.com, and are working to discover the cause and scope of the issue..

May 8, 11:38:35 GMT+0
Monitoring - We have observed that failures to load Clerk JS (reported by dashboard.clerk.com: http://dashboard.clerk.com) last occurred 30minutes ago, and this would correlate with failures reported from Clerk applications. We are in contact with our DNS providers to understand the root cause..

May 8, 14:40:58 GMT+0
Resolved - We continue to work with our DNS provider to discover the source of the issue. We currently believe approximately 0.37% of traffic was impacted by being unable to resolve DNS of the CDN that provides ClerkJS..

Duration: 11 hours and 43 minutes

Affected Components: Memorang Hub, AiLA, API, AiBL Apps, Integration Webhooks, Memorang Website, Purchase Webhooks

Apr 30, 22:27:17 GMT+0
Identified - We are working on a maintenance for our services, patching databases.

May 1, 02:05:02 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

May 1, 02:12:42 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Apr 30, 16:53:17 GMT+0
Investigating - We are currently doing an emergency maintenance which is affecting our main services.

Apr 30, 17:28:37 GMT+0
Identified - We are continuing to work on a fix for this incident..

May 1, 04:36:03 GMT+0
Resolved - This incident has been resolved..

Duration: 2 hours and 16 minutes

Affected Components: Memorang Hub, AiLA, API, AiBL Apps, Integration Webhooks, Memorang Website, Purchase Webhooks

Apr 30, 14:00:11 GMT+0
Investigating - Multiple users are reporting to see 0 topics on our mobile apps and they cannot access content. We are investigating and working on provide a solution for this as soon as possible.

Apr 30, 14:46:11 GMT+0
Resolved - This incident has been resolved..

Apr 30, 15:31:37 GMT+0
Investigating - We are currently investigating this incident..

Apr 30, 15:44:01 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Apr 30, 16:15:58 GMT+0
Resolved - This incident has been resolved..

Duration: 2 hours and 10 minutes

Affected Components: Memorang Hub, AiBL Apps

Feb 19, 16:30:00 GMT+0
Identified - We are continuing to work on a fix/workaround for this incident..

Feb 19, 17:14:58 GMT+0
Identified - We are currently monitoring the underlying service provider on the updates..

Feb 19, 18:25:04 GMT+0
Monitoring - Services are being restored gradually. We are currently monitoring the downstream provider for more updates..

Feb 19, 18:40:00 GMT+0
Resolved - This incident has been resolved..

Duration: 1 hour

Affected Components: Memorang Hub, AiBL Apps

Dec 5, 09:00:05 GMT+0
Identified - We’ve confirmed an issue with a third-party provider that’s impacting email deliveries and some auth related services. We’re actively working to restore the services as soon as possible..

Dec 5, 10:00:00 GMT+0
Resolved - All services are back to normal. We'll continue to monitor the status of the impacted third party services.