1PasswordScheduled Support Maintenance – Response Delays Expected
The scheduled maintenance is now complete
Resolved
Outages and recoveries from the services you depend on.
40 incidents
The scheduled maintenance is now complete
Resolved
The issue with Event processing has been resolved. Impacted services have returned to normal operation. Flag Delivery was not impacted. There was no data loss experienced.
Resolved
On 2 February 2026 between 08:52 and 16:40 UTC, some Statuspage customers’ API-based integrations started failing with authorization errors when a planned cleanup of old API keys unintentionally disabled new keys as well. Statuspage UI and core product functions remained available. We provided a workaround by creating new API keys and then fully restored affected keys from a point‑in‑time database backup. We are implementing safeguards around bulk key operations, improved detection of abnormal API error rates, and stronger operational checks for similar maintenance activities to reduce the likelihood and duration of similar incidents in the future.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Issues affecting the NGC Catalog service have been resolved and the service is operating normally.
Resolved
This incident has been resolved.
Resolved
This issue is now resolved.
Resolved
The delays in SIM card management actions have been resolved. All operations are processing normally.
Resolved
This incident has been resolved.
Resolved
Overview On March 4, 2026, our platform experienced a period of degraded performance and a brief service interruption, primarily impacting users in the APAC region. The incident was triggered by an update to our Load Balancing layer that inadvertently extended to the cache synchronization workers across several global regions. This synchronization initiated a high-volume data retrieval process from our primary database. The resulting resource contention coincided with peak organic traffic, leading to increased latency and, eventually, a necessary database restart to restore system stability. Incident Timeline \(PST\) - March 4th, 2026 • 15:50 – 16:50: A new version deployment triggered a phased restart of cache synchronization workers across global regions. • 18:30: Coinciding with peak regional demand, the primary database experienced elevated CPU utilization. Users began noticing increased Time to First Audio \(TTFA\). • 19:45: Database resources reached a critical threshold, leading to broader performance degradation. • 20:18: Engineering teams initiated an investigation into database health. • 21:00: To clear queued transactions and stabilize the environment, a manual reset of the primary database was performed, resulting in a brief total service interruption. • 21:04: Database services were successfully restored. • 21:08: Latency metrics returned to normal levels. • 21:12: All background cache synchronization tasks successfully completed. Root Cause Analysis Resource Contention and Buffer Saturation The primary driver of this incident was the simultaneous "cold start" of cache workers across multiple regions. By design, these workers attempt to populate the rapid-access cache by performing a comprehensive data fetch from the primary database. Because several regions initiated this process concurrently, the database was subjected to multiple long-running read operations. This created a high demand for the database’s buffer pool. When peak organic traffic arrived, the database struggled to balance these synchronization read requests with the high-frequency write operations required by active user sessions. Latent Dependency A recent configuration update introduced an unexpected synchronous database look-up during the request resolution path. While typically negligible, this added DB query time became significant when the DB was under heavy load. This dependency meant that as database performance slowed, user-facing latency increased proportionally, eventually leading to a backlog of requests. Lessons Learned and Resolution Architectural Optimization • Decoupled Synchronization: We are re-evaluating our cache synchronization process to make it future proof as our load grows. • Improving our global database architecture: We are implementing a global database architectural change to make our system more resilient. Enhanced Monitoring We are deploying a unified health dashboard to provide real-time visibility into: • Granular resolution request hot path latency. • More aggressive alerting on DB / Cache health.
Resolved
All impacted services have now fully recovered.
Resolved
This issue is now resolved.
Resolved
This incident is now resolved. Between 17:55 and 20:35 UTC (10:55 AM–1:35 PM PT), form submission notification emails were not sent as expected. During this time, form submissions were successfully collected and remain available in the Forms tab within Site settings. However, notification emails that were not sent during this window will not be delivered retroactively. A fix was deployed, and email delivery has been fully restored. We are no longer seeing customer impact related to this issue. We appreciate your patience while we worked to resolve this.
Resolved
Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.
Resolved
Provider recovered
Resolved
The issues causing increased latency in the US East 2 region have been resolved.
Resolved
On March 9, 2026, between 01:23 UTC and 03:25 UTC, users attempting to create or resume codespaces in the Australia East region experienced elevated failures, peaking at a 100% failure rate for this region. Codespaces in other regions were not affected.<br /><br />The create and resume failures were caused by degraded network connectivity between our control plane services and the VMs hosting the codespaces. This was resolved by redirecting traffic to an alternate site within the region. While we are addressing the core network infrastructure issue, we have also improved our observability of components in this area to improve detection. This will also enable our existing automated failovers to cover this failure mode. These changes will prevent or significantly reduce the time any similar incident causes user impact.
Resolved
_Notice and disclaimer: Box is providing this preliminary information subject to further review and analysis. To the best of our knowledge, this is the current state and we may update as more information is confirmed._ On February 24th, 2026 between 6:11 AM PST and 6:40 AM PST, some users may have experienced difficulties while while attempting to log into Box. Users already logged into Box were not impacted by this issue. The issue occurred due to a recent configuration change related to device security that prevented users from logging in to Box. We were able to resolve the issue by quickly reverting the change. We are also working to improve our release strategy and testing processes to prevent similar issues from occurring in the future. We are conducting a full engineering postmortem and our overview is subject to change with further analysis and findings. In the event our continuing investigation yields further substantive findings, we may publish additional analysis after the conclusion of the full engineering postmortem. We are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter. Sincerely, The Box Team
Resolved
This incident has been resolved by Clerk.
Resolved
This incident has been resolved.
Resolved
This incident is now resolved. We've identified the root cause and are preparing a detailed post-mortem, which we'll share soon. Thank you for your patience.
Resolved
Between 16:50 - 17:01 UTC approx 25% of articles were failing to load and an error page was displayed on all help-centres. We rolled back a change which resolved the issue. Apologies for the disruption.
Resolved
Between 16:50 - 17:01 UTC approx 25% of articles were failing to load and an error page was displayed on all help-centres. We rolled back a change which resolved the issue. Apologies for the disruption.
Resolved
Between 16:50 - 17:01 UTC approx 25% of articles were failing to load and an error page was displayed on all help-centres. We rolled back a change which resolved the issue. Apologies for the disruption.
Resolved
We've fixed the earlier outage - apologies for the disruption. Get in touch via help.granola.ai "help.granola.ai": http://help.granola.ai if you're still having issues!
Resolved
The authorization provider has completed mitigation work and is reporting a full recovery in their systems. We are no longer observing impact to users.
Resolved
Duration: March 10, 2026, 9:00 AM PST - 9:14 PM PST Impact: Runtime logs for Line agent calls made during this time period were not available via the dashboard or API. Call processing was not affected. Resolution: Our engineering team identified the root cause as an upstream breaking change from an infrastructure provider that disrupted our log ingestion pipeline. A hotfix was deployed and log collection has been fully restored. All logs from the affected window have also now been recovered and backfilled. Next Steps: We are conducting a postmortem to improve reliability and detection speed moving forward.
Resolved
This incident has been resolved.
Resolved
Apologies for the disruption to MCP with Claude, we've worked through these with the Claude team and it looks like we're back up and running. If you're having issues, please follow the troubleshooting steps here: https://docs.granola.ai/help-center/sharing/integrations/mcp#granola-mcp
Resolved
The issue affecting WRITER Agent has been resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused.
Resolved
This incident is now resolved. We are also noting that some other parts of honeycomb (the query UI) may have seen spurious failures as well during the impacted period (13:22—13:44 UTC).
Resolved
This incident has been resolved.
Resolved
Update Our team has completed patching the W3 Total Cache plugin across all managed systems where the update was possible based on the current WordPress and PHP version requirements. In cases where the patch could not be applied due to compatibility constraints or other configuration limitations, the affected clients have been contacted directly with the relevant details and recommended next steps. In most instances, this involves upgrading the underlying WordPress and/or PHP versions before updating the plugin. At this time, the planned remediation work has been completed and this matter is considered resolved. Recommended Action Clients with sites running W3 Total Cache version 2.9.1 or earlier are encouraged to update to the patched version 2.9.2 as soon as possible. Where the update is not currently possible due to WordPress or PHP version constraints, please upgrade those components first and then proceed with the plugin update. If you require assistance with completing the update, please contact our support team. Thank you for your patience and understanding while we worked to address this matter.
Resolved
All impacted services have now fully recovered.
Resolved
The issue has been resolved.
Resolved
The networking fix has been applied and all systems are operational. We have identified the root cause. Function execution has returned to normal. Any backlogs incurred during the incident will be executed.
Resolved
On 9 March UTC, Automation users in the APAC region may have experienced performance degradation within Jira, Jira Product Discovery, Jira Service Management, Jira Work Management, Confluence. The issue has now been resolved, and the service is operating normally for all affected customers.
Resolved
On 9 March UTC, Automation users in the APAC region may have experienced performance degradation within Jira, Jira Product Discovery, Jira Service Management, Jira Work Management, Confluence. The issue has now been resolved, and the service is operating normally for all affected customers.
Resolved
This incident has been resolved and system performance has returned to normal. Thank you for your patience while we worked to resolve the issue.
Resolved