30 Attio incidents · januar 2024 — official updates, affected components, duration and resolution details.
Et problem er blevet identificeret. Vi har identificeret årsagen, og vores team arbejder på at løse problemet så hurtigt som muligt.
Spørgsmålet er nu løst. Vi beklager ulejligheden.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi undersøger rapporter om forsinkelser til formel attribut invalideringer, vores team arbejder på at løse problemet så hurtigt som muligt.
Vi har identificeret årsagen til forsinkelserne i formula opdateringer og arbejder gennem backlog. Nogle formler kan fortsætte med at vise forældede værdier, indtil behandlingen indhente.
En rettelse er blevet anvendt og formel opdateringer er behandling normalt igen. Den resterende forsinkelse er ved at indhente det forsømte, og vi forventer, at det bliver ryddet inden for den næste time.
Det spørgsmål, der forårsager forsinkelser til formel opdateringer er nu blevet løst, og efterslæbet er blevet fuldt behandlet. Vi beklager ulejligheden.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi har identificeret et problem, der forårsager en forsinkelse i alle workflow-kørsler. Vi arbejder på at genoptage behandlingen så hurtigt som muligt og undskylde ulejligheden.
Vi fortsætter med at reagere på en hændelse, der påvirker udførelsen af arbejdsblokken og levering af webhook.
Vi fortsætter med at reagere på problemer med udførelse af workflow og levering af webhook. Vi er også klar over den potentielle indvirkning på import- / eksportdelsystemerne samt Ask Attio. Vi arbejder på at genoprette tjenestens tilgængelighed.
Spørgsmålet om udførelse af workflow og levering af webhook er nu løst. Vi beklager ulejligheden.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi efterforsker rapporter om problemer med adgang til en intim platform. Vi undersøger i øjeblikket årsagen, og vores team arbejder på at løse problemet så hurtigt som muligt.
Vores team har indsat et fix for problemet og er i øjeblikket at overvåge systemet for at sikre, at problemet er løst.
Det identificerede spørgsmål er nu løst. Vores team har indsat et fix for problemet og er i øjeblikket at overvåge systemet for at sikre, at problemet er løst.
Spørgsmålet er nu løst. Vi beklager ulejligheden.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi efterforsker rapporter om, at arbejdsgange ikke udløser. Vi undersøger i øjeblikket årsagen, og vores team arbejder på at løse problemet så hurtigt som muligt.
Et problem er blevet identificeret. Vi har identificeret årsagen, og vores team arbejder på at løse problemet så hurtigt som muligt.
Vores team har indsat et fix for problemet og er i øjeblikket at overvåge systemet for at sikre, at problemet er løst.
Mellem 16: 33 og 18: 01 UTC den 21. juli 2026, nogle arbejdsgange kunne ikke udløse korrekt. Hvad skete der? En infrastrukturkonfigurationsændring, der blev foretaget kort før hændelsen, forårsagede en fejl ved kryptering af indholdet af nyligt modtagne arbejdsgange, hvilket forårsagede nogle arbejdsgange, der ikke kørte korrekt. Det vi gjorde: Vi vendte om og korrigerede den underliggende infrastrukturkonfiguration. Alle berørte workflow udløser genoptaget behandling normalt 18: 01 UTC, og vi har siden bekræftet udløsere fungerer korrekt. Vi fortsætter med at undersøge, om vi kan komme ud af den tid. Vi opdaterer denne side, så snart vi har en opdatering.
Spørgsmålet er nu blevet løst, og vi har direkte underrettet alle kunder, der blev påvirket af denne afbrydelse. Vi beklager ulejligheden.
Automatisk oversat fra den officielle hændelsesopdatering.
We're investigating reports of intimitent errors across some platform features. We are currently investigating the root cause and our team is working to resolve the issue as quickly as possible.
We've identified the issue caused by an upstream provider - our team is working to mitigate the issue as quickly as possible.
The issue has now been resolved. We apologize for any inconvenience caused.
We’re addressing an issue where some users may be unable to view email content (and in some cases access other stored content like call recordings, file uploads, or exports). We’ve identified the problem and we’re working on a fix now.
The issue has been resolved. Our team deployed a fix and is monitoring the system to confirm stability. The disruption occurred 08:34 - 09:48 and 10:26 - 10:40 UTC.
The issue has now been resolved. We’re sorry for any inconvenience caused.
The Attio team has identified a spike in errors when querying records and lists. Users may experience errors when loading record and list views or when using query endpoints on the public API. We are currently investigating the root cause and working to resolve the issue as quickly as possible.
The identified issue has now been resolved. Our team has deployed a fix for the issue and are currently monitoring the system to ensure the issue is resolved.
The issue has now been resolved. We’re sorry for any inconvenience caused.
We're investigating reports of intimitent platform availability issues. We are currently investigating the root cause and our team is working to resolve the issue as quickly as possible.
We’re currently experiencing service degradation due to an issue with one of our upstream providers. We’re working closely with them to restore full functionality as soon as possible.
We are continuing to work with our upstream provider as they work toward a full resolution. We’ll share further updates as soon as more information becomes available.
Our upstream provider has resolved the underlying issue, and the platform is now available again. We’re currently working through a backlog of background tasks, but all core functionality has been restored
The issue has now been resolved. We apologize for any inconvenience caused.
We are investigating a system outage that is affecting our realtime sync engine. The realtime engine is responsible for updating information in the UI of our applications as changes are received by our backend. As a workaround, refreshing the page will ensure the latest information is available in the UI.
The identified issue has now been resolved. Our team has deployed a fix for the issue and are currently monitoring the system to ensure the issue is resolved.
The issue has now been resolved. We’re sorry for any inconvenience caused.
An issue has been identified causing elevated latency in the web app & api. We are currently investigating the root cause and our team is working to resolve the issue as quickly as possible.
We have identified the root cause and our team is working to resolve the issue as quickly as possible.
The issue has now been resolved. We’re sorry for any inconvenience caused.
We are currently investigating the root cause and our team is working to resolve the issue as quickly as possible.
The issue has now been resolved. We’re sorry for any inconvenience caused.
We're aware of an issue with a downstream provider that is impacting platform availability. Our team is working to resolve the issue as quickly as possible.
We're currently investigating a major issue with one of our infrastructure providers that's resulting in increased latency for users. A small subset of users may also be unable to access the platform entirely. We're working to resolve this as quickly as possible and will continue to provide updates.
We're seeing signs of recovery and are closely monitoring the situation. We'll continue to share updates as we receive them from our infrastructure provider.
The platform is now fully operational. We’re continuing to monitor our infrastructure provider for any further updates and ongoing stability. Thank you for your patience while we resolved the issue.
We have identified an issue that is causing delays in the delivery of outbound email traffic across all email sending functionality (including sequences). The team is actively investigating the root cause of the issue and working to establish mitigations.
The issue has now been resolved. We’re sorry for any inconvenience caused.
We are currently investigating reports of platform availability issues, our team is working to resolve the issue as quickly as possible.
The identified issue has now been resolved. Our team has deployed a fix for the issue and are currently monitoring the system to ensure the issue is resolved.
The issue has now been resolved. We’re sorry for any inconvenience caused.
An issue has been been identified with our Developer API returning an elevated number of 5xx class errors. Our team is currently investigating and we are working to resolve the issue as quickly as possible.
The identified issue has now been resolved. Our team has deployed a fix for the issue and are currently monitoring the system to ensure the issue is resolved.
The issue has now been resolved. We’re sorry for any inconvenience caused.
An issue has been been identified. We are currently investigating the root cause and our team is working to resolve the issue as quickly as possible.
An issue has been been identified. We have identified the root cause and our team is working to resolve the issue as quickly as possible.
Our team has deployed a fix for the issue and are currently monitoring the system to ensure the issue is fully resolved.
The issue has now been resolved. We’re sorry for any inconvenience caused.
We are currently investigating a delay in our search indexing system when records are created or updated.
The issue has now been resolved. We’re sorry for any inconvenience caused.
We are aware of an issue affecting the speed of CSV Imports. Our team are currently working to resolve the issue.
The identified issue has now been resolved. Our team has deployed a fix for the issue and are currently monitoring the system to ensure the issue is resolved.
The issue has now been resolved. We’re sorry for any inconvenience caused.
We are investigating reports of some Workflows experiencing a delay in executing.
The identified issue has now been resolved. Our team has deployed a fix for the issue and are currently monitoring the system to ensure the issue is resolved.
The issue has now been resolved. We’re sorry for any inconvenience caused.
