DNSimpleCSS styles not loading for dnsimple.com
This incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This network issue has been resolved fully. If you have any further issues please let us know by emailing support@dnsimple.com
Resolved
Cache edge performance has been stable for some time, and we have seen no further issues. The incident is now closed.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The rollback has completed, and DNS resolution has returned to normal behavior. We will be making follow-up improvements to alias-resolution handling, including additional safeguards and testing to prevent recurrence.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue has been resolved and chat is now functioning normally. We apologize for any inconvenience this caused.
Resolved
This incident has been resolved. Runs should now be accessible in the EU LangSmith UI. Please let us know at support@langchain.dev if you're still experiencing issues.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The maintenance is complete and checkout is now available. Thankyou for your patience.
Resolved
The Inngest incident causing Git Sync delays has been resolved. Everything should be back to normal! Please note that any syncs that didn't go through during the incident won't be retried automatically, so you'll need to push again to trigger a new sync. If you're still seeing any issues, reach out and we'll take a look!
Resolved
Our engineering team has implemented a fix, and course access is now functioning as expected.
Resolved
This incident has been resolved, the backlog of jobs has processed successfully.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue causing 404 errors when editing and deleting Zap templates has been resolved. Users attempting to edit templates were encountering 404 errors due to a routing misconfiguration introduced during an ATC (Application Traffic Control) rollout, which changed the default ATC origin from the monolith to the marketing site. This broke routing for the /zap-templates path, causing edit actions to fail. The fix was deployed by completing the ATC routing correction to production. Once the rollout completed, edit functionality was restored. A remaining cosmetic bug — where the UI incorrectly indicates a template deletion failed despite the deletion succeeding — has been identified as a separate, no-impact bug and does not affect actual data. No data was lost as a result of this incident. If you're still experiencing issues, please contact Support by clicking above or visit: https://zapier.com/app/get-help Thank you for your patience.
Resolved
This incident has been resolved.
Resolved
The incident is now resolved and the system is full operational.
Resolved
This issue is now resolved.
Resolved
This issue is now resolved.
Resolved
This incident has been resolved.
Resolved
We recently addressed issues affecting the “All Files” page in Box. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future. Between **3:00 PM PDT** and **9:34 PM PDT** on **March 19, 2026**, some users may have experienced difficulties while working in Box. During this time, users accessing Box through the web application may have encountered blank pages when navigating into folders on the “All Files” page or when opening certain shared links. The issue occurred as a result of a recent code change, made in our ongoing effort to improve performance and stability. We were able to resolve the issue by reverting the web application to the previous stable version. In addition, we are strengthening safeguards in our deployment and rollback processes to prevent similar issues from occurring in the future. **Analysis** The incident revealed areas for improvement in automation reliability, validation controls, and the consistency of rollout and rollback mechanisms, which contributed to an unintended artifact version being promoted to the production environment. **Corrective Actions** Box has initiated the following corrective actions: * **Strengthen deployment validation and gating mechanisms**: We are implementing stricter automated checks to verify artifact integrity, version correctness, and configuration alignment at each stage of the pipeline, ensuring only validated and approved builds can be promoted to production. * **Standardize and reinforce rollout and rollback procedures**: We are establishing consistent, well-documented deployment and rollback workflows with automated safeguards and audit trails to ensure reliable reversibility and prevent incorrect artifact promotion during release operations. 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
We've identified an issue that was preventing the workflow builder from adding Event campaign triggers. This did not affect processing or deliveries for existing campaigns, only the workflow UI experience was impacted. This incident has already been resolved.
Resolved
Activity Log is ingesting events again. We had no loss in data.
Resolved
All impacted services have now fully recovered.
Resolved
On April 9, 2026, between 03:22 UTC and 04:49 UTC, GitHub Notifications experienced degraded availability. During this time, approximately 45% of requests to the notifications service returned errors, with a peak error rate of approximately 54%, preventing affected users from successfully viewing or interacting with their notifications service. The issue was identified and resolved, restoring the service to full availability.<br /><br />We are working to improve our metrics to reduce time to detection and mitigation for similar issues in the future.
Resolved
We identified and fixed an issue with our verify API endpoint.
Resolved
This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Issue appears to be resolved
Resolved