Customer.ioForms submissions experiencing intermittent delays
The issue has now been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
The issue has now been resolved.
Resolved
We experienced a brief interruption to our API service in the US region between 11:07 UTC and 11:08 UTC due to an issue at the AWS platform. The impact was very minimal. We apologise for any inconvenience caused.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We can confirm that the issues affecting the UpCloud API are fully resolved and all management services are operating as expected. If you continue to experience issues, please reach out to our Support team via our 24/7 Live Chat or email support@upcloud.com. We sincerely apologise for any inconvenience caused by this incident and appreciate your kind patience and understanding.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Delivery latency has returned to normal for all incoming traffic. A small number of events are queued for retry, and will be delivered within the next 15 minutes.
Resolved
Incident: [Cloudflare experienced an outage](https://blog.cloudflare.com/18-november-2025-outage/) that impacted the Workers KV service, a storage infrastructure service our MCP server relies on. This resulted in increased error rates and failed requests for a portion of our MCP traffic over the span of 3 hours. Impact: Approximately 100 users making requests to the MCP server received error responses or were unable to reach the server from 2025-11-18 11:20 UTC through 14:20 UTC. Moving forward: We are investing in our MCP Server to improve its resilience to KV store outages, and are investigating ways to reduce the overall impact of Cloudflare outages. Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.
Resolved
This incident has been resolved.
Resolved
This issue has been resolved. We apologize for any inconvenience it may have cause.
Resolved
This incident has been resolved.
Resolved
The incident has been resolved
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
All landing pages are loading as expected.
Resolved
Reverting the maintenance operation has resolved the connectivity issues.
Resolved
**Incident Summary** **–** Post-Incident Review **Detailed Root Cause Analysis Report: Device Compliance Broken in iOS Self Service 11.4.0** **Incident Start Date and Time \(in UTC\):** Nov 5, 5:46 PM UTC **Incident End Date and Time \(in UTC\):** Nov 6, 9:21 AM UTC **Severity: SEV2** **Duration: 15h 35m** **Impact:** Global disruption of Microsoft Device Compliance workflow for users using iOS Self Service 11.4.0. **Summary** On 11-05-2025 a release of iOS Self Service 11.4.0 broke the Microsoft Device Compliance workflow. Impacted users could not access resources protected by Microsoft Device Compliance policies. **Root Cause & Timeline** * **Root Cause:** Incorrect configuration of keychain access group in production release of iOS Self Service 11.4.0 * **Key Events:** * November 5, 5:46 PM UTC - Self Service 11.4.0 was released * November 5, 9:50 PM UTC - Issue with Device Compliance worfklow in Self Service 11.4.0 was escalated to Jamf * November 6, 12:18 AM UTC - Self Service 11.4.1 was submitted to Apple for expedited review * November 6, 9:21 AM UTC - Self Service 11.4.1 is available for all customers and users **Business & User Impact** * Users unable to access internal company resources protected by Microsoft Device Compliance policies. * Affected Capabilities: Device Compliance **Gaps Identified** * Gap in automated and human-driven release testing coverage. **Remediation & Next Steps** · The functionality was restored with a new release of iOS Self Service 11.4.1 that reverted the changes introduced in 11.4.0. · Test automation and human-driven release test case coverage was extended to cover the affected workflow end-to-end.
Resolved
This incident has been resolved.
Resolved
The incident has been resolved.
Resolved
The rollout of the fix for impacted videos without audio has now completed. Customers should now be able to review existing videos without audio and see that it has been properly restored. If you are continuing to see any issues with playback of your videos, please reach out to Loom support for assistance. We apologize for any inconvenience caused by this issue.
Resolved
The backfill for the CDN and Error Log reports has been completed. You should now be able to download the reports from the Dashboard or via the API as usual.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
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 November 10, 2025 between 5:00 pm PST and 5:26 pm PST, some users may have experienced slowness or temporary unavailability while working in Box. The issue occurred due to a sudden, large traffic spike on one database, which caused connection saturation on other databases, making them temporarily inaccessible. The issue was automatically resolved as our middleware service detected the problem and backed off. We are working on ways to prevent sudden traffic spikes from cascading to other systems and accelerating our middleware service’s auto-remediation process 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.
Resolved
This incident has been resolved as of 2:32PM ET.
Resolved
Between 11:15 UTC and 12:40 UTC on November 19, some customers in the EU region may have experienced difficulties in data ingest. We have investigated and resolved this service interruption and impacted services have returned to normal operations
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
US01 and US03 Dashboard and SDK services have remained stabled. The incident is now resolved.
Resolved
This incident has been resolved.
Resolved
The US02 Dashboard and SDK have remained stable since 17:18 ET. We can confirm the incident is resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Cloudflare has restored normal operation, and access to our documentation and Google Authentication is fully restored. All services are functioning as expected, and the incident is now resolved.
Resolved
Cloudflare communicated that they fixed their issue. We are resolving this incident as no related issue has been identified on our side.
Resolved
Between 11:46 UTC and 15:48 UTC on November 18th, 2025, some customers in the EU region may have experienced issues loading New Relic UI. The service interruption was investigated and resolved with our cloud provider and impacted services have returned to normal operations.
Resolved