BEE Plugin Outage History

Started Oct 14, 2026, 12:24 PM UTC· resolved Oct 14, 2026, 12:30 PM UTC

1. investigating Oct 14, 2026, 12:24 PM UTC

   We’re currently experiencing an issue that makes the Beefree SDK unreachable. Requests to the SDK return a 502 Bad Gateway or 504 Gateway Timeout error, so the editor may fail to load or respond. Our team is already investigating the cause and working to restore service as quickly as possible. We’ll post an update here as soon as we have more information.

2. resolved Oct 14, 2026, 12:30 PM UTC

   The issue has been resolved. The 502 and 504 errors were caused by a configuration issue in our gateway, which our team has fixed. The Beefree SDK is back online, and all services are operating normally.

3. postmortem Oct 14, 2026, 03:09 PM UTC

   # **Summary** On Oct 14, between 12:12 UTC and 12:26 UTC, a service disruption impacted the availability of the Editor component for end-users. The incident occurred during a planned configuration update aimed at decommissioning a legacy service. During execution via Terraform, an undetected state drift between the remote infrastructure and the defined configuration caused an unexpected destruction and recreation of the API Gateway, followed by a listener misconfiguration on the Application Load Balancer \(ALB\). Total service degradation lasted approximately 14 minutes. Full functionality was restored at 12:26 UTC following targeted manual remediation. # **Status** **Solved** # **Timeline \(UTC\)** Oct 14, 2026 * 12:10 UTC – A routine infrastructure update was initiated via Terraform to remove resources associated with a decommissioned service. * 12:12 UTC – Upon execution, Terraform identified an implicit dependency drift, triggering an unintended `destroy-and-recreate` cycle for the API Gateway instance. * 12:18 UTC – The API Gateway replacement was provisioned. However, traffic routing failed due to a mismatched configuration state on the Application Load Balancer \(ALB\) listener bindings. * 12:20 UTC – Engineering teams identified the routing anomaly on the ALB listener and initiated corrective configuration procedures. * 12:26 UTC – Listener configuration was fully restored and verified. Traffic flow to the EVC cluster normalized, resolving customer impact. **Incident window**: ~14m, all EVC services not reachable # **Customer impact** Duration: 14 minutes \(12:12 UTC – 12:26 UTC\) Affected Components: EVC Cluster underlying services, Editor interface. User Experience: End-users attempting to access or perform operations within the Editor experienced temporary service unavailability and request timeouts. No data loss or corruption occurred during this period. # **Root Cause** The root cause was an unexpected dynamic resource replacement triggered by Terraform execution, resulting from a latent configuration drift between the active cloud resources and the declarative state file. During the removal of legacy service declarations, an implicit resource attribute dependency within the Terraform provider schema evaluated the update as a breaking change requiring resource replacement rather than an in-place update. Because the environment had experienced minor manual or unindexed attribute shifts over time \(configuration drift\), the plan preview did not clearly highlight the cascading effect on the API Gateway's dependent ALB listener configuration. Consequently, when the gateway was recreated, the associated ALB listener bindings failed to map correctly to the target group, cutting off ingress traffic to the EVC cluster. # **Lessons Learned & Action Items** To prevent similar issues during future infrastructure changes, the following systemic improvements will be implemented: 1. Enhanced Pre-Apply Plan Inspection & Safety Gates: * Implement automated CI/CD checks to block Terraform execution if a plan contains destructive actions \(`destroy`\) on critical network infrastructure \(gateways, ALBs\) without explicit secondary authorization. 2. Drift Detection & Reconciliation Automation: * Introduce periodic scheduled drift-detection pipelines \(e.g., automated `terraform plan` audits\) to identify and reconcile discrepancies between real-world infrastructure and state files prior to active maintenance windows. 3. Decoupling Dependency Graphs: * Refactor infrastructure-as-code modules to isolate API Gateway definitions from underlying ALB target group lifecycle management, ensuring gateway updates cannot implicitly impact ingress routing listeners.

Read the full incident report →

Started Sep 19, 2026, 05:57 PM UTC· resolved Sep 19, 2026, 06:04 PM UTC

1. investigating Sep 19, 2026, 05:57 PM UTC

   Starting today at 17.39 UTC, the service responsible for the creation of PDFs and thumbnails has been experiencing degraded performance. As a result, you or your users may experience longer wait times or errors when trying to generate PDFs or thumbnails. Other APIs and services are operational at this time. Our team is investigating the root cause and preparing a fix.

2. investigating Sep 19, 2026, 06:00 PM UTC

   We are continuing to investigate this issue.

3. resolved Sep 19, 2026, 06:04 PM UTC

   We implemented temporary contingencies to prevent the issue from happening again while we continue investigating the root cause. The service is now stable, and we are continuing to monitor.

Read the full incident report →

Started Jun 19, 2026, 12:21 PM UTC· resolved Jun 20, 2026, 12:24 AM UTC

1. resolved Jun 19, 2026, 12:41 PM UTC

   On June 19, between 12:21 and 12:24 am UTC, some users may have experienced issues accessing design previews in the editors or exporting HTML, and you might have seen elevated API error rates on the "message/html" endpoint or with the onSave() callback. The affected component was our Multiparser, the service that translates Beefree JSON into HTML. The root cause has been identified, and we have deployed a fix to address it. We aim to deploy it as soon as the testing is completed. The service is now stable, and we are continuing to monitor.

Read the full incident report →

Started Jun 04, 2026, 11:15 AM UTC· resolved Jun 04, 2026, 02:12 PM UTC

1. resolved Jun 04, 2026, 04:40 PM UTC

   Today, June 4th, between 11:15 and 14:12 UTC, some customers may have experienced intermittent loading and authorization issues, causing the builders not to load. As a remediation strategy, we decided to roll back the involved component to the latest stable version while we investigate the root cause and determine the best path forward to prevent the issue from happening again. Although we don't expect any further disservice, we keep monitoring our systems.

Read the full incident report →

Started Jun 01, 2026, 12:51 PM UTC· resolved Jun 01, 2026, 01:03 PM UTC

1. resolved Jun 01, 2026, 01:19 PM UTC

   Today, between 12:51 UTC and 13:03 UTC, we experienced an outage of our Content Service APIs, impacting all the related services. Our team worked to resolve the issue during this time, including performing a service reboot and retrieving the necessary logs and diagnostics to restore full functionality. All services are now fully operational, and we’re continuing to investigate the root cause to help prevent similar issues in the future. Thank you for your patience and understanding.

Read the full incident report →

Started May 11, 2026, 08:03 AM UTC· resolved May 11, 2026, 09:03 AM UTC

1. investigating May 11, 2026, 08:03 AM UTC

   We are currently experiencing an issue with the co-editing functionality. As a result, any editor session initialized with co-editing enabled will fail to start. While our team works on a resolution, editor access can be restored by disabling co-editing in the SDK configuration. We'll share further updates as soon as we have more information.

2. investigating May 11, 2026, 08:37 AM UTC

   Our team is continuing to investigate the issue with the co-editing functionality. As a temporary measure, editor access can still be restored by disabling co-editing in the SDK configuration.

3. resolved May 11, 2026, 09:03 AM UTC

   Following our investigation, we've confirmed that the SDK co-editing functionality was not impacted by the issue reported earlier. Co-editing can remain enabled in your SDK Configuration. We apologize for any confusion this may have caused.

Read the full incident report →

Started Apr 30, 2026, 09:14 AM UTC· resolved Apr 30, 2026, 09:44 AM UTC

1. resolved Apr 30, 2026, 10:24 AM UTC

   Between 9:14 and 9:46 UTC, an internal update caused the builder to fail loading on new instances. Users who already had the builder open were not affected. We rolled back the change, and service was fully restored. Total duration: 32 minutes. Timeline: Identified (9:14 UTC): An internal update caused the builder to fail loading on new instances. Users who already had the builder open were not affected. Monitoring (9:40 UTC): We rolled back the change and started monitoring recovery. Resolved (9:46 UTC): Service fully restored.

2. postmortem May 07, 2026, 01:56 PM UTC

   ## **Summary** On April 30, 2026, we released an update to the component responsible for loading the Beefree SDK in your applications. Due to an error in this update, approximately 70% of Beefree SDK initializations failed, and the builder did not load. The issue was resolved by reverting to the previous loader version. ## **Timeline \(UTC\)** **09:14** – The loader component update is released for all Beefree SDK customers **09:37** – We detected the issue by trying to access a Beefree SDK instance **09:46** – The loader component has been reverted to the previous version **Incident window**: ~30 minutes ## **Customer impact** During the approximately 30-minute incident, end users attempting to initialize the Beefree SDK builders were not able to load it correctly. Two groups of users were unaffected: * Users who were already working in an active, initialized builder session at the time of the incident. * Applications that re-initialized the builder without fetching the updated loader, relying instead on a previously loaded version. ## **Root Cause** ### **The issue** In preparation for an upcoming feature rollout, we deployed an update to the component that loads the intended version of the Beefree SDK in the host application. The update was intended to address a browser caching issue we had identified in two internal testing environments. However, the update caused the loader to provide an incorrect path to the SDK version to be executed, resulting in the builder failing to load. ### **Why did we not catch this problem in our testing?** Our initial testing covered only internal instances, and the programming error that caused the issue was not caught during our review process, which was asynchronous in this case. Additionally, our existing automated tests did not cover this initialization scenario. ## **Action Items** ### **Immediate action taken:** * Reverted the loader to the previous stable version. ### **Next steps and short-term action items:** * We have since corrected the programming error and re-deployed the loader update on May 4, 2026, with no issues. * We will enhance our automated testing to ensure that builder initialization is explicitly verified at the end of every deployment process for infrastructure components that could affect it. * We will extend our AI-assisted pull request review to cover all components that may affect builder initialization, not just the frontend. Both action items are high priority and will be completed within the next two weeks.

Read the full incident report →

Started Feb 10, 2026, 09:30 PM UTC· resolved Feb 10, 2026, 09:30 PM UTC

1. resolved Feb 10, 2026, 10:21 PM UTC

   At 21:26 UTC, the login page of the SDK Developer Portal was unavailable in select regions due to a brief Amazon CloudFront issue. The downtime varied by location, but the issue resolved itself within approximately 30 minutes. We are continuing to monitor the situation.

Read the full incident report →

Started Dec 05, 2025, 09:09 AM UTC· resolved Dec 05, 2025, 09:15 AM UTC

1. monitoring Dec 05, 2025, 09:09 AM UTC

   An ongoing incident affecting the Cloudflare infrastructure is impacting our website, making developers.beefree.io and docs.beefree.io unreachable. It is still possible to log in directly to your SDK Console via this URL: developers.beefree.io/login

2. resolved Dec 05, 2025, 09:15 AM UTC

   Cloudflare has released a fix to address the incident. Systems seem to be fully operational again, but we will keep monitoring.

Read the full incident report →

Started Oct 31, 2025, 06:02 PM UTC· resolved Oct 31, 2025, 08:38 PM UTC

1. monitoring Oct 31, 2025, 06:02 PM UTC

   Due to recent issues with the latest version of our co-editing service, we’re temporarily routing traffic to a previous version. This older version offers lower performance but higher stability, which helps us minimize the risk of a total service outage while we address the underlying problems. Known Issues in the Older Version Intermittent “Connecting…” messages: Some users on specific network types may see this message, accompanied by corresponding entries in the onError callback logs. Duplicate user icons: In some implementations, refreshing the browser can cause duplicate user avatars to appear. What This Means We understand these issues may look like a regression in behavior, and we recognize the potential discomfort for users. Our priority is to maintain continuous availability of the co-editing experience while we work on a stable fix for the new version.

2. monitoring Oct 31, 2025, 07:30 PM UTC

   After careful evaluation, we have decided to continue utilizing the previous version of our co-editing service for at least the next several days. This approach will provide us with additional time to ensure system stability, thoroughly investigate and resolve any potential issues, and implement measures to minimize disruptions. Our goal is to reduce—and ideally eliminate—instances where the editor crashes due to a co-editing service failure.

3. resolved Oct 31, 2025, 08:38 PM UTC

   Although the incident is now marked as Resolved, we remain in a monitoring phase to confirm that the issue does not recur. Our co-editing service will continue to operate on the old version, which is fully stable and functioning as expected. We're leaving no stone unturned and are dedicating substantial resources to strengthening our co-editing infrastructure.

Read the full incident report →

Started Oct 31, 2025, 04:31 PM UTC· resolved Oct 31, 2025, 05:10 PM UTC

1. investigating Oct 31, 2025, 04:39 PM UTC

   We are investigating a service disruption affecting the Coediting functionality. In instances where Coediting is enabled, users may experience issues with templates not loading correctly. Our team is actively working to identify the cause and restore full functionality as soon as possible. We will provide updates here as soon as more information becomes available. Thank you for your patience.

2. monitoring Oct 31, 2025, 04:39 PM UTC

   We have identified and resolved the issue that was affecting the Coediting functionality and causing templates not to load correctly in instances where Coediting was enabled. The service is now fully operational, and we are currently monitoring to ensure stability.

3. resolved Oct 31, 2025, 05:10 PM UTC

   The issue affecting the Coediting functionality and causing templates not to load correctly in instances where Coediting was enabled has been fully resolved. After 30 minutes of monitoring, the service has remained stable, and all systems are now operating normally. Thank you for your patience while we worked to restore the service.

Read the full incident report →

Started Oct 27, 2025, 07:29 PM UTC· resolved Oct 27, 2025, 07:54 PM UTC

1. investigating Oct 27, 2025, 07:29 PM UTC

   We experienced a brief disruption with a real-time data streaming service. This may have impacted customers’ ability to use the builder and/or our co-editing service.

2. resolved Oct 27, 2025, 07:54 PM UTC

   The issue has been resolved and our service has returned to normal. Our team is investigating the root cause and will provide additional details as they become available.

Read the full incident report →

Started Oct 23, 2025, 11:30 PM UTC· resolved Oct 23, 2025, 11:30 PM UTC

1. resolved Oct 27, 2025, 03:35 PM UTC

   Our image hosting domain was recently listed on Spamhaus, which caused some end users to have trouble with images not loading correctly. We promptly requested a delisting, and by 10:00 a.m. Eastern Time on October 27th, our domain was no longer listed on Spamhaus. We are still monitoring the situation.

Read the full incident report →

Started Oct 21, 2025, 07:33 PM UTC· resolved Oct 21, 2025, 09:09 PM UTC

1. investigating Oct 21, 2025, 07:33 PM UTC

   At about 19:30 UTC we started to experience issues with our Coediting services, causing messages to not load. We restarted the systems for a prompt resolution, so your customers should no longer experience loading issues. We're monitoring the situation and are investigating the root cause.

2. monitoring Oct 21, 2025, 07:34 PM UTC

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

3. resolved Oct 21, 2025, 09:09 PM UTC

   This incident has been resolved. We continue to investigate the root cause and will add additional details as soon as possible.

4. postmortem Oct 29, 2025, 03:50 PM UTC

   ### Duration: 42 minutes ### Impact The Beefree SDK builder was unavailable for users on plans with the co-editing feature. These users experienced an infinite loading loop with a rotating spinner after the editor progress bar and toolbar had loaded, indicating a failure to retrieve templates. ### Summary A failure in the co-editing application led to 42 minutes of editor unavailability. The issue was resolved by restarting the Redis, Lightstreamer, and adapter services. ### Root Cause \(Under Investigation\) Initial analysis suggests an interruption in traffic flow between the frontend and the co-editing application. A comprehensive log analysis of system, application, and Lightstreamer-specific logs during the incident period ruled out a Lightstreamer license issue as a contributing factor, as no warnings or errors were found. Further investigation is ongoing. ### Timeline **19:30 UTC**: Co-editing application ceased receiving traffic, leading to editor loading issues. **19:35 UTC**: The Beefree team reported the issue due to multiple user complaints. **19:50 UTC**: Analysis identified that Redis and workers were not processing traffic. **20:06 UTC**: Redis was manually restarted \(without immediate impact\). **20:12 UTC**: Lightstreamer and adapter services were restarted, fully resolving the issue. ### Next Steps * To quickly resolve the issue, we restarted all co-editing-related services. * After the situation was stabilized, a series of tests was performed to simulate the issue and better understand the root cause. Some of them are still in progress. * Monitoring was improved by adding new dashboards for monitoring hardware resources used by the containers and the license status.

Read the full incident report →

Started Sep 15, 2025, 03:55 PM UTC· resolved Sep 15, 2025, 05:12 PM UTC

1. investigating Sep 15, 2025, 03:55 PM UTC

   We experienced a disruption with a real-time data streaming service that lasted for approximately 25 minutes. This may have impacted customers' ability to use the builder and/or our co-editing service. The issue has since been resolved, and service has returned to normal. Our team is actively investigating the root cause and will provide additional details as they become available.

2. investigating Sep 15, 2025, 04:04 PM UTC

   We are continuing to investigate this issue.

3. resolved Sep 15, 2025, 05:12 PM UTC

   We traced the issue to a Lightstreamer deployment process. The service exited unexpectedly while checking a license. Service has returned to normal. To better understand the cause, our team will reproduce and debug the issue. Please reach out to [email protected] with any questions.

Read the full incident report →

Started Jun 20, 2025, 03:28 PM UTC· resolved Jun 20, 2025, 03:28 PM UTC

1. resolved Jun 20, 2025, 03:28 PM UTC

   We would like to extend our sincere apologies for any inconvenience or concern caused by any incident you were notified of today. After a thorough review, we have identified that the issue was the result of a false alarm, which triggered our automated systems. Please be assured that our systems remain fully operational, and we are actively implementing updates and safeguards to prevent similar occurrences in the future. Our team is committed to maintaining the reliability and integrity of our services, and we deeply regret any disruption this may have caused. We appreciate your understanding and patience as we continue to improve our processes.

Read the full incident report →

Started Jun 13, 2025, 05:40 AM UTC· resolved Jun 13, 2025, 07:20 AM UTC

1. resolved Jun 13, 2025, 08:09 AM UTC

   Between June 13th at 5:40 AM UTC and 7:20 AM UTC, some users experienced issues with the authorization services used by the Beefree SDK. Our team worked to resolve the issue during this time, including performing a service reboot and retrieving the necessary logs and diagnostics to restore full functionality. All services are now fully operational, and we’re continuing to investigate the root cause to help prevent similar issues in the future. Thank you for your patience and understanding.

Read the full incident report →

Started Mar 11, 2025, 05:35 PM UTC· resolved Mar 11, 2025, 06:59 PM UTC

1. investigating Mar 11, 2025, 05:35 PM UTC

   We are currently investigating an issue with our service that powers our Co-editing functionality. As a result, customers using Co-editing are currently unable to launch the builder. Our team is already actively working to resolve the issue, and we will provide updates as soon as we have more information.

2. identified Mar 11, 2025, 06:16 PM UTC

   We have identified the cause of the issue with the service powering the Co-editing functionality. Our team is actively working on a solution and will provide further updates shortly.

3. monitoring Mar 11, 2025, 06:33 PM UTC

   The co-editing functionality is now working again. The service issue has been resolved. We are monitoring the service closely to ensure it continues functioning as expected.

4. resolved Mar 11, 2025, 06:59 PM UTC

   The issue has been mitigated by rolling back the impacted component, and all services are now stable. While the immediate incident is resolved, we will be conducting further work to ensure a long-term fix and prevent recurrence.

Read the full incident report →

Started Mar 10, 2025, 03:09 PM UTC· resolved Mar 10, 2025, 04:36 PM UTC

1. investigating Mar 10, 2025, 03:09 PM UTC

   We are currently experiencing a partial outage that is affecting our login system. As a result, users may encounter 403 (Forbidden) and 504 (Gateway Timeout) errors when attempting to access our services via our login endpoint. Users may experience login failures, including 403 and 504 errors, and access to certain endpoints may be delayed or unavailable. Our team is actively investigating the issue and working towards a resolution.

2. investigating Mar 10, 2025, 03:19 PM UTC

   Update: We are currently identifying the root cause of the issue and are actively working on a solution. Our team is dedicated to resolving the problem as quickly as possible, and we will continue to provide updates on our progress.

3. monitoring Mar 10, 2025, 04:18 PM UTC

   We have identified the root cause of the issue and implemented a solution to address the intermittent issues affecting key services. Our team is closely monitoring the situation to ensure system stability.

4. resolved Mar 10, 2025, 04:36 PM UTC

   The issue has been resolved, and all services are now operating normally. We will continue to monitor the situation closely over the next few days to ensure stability. Thank you for your patience.

5. postmortem Mar 11, 2025, 03:13 AM UTC

   ### Duration: 1 hour, 37 minutes ### Impact: Beefree SDK customers experienced slowdowns and errors when loading the editors, particularly on the Auth and Utils endpoints. API SDK calls were impacted by slowness and errors. ### Summary: On Saturday, March 8, 2025, we updated our infrastructure and services to support a multi-region deployment, enabling our SDK to operate across two AWS regions—Dublin, Ireland, and Frankfurt, Germany. The scheduled maintenance was successfully completed at 11:36 AM EST, with additional adjustments made on March 9 and the morning of March 10 \(CET\). However, as traffic increased on **Monday, March 10, 2025**, the **Beefree SDK and Beefree SDK API** began experiencing **intermittent issues**, which later escalated into a **stable outage**. During the escalation, we investigated the root cause and explored multiple possible fixes. Given the time constraints and uncertainty of an immediate resolution, **we prioritized stability and swiftly redirected traffic to a single region, which restored normal service**. ## Current status: Services are **normal** with no further detected issues. We are actively monitoring for any residual effects. ## Root cause: The issue was highly traffic-dependent, as no slowdowns or failures were observed in the days prior or during load testing. Autoscaling worked correctly, ruling it out as a contributing factor. The problem originated from the use of shared resources within the EKS cluster, specifically DNS resolution. A preliminary analysis indicates that the primary cause was a slowdown in CoreDNS within our AWS infrastructure. As traffic surged, CoreDNS pods became overwhelmed with DNS queries, leading to delayed responses. However, CPU and memory usage remained stable, showing no signs of resource exhaustion. We are conducting further investigations to validate this finding and ensure there are no additional contributing factors. ## Issue timeline **10:38 AM EDT** Our monitoring systems triggered phone alerts, notifying developers of the issue. Our automated monitoring service also posted an alert in our internal Slack channel. Internal escalation was officially initiated. **10:41 AM EDT** A cross-functional incident response meeting was held with developers and support team members. It quickly became evident that the issue was causing slowdowns across the entire infrastructure. The team began troubleshooting to identify the root cause. **11:45 AM EDT** The issue was identified as an anomaly in the internal network management of the newly deployed multi-region AWS setup. To mitigate the impact, we redirected all traffic for essential services to a single region \(AWS Dublin, Ireland\). **12:05 PM EDT** Traffic redirection was fully completed, and infrastructure slowdowns resolved almost immediately. We began monitoring the effectiveness of the solution. **12.35 PM EDT** After 30 minutes of stable monitoring, we officially closed the escalation ## Next steps: Our team is currently conducting a full Root Cause Analysis \(RCA\) to completely understand the underlying cause. We will post updates here as we continue to receive them, including when the RCA is available upon request from our team. ‌ We will evaluate additional monitoring, testing, and safeguards to prevent recurrence. #### If you are still experiencing issues, please contact our [support](mailto:[email protected]) team. No further action is needed by you at this time. ‌ **We sincerely apologize for the disruption and appreciate your patience.** We will provide an update once we complete our analysis.

Read the full incident report →

Started Feb 07, 2025, 11:30 PM UTC· resolved Feb 07, 2025, 11:31 PM UTC

1. resolved Feb 10, 2025, 05:56 PM UTC

   The image editor experienced a brief outage and was unavailable for approximately 1 minute. The issue has been resolved, and full functionality has been restored.

Read the full incident report →

Started Dec 04, 2024, 03:45 PM UTC· resolved Dec 05, 2024, 02:47 PM UTC

1. investigating Dec 04, 2024, 03:45 PM UTC

   We are investigating an issue where some images hosted on our CDN are not displaying for users due to a temporary listing of our CDN URLs on a spam blacklist. This affects users with specific ad blockers or antivirus settings, causing images to be invisible in libraries, designs, and landing pages. The delisting request has been approved, but it may take time for the update to propagate. Our team is actively monitoring the situation, reviewing systems to address vulnerabilities, and exploring solutions to prevent recurrence. For now, affected users can try disabling ad blockers or whitelisting our CDN.

2. monitoring Dec 04, 2024, 05:11 PM UTC

   The issues affecting content visibility are steadily improving. The feeds that impact various blocklists are updating, and we anticipate a return to normal by tomorrow morning UTC. However, some residual effects, such as browser ad blockers, are still flagging content, and may persist temporarily. While significant progress has been made, we recommend checking this status page to stay updated on ongoing monitoring. Thank you for your patience as we continue to address this issue.

3. monitoring Dec 04, 2024, 06:18 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Dec 05, 2024, 02:47 PM UTC

   We no longer see our CDN URL listed in popular ad blockers, and we confirmed that most customers no longer experience issues with images. There’s a small chance that some corporate filters or niche ad blockers may still temporarily block images until the fix propagates. In the unlikely case that you’re still experiencing issues, please reach out to our support team and we’ll investigate.

Read the full incident report →

Started Nov 12, 2024, 02:00 PM UTC· resolved Nov 12, 2024, 04:00 PM UTC

1. resolved Nov 20, 2024, 09:49 PM UTC

   Our systems experienced degraded performance due to an unexpected surge in oversized JSON files. This caused temporary delays and occasional failures for a small percentage of users during specific timeframes: 8:12-8:24 AM PST 9:23-10:16 AM PST 11:21-11:47 AM PST To address the issue, we scaled our infrastructure, implemented safeguards to handle oversized requests, and deployed a fix on Monday, November 18, to prevent future parser hangs.

Read the full incident report →