BeamIncreased Latency
This incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has been resolved.
Resolved
Between 10:20 UTC and 11:00 UTC on December 10th, some customers in the US and EU regions may have experienced issues creating new dashboards. We have investigated and resolved this service interruption and impacted services have returned to normal operations.
Resolved
We are glad to inform you that the fix has been implemented and the incident resolved. We will run a problem investigation to understand what happened and how to prevent it from happening again. Thanks for your understanding & sorry for any inconvenience this has caused.
Resolved
Our engineering team has resolved this incident. We apologise for any inconvenience this may have caused.
Resolved
This accident has been fully resolved, after monitoring we confirmed that all functionality returned to normal
Resolved
The issue has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue with data export has been resolved. Impacted services have returned to normal operation
Resolved
This incident has been resolved.
Resolved
Between 22:51 UTC on Wednesday, December 5th and 02:16 UTC on December 6th, some customers in the EU region may have experienced delayed or missing alert notifications. Data processing for affected data may have been impacted. We have investigated and resolved this service interruption and impacted services have returned to normal operations.
Resolved
Incident: During an automated deployment of new code, an error in an internal networking service caused several system components to retain stale network connections. This caused requests to fail across a portion of our European data center. Impact: Users in our European datacenter were unable to load the Asana web app between 2024-12-02 2340UTC and 2024-12-03 0050UTC. The mobile app, our developer API, and app integrations saw degraded performance and an inability to modify or add data to Asana. Existing sessions on the Asana web app were mostly unaffected by this incident. Moving forward: We are adjusting our configuration of the library responsible for incorrectly retaining connections to avoid similar issues in the future. Additionally, Asana is in the process of upgrading and simplifying our internal routing infrastructure. 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
Between 07:20 UTC and 10:25 UTC on Dec 05, some customers may have experience issue with APM monitoring/tools not displaying data 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
The issue is resolved. Access to our dashboards is available as usual. Thank you again for your patience.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Between 20:48 UTC and 22:34 UTC, some customers in the US region may have experienced issues creating or editing alert conditions through the New Relic UI or API. This issue has been resolved and impacted services have returned to normal operation. Data ingest and alert notifications were not impacted.
Resolved
This incident has been resolved.
Resolved
We're all set! PandaDoc is working properly and the incident has been fully resolved. If you continue to experience any issues with this, please reach out to us using the instructions here: https://support.pandadoc.com/en/articles/9715061-how-to-contact-pandadoc-support.
Resolved
This incident has been resolved.
Resolved
We're continuing to observe successful provisioning and cleanup of query engine instances in all regions. This incident is resolved.
Resolved
RESOLVED A production data migration caused Optimize to remain in maintenance mode for 64 minutes. Affected Users: All users were unable to access Optimize during the incident. Root cause: An issue with an upstream provider caused the schema migration process to stall. Workarounds: None
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The incident with our 3rd party billing provider has been resolved and we've seen full recovery. We appreciate your patience!
Resolved
This incident is now resolved. Thanks for bearing with us!
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
This incident has been resolved.
Resolved
The incident has been resolved as the Licensify webpages are working again and not returning 404.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved