Incidentsby IbisIssue Identified
Feb 11, 22:29 UTCFeb 11, 22:53 UTC
Duration
24m
Impact
Minor
Root cause
Not disclosed
Coalesce, 90 days
8 incidents
Affected
APISchedulerWeb App[Azure] centralus - Web App[Azure] centralus - API[Azure] centralus - Scheduler[Azure] eastus2 - Web App[Azure] eastus2 - API[Azure] eastus2 - Scheduler[Azure] westus2 - Web App[Azure] westus2 - API[Azure] westus2 - Scheduler[AWS] us-east-1 - Web App[AWS] us-east-1 - API
Final update
A fix was developed, tested successfully, and deployed to production. The incident is now resolved.
Timeline
- Resolved · Feb 11, 22:53 UTC
A fix was developed, tested successfully, and deployed to production. The incident is now resolved.
- Identified · Feb 11, 22:29 UTC
We have identified an issue related to our recent release where some static content is being served from a testing domain. This may impact clients with security policies that restrict traffic to specific domain names. Our team is actively working on deploying a fix to resolve this as quickly as possible. We sincerely regret any inconvenience this may cause and appreciate your patience. Temporary Workaround: Allowing content to be served from the domain coalescestage.io may help mitigate the issue while we are working towards a fix. We will provide further updates as we progress toward a resolution. If you have any questions or concerns, please reach out to our support team. Thank you for your understanding. , Coalesce Team