Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Livechat driftsforstyrrelser

    30 Livechat incidents · marts 2015 — official updates, affected components, duration and resolution details.

    Tilbage til aktuel status

    Funktionsfejl

    Startede 14. oktober 2026 kl. 02.08 UTC · 1h 51m

    IssuesMindre hændelse
    1. 14. oktober 2026 kl. 02.08 UTCidentified

      Vi er i øjeblikket ved at undersøge problemet med arbejdsgange. Vi undskylder for eventuelle ulemper dette kan forårsage, og vores team arbejder flittigt på at løse problemet så hurtigt som muligt.

    2. 14. oktober 2026 kl. 03.07 UTCidentified

      Vi har identificeret årsagen til problemet og arbejder på et fix. Service kan forblive forringet, mens vi gennemfører løsningen. Vi vil give en opdatering, så snart vi har flere detaljer eller en anslået tid til løsning.

    3. 14. oktober 2026 kl. 03.36 UTCmonitoring

      De nødvendige rettelser er blevet anvendt med succes på systemet. I øjeblikket overvåger vi aktivt resultaterne for at vurdere effektiviteten af disse ændringer og sikre, at alt fungerer efter hensigten.

    4. 14. oktober 2026 kl. 03.59 UTCresolved

      Problemet med arbejdsgange er løst, og tjenesterne fungerer nu normalt. Vi undskylder for eventuelle forstyrrelser, og værdsætter din tålmodighed og forståelse.

    Automatisk oversat fra den officielle hændelsesopdatering.

    Funktionsfejl

    Startede 12. oktober 2026 kl. 17.21 UTC · 7h 39m

    OutageStørre hændelse
    1. 12. oktober 2026 kl. 17.21 UTCidentified

      Vi har identificeret årsagen til problemet og arbejder på et fix. Service kan forblive forringet, mens vi gennemfører løsningen. Vi vil give en opdatering, så snart vi har flere detaljer eller en anslået tid til løsning.

    2. 12. oktober 2026 kl. 17.45 UTCidentified

      Vores team arbejder stadig aktivt på fixet. Arbejdsstrømmene kan i mellemtiden forblive forringede. Vi sætter pris på din tålmodighed og vil dele en anden opdatering, så snart vi har flere detaljer eller en anslået tid til løsning.

    3. 12. oktober 2026 kl. 18.12 UTCidentified

      Vores hold fortsætter med at arbejde på fixet. Arbejdsstrømmen er fortsat forringet. Næste opdatering at følge.

    4. 12. oktober 2026 kl. 18.40 UTCidentified

      Vi arbejder stadig på at løse dette problem, og arbejdsgange fortsætter med at blive nedbrudt. Vores ingeniører fokuserer stadig på at implementere fixet, og vi overvåger situationen nøje. Vi deler mere information, så snart den er tilgængelig.

    5. 12. oktober 2026 kl. 19.01 UTCidentified

      Vi arbejder stadig aktivt på fixet. Service forbliver påvirket, og vores ingeniører er fokuseret på at få tingene tilbage til normal. Tak for din tålmodighed. Vi deler yderligere oplysninger, så snart de er tilgængelige.

    6. 12. oktober 2026 kl. 19.25 UTCidentified

      Problemet er endnu ikke løst, og vores team arbejder stadig på løsningen. Vi opdaterer dig igen, så snart vi har flere oplysninger.

    7. 12. oktober 2026 kl. 19.55 UTCidentified

      Vi arbejder stadig på at genoprette tjenesten, som stadig er forringet. Vores ingeniører er fuldt engageret, og vi er kede af den fortsatte afbrydelse. Vi deler endnu en opdatering, så snart vi har fremskridt at rapportere.

    8. 12. oktober 2026 kl. 20.26 UTCidentified

      Vi arbejder stadig på at genoprette tjenesten. Vi beklager forstyrrelsen og værdsætter din tålmodighed. Vi deler en ny opdatering, så snart vi har mere at rapportere.

    9. 12. oktober 2026 kl. 21.04 UTCidentified

      Vi arbejder stadig på at genoprette tjenesten. Vi gør fremskridt og nærmer os løsningen. Tak for din tålmodighed.

    10. 12. oktober 2026 kl. 22.02 UTCidentified

      Service forbliver forringet, og vi ved dette har været i gang i flere timer. Vores hold arbejder stadig på at genoprette den. Vi beklager forstyrrelsen.

    11. 12. oktober 2026 kl. 23.12 UTCidentified

      Brugen af arbejdsgange forringes fortsat. Vores team arbejder aktivt på at genoprette fuld funktionalitet. Vi undskylder for den langvarige forstyrrelse og enhver ulejlighed dette kan forårsage.

    12. 13. oktober 2026 kl. 00.14 UTCidentified

      Funktionen af arbejdsgange oplever stadig forringelse. Vores team arbejder flittigt på at genoprette den til fuld kapacitet. Vi undskylder for den udvidede forstyrrelse og enhver ulejlighed dette kan skabe.

    13. 13. oktober 2026 kl. 00.23 UTCmonitoring

      De nødvendige rettelser er blevet anvendt med succes på systemet. I øjeblikket overvåger vi aktivt resultaterne for at vurdere effektiviteten af disse ændringer og sikre, at alt fungerer efter hensigten.

    14. 13. oktober 2026 kl. 01.00 UTCresolved

      Problemet med arbejdsgange er løst, og tjenesterne fungerer nu normalt. Vi undskylder for eventuelle forstyrrelser, og værdsætter din tålmodighed og forståelse.

    Automatisk oversat fra den officielle hændelsesopdatering.

    Login-spørgsmål

    Startede 26. september 2026 kl. 13.00 UTC · 58m

    IssuesMindre hændelse
    1. 26. september 2026 kl. 13.00 UTCinvestigating

      Vi har problemer med at logge ind på LiveChat. Vores team er klar over problemet og arbejder på at løse det så hurtigt som muligt

    2. 26. september 2026 kl. 13.18 UTCinvestigating

      Vi undersøger et problem, der påvirker nogle kunder. Vores team arbejder på at identificere årsagen og genoprette normal service så hurtigt som muligt. Vi vil dele en opdatering, så snart mere information er tilgængelig.

    3. 26. september 2026 kl. 13.52 UTCmonitoring

      Et fix er blevet gennemført, og vi overvåger resultaterne. Nogle kunder kan stadig opleve mindre forstyrrelser, mens systemerne komme sig. Vi deler opdateringer, hvis situationen ændrer sig.

    4. 26. september 2026 kl. 13.58 UTCresolved

      Problemet er løst, og tjenesterne fungerer normalt. Der forventes ingen yderligere indvirkning.

    Automatisk oversat fra den officielle hændelsesopdatering.

    Problemer med at åbne filer

    Startede 28. juli 2026 kl. 11.27 UTC · 1d 1h

    IssuesMindre hændelse
    1. 28. juli 2026 kl. 11.30 UTCidentified

      Vi har konstateret, at problemet er relateret til en ekstern udbyder. Vi samarbejder med dem om at undersøge og løse problemet. Tjenesten kan forblive forringet, mens problemet behandles. Vi vil give en opdatering, så snart vi har flere detaljer eller en anslået tid til løsning.

    2. 28. juli 2026 kl. 11.54 UTCinvestigating

      Vi undersøger et problem, der påvirker nogle kunder. Problemet kan være relateret til en ekstern udbyder, og vi arbejder på at bekræfte årsagen og genoprette normal service så hurtigt som muligt. Vi vil dele en opdatering, så snart mere information er tilgængelig.

    3. 28. juli 2026 kl. 13.49 UTCinvestigating

      Vi fortsætter med at arbejde sammen med tredjepartsudbyderen for at løse problemet. På nuværende tidspunkt afventer vi yderligere oplysninger fra dem som led i deres revisionsproces. Vi vil give vores næste opdatering, så snart vi har yderligere oplysninger at dele eller der er en betydelig ændring af situationen. Tak for din tålmodighed.

    4. 29. juli 2026 kl. 13.01 UTCresolved

      Problemet med at åbne filer er blevet løst, og tjenester fungerer normalt. Vi er kede af eventuelle forstyrrelser og takker for jeres tålmodighed og forståelse.

    Automatisk oversat fra den officielle hændelsesopdatering.

    Workflow degraded performance

    Startede 10. juli 2026 kl. 02.24 UTC · 17m

    IssuesMindre hændelse
    1. 10. juli 2026 kl. 02.24 UTCinvestigating

      We have identified a problem affecting Workflows. The Infrastructure team is actively investigating. We will share more information as soon as we have updates.

    2. 10. juli 2026 kl. 02.36 UTCidentified

      We’ve identified the issue affecting Workflows and are working on a fix.

    3. 10. juli 2026 kl. 02.38 UTCidentified

      Fix applied, we are waiting for the service to return to normal.

    4. 10. juli 2026 kl. 02.41 UTCresolved

      The issue has been resolved, and we can confirm that services are operating normally again.

    Workflow degraded performance

    Startede 12. juni 2026 kl. 22.25 UTC · 1h 6m

    IssuesMindre hændelse
    1. 12. juni 2026 kl. 22.25 UTCinvestigating

      We have identified a problem affecting Workflows. The Infrastructure team is actively investigating. We will share more information as soon as we have updates.

    2. 12. juni 2026 kl. 22.33 UTCidentified

      We’ve identified the issue affecting Workflows and are working on a fix.

    3. 12. juni 2026 kl. 22.55 UTCidentified

      Fix applied, we are waiting for the service to return to normal.

    4. 12. juni 2026 kl. 23.07 UTCmonitoring

      The issue was fixed, and we can confirm that services are working correctly again. Some customers may still notice minor disruptions while systems fully recover. We appreciate your patience and will continue to keep you informed if anything changes.

    5. 12. juni 2026 kl. 23.30 UTCresolved

      The issue has been resolved, and we can confirm that services are operating normally again.

    LiveChat - Issues with reports from Export Raw Data

    Startede 25. maj 2026 kl. 05.30 UTC · 44m

    OutageStørre hændelse
    1. 25. maj 2026 kl. 05.30 UTCinvestigating

      We are investigating an issue affecting some customers. They are unable to generate reports in the Export raw data section for LiveChat. The scheduled reports may also be not delivered by email.

    2. 25. maj 2026 kl. 06.08 UTCmonitoring

      We implemented a fix, and we are now monitoring the situation to ensure stability. Some customers may still notice delays with receiving the report while the reporting systems fully recover. We appreciate your patience and will continue to keep you informed if anything changes.

    3. 25. maj 2026 kl. 06.15 UTCresolved

      The issue has been resolved, and services are operating normally. No further impact is expected. We’re sorry for any disruption this may have caused and thank you for your patience and understanding.

    Workflows delay

    Startede 19. maj 2026 kl. 02.11 UTC · 2h 4m

    Pending
    1. 19. maj 2026 kl. 02.32 UTCinvestigating

      We are investigating an issue affecting some customers. We are working to confirm the cause and restore normal service as quickly as possible. We will share an update as soon as more information is available.

    2. 19. maj 2026 kl. 03.45 UTCmonitoring

      We implemented a fix, and we are now monitoring the situation to ensure stability. Some customers may still notice minor disruptions while systems fully recover. We appreciate your patience and will continue to keep you informed if anything changes.

    3. 19. maj 2026 kl. 04.15 UTCresolved

      The issue has been resolved, and services are operating normally. No further impact is expected. We’re sorry for any disruption this may have caused and thank you for your patience and understanding.

    Issues with adding new Knowledge Sources

    Startede 13. maj 2026 kl. 11.33 UTC · 33m

    IssuesMindre hændelse
    1. 13. maj 2026 kl. 11.33 UTCinvestigating

      We are investigating an issue that prevents some customers from adding new Knowledge Sources. Our team is working to identify the root cause and restore normal service as quickly as possible. We will share an update as soon as more information is available.

    2. 13. maj 2026 kl. 11.40 UTCmonitoring

      A fix has been implemented, and we are monitoring the results. The ability to add new Knowledge Sources has been restored.

    3. 13. maj 2026 kl. 12.06 UTCresolved

      The issue has been resolved, and services are operating normally. No further impact is expected.

    LiveChat - outage

    Startede 25. februar 2026 kl. 04.33 UTC · 1d 5h

    OutageKritisk hændelse
    1. 25. februar 2026 kl. 04.33 UTCinvestigating

      We are currently investigating an issue affecting some customers' ability to access LiveChat and working to understand the cause. We’ll share another update as soon as we have more information.

    2. 25. februar 2026 kl. 04.37 UTCinvestigating

      We are currently investigating an issue affecting some customers' ability to access LiveChat and working to understand the cause. We detected an issue with our cloud provider. We’ll share another update as soon as we have more information.

    3. 25. februar 2026 kl. 04.57 UTCidentified

      We have identified the cause of the issue affecting some customers and are working on a fix. Service may still be degraded while we complete the necessary steps. We are working with our Cloud provider to resolve the issue. We’ll share another update as soon as we have more information.

    4. 25. februar 2026 kl. 05.22 UTCidentified

      Our team is actively working to resolve the issue. We will share another update as soon as we have more details.

    5. 25. februar 2026 kl. 05.44 UTCidentified

      We are still actively working to resolve the issue. We will provide further updates as we make progress.

    6. 25. februar 2026 kl. 06.08 UTCidentified

      We are actively implementing steps to resolve the problem. We will share the next update as soon as possible.

    7. 25. februar 2026 kl. 06.30 UTCidentified

      Work on resolving the issue is ongoing. We will provide another update as soon as we have more information.

    8. 25. februar 2026 kl. 06.51 UTCidentified

      Our team continues to investigate the issue and work toward a resolution. We will provide further updates as soon as they are available.

    9. 25. februar 2026 kl. 07.06 UTCidentified

      We are observing ongoing recovery on the side of Google, and our services are gradually returning to normal availability. We will continue to monitor the situation and provide further updates as needed.

    10. 25. februar 2026 kl. 07.11 UTCmonitoring

      We are seeing improvements in our service availability and are now moving to closely monitor the situation. We will provide further updates when necessary.

    11. 25. februar 2026 kl. 07.42 UTCmonitoring

      Services are operational, and we are actively monitoring to maintain stability.

    12. 25. februar 2026 kl. 08.05 UTCmonitoring

      We continue to monitor the situation to ensure everything remains stable.

    13. 25. februar 2026 kl. 11.25 UTCmonitoring

      **Brief status update and additional context on the ongoing incident** This incident is related to an issue within our cloud provider’s infrastructure (GCP). We’re actively coordinating with their engineering teams since the beginning of the incident and staying in continuous contact as they work through mitigation and recovery steps. The incident hasn’t been resolved on their end yet. Minor performance issues persist, but these are limited in scale and do not affect overall availability for customers.

    14. 25. februar 2026 kl. 11.57 UTCidentified

      We have identified the cause of the issue affecting some customers and are working on a fix. Access to Archives and Reports may be degraded while we complete the necessary steps.

    15. 25. februar 2026 kl. 12.48 UTCmonitoring

      We are monitoring the situation to ensure everything remains stable. Some customers may still notice minor disruptions while systems fully recover.

    16. 25. februar 2026 kl. 13.36 UTCmonitoring

      We continue to monitor the situation to ensure stability. While systems are recovering, some customers may still experience minor disruptions as we await a permanent fix from our service provider. While the issue has not yet been fully resolved on their end, we have been actively coordinating with their engineering teams since the incident began and remain in close contact as they progress through mitigation and recovery efforts.

    17. 25. februar 2026 kl. 15.02 UTCmonitoring

      We are continuously monitoring the service to ensure continuity and stability while we are waiting for a fix from our service provider. Some customers may experience minor disruptions during that time. We remain in close contact with the provider’s engineering teams, and the issue has not yet been resolved on their end.

    18. 25. februar 2026 kl. 16.03 UTCmonitoring

      We are continuously monitoring the service to ensure continuity and stability while we await a fix from our service provider. Some customers may still experience degraded performance during this time.

    19. 25. februar 2026 kl. 17.00 UTCmonitoring

      We are continuously monitoring the service to ensure continuity and stability while we await a fix from our cloud provider’s infrastructure, **Google Cloud Platform (GCP)**. Some customers may still experience degraded performance during this time. We remain in close contact with GCP’s engineering teams, and the issue has not yet been resolved on their end. During this period, customers may experience delays when starting chats or sending messages.

    20. 25. februar 2026 kl. 17.49 UTCinvestigating

      Our team is working closely with **Google Cloud Platform (GCP)** to resolve the issue. While chats can be started, customers may experience delays or failures when sending messages.

    21. 25. februar 2026 kl. 18.13 UTCidentified

      We are implementing additional mitigation measures. Chat sessions may start successfully; however, some messages may be delayed or not delivered. We are actively working on a fix, and the estimated time to resolution is approximately 20 minutes.

    22. 25. februar 2026 kl. 18.28 UTCidentified

      We are continuing to deploy the fix and will provide an update shortly.

    23. 25. februar 2026 kl. 18.43 UTCmonitoring

      Deployment of the fix is complete. We are monitoring the service to ensure full stability.

    24. 26. februar 2026 kl. 05.22 UTCinvestigating

      We are currently investigating an issue affecting some customers and working to understand the cause. We’ll share another update as soon as we have more information.

    25. 26. februar 2026 kl. 05.31 UTCmonitoring

      A fix has been implemented and we are monitoring the situation to ensure everything remains stable. Some customers may still notice minor disruptions while systems fully recover.

    26. 26. februar 2026 kl. 10.19 UTCresolved

      A fix has been implemented, and we see that our assets become available and reports a healthy status. We’ve been monitoring the situation, and will continue checks

    Messages sent via the chat widget are delayed

    Startede 21. februar 2026 kl. 18.26 UTC · 32m

    IssuesMindre hændelse
    1. 21. februar 2026 kl. 18.26 UTCinvestigating

      Many customers experienced delays of up to 30 seconds when sending messages via the chat widget. We are currently investigating the problem

    2. 21. februar 2026 kl. 18.52 UTCinvestigating

      We are still investigating the problem. The delay was shortened, but it is still occurring.

    3. 21. februar 2026 kl. 18.54 UTCmonitoring

      The problem should be resolved now. We are moving to monitoring.

    4. 21. februar 2026 kl. 18.57 UTCresolved

      The incident has been resolved and services are now operating as expected. We will continue to monitor the situation, but no further impact is anticipated.

    Messages sent in the chat widget may be delayed

    Startede 10. februar 2026 kl. 17.04 UTC · 1h 6m

    IssuesMindre hændelse
    1. 10. februar 2026 kl. 17.04 UTCinvestigating

      We are currently observing delays when sending messages via the chat widget. Our team is investigating the issue and working on a fix. Updates will be shared as we learn more.

    2. 10. februar 2026 kl. 17.21 UTCinvestigating

      Our team is continuing to investigate the cause of the message delays in the chat widget. We’re actively working toward a resolution and will share further updates shortly.

    3. 10. februar 2026 kl. 17.32 UTCidentified

      We have identified the cause of the delays affecting message delivery in the chat widget. Our team is working on implementing a fix and will provide an update once resolved.

    4. 10. februar 2026 kl. 17.51 UTCidentified

      Engineering is still working on the resolution, and we are closely monitoring progress to restore normal functionality as quickly as possible.

    5. 10. februar 2026 kl. 18.06 UTCmonitoring

      The fix for the chat widget message delays has been implemented. We are monitoring the system to ensure normal functionality is fully restored.

    6. 10. februar 2026 kl. 18.10 UTCresolved

      This incident has been resolved and services are operating normally. Thank you for your patience.

    Performance degradation of our services

    Startede 20. januar 2026 kl. 23.28 UTC · 2h 14m

    IssuesMindre hændelse
    1. 20. januar 2026 kl. 23.28 UTCinvestigating

      We noticed a performance degradation in our services related to issues with our cloud provider. We're currently investigating this issue.

    2. 21. januar 2026 kl. 00.08 UTCinvestigating

      We have received a communication from the cloud provider's engineers stating that they are reviewing our case.

    3. 21. januar 2026 kl. 00.48 UTCinvestigating

      We are still investigating the situation and working with our cloud provider engineers to implement the fix.

    4. 21. januar 2026 kl. 01.28 UTCmonitoring

      After discussing the issue with our admins, the cloud provider engineers are still working on the case and investigating further. Currently, we are not seeing any further issues, but we are still monitoring the situation.

    5. 21. januar 2026 kl. 01.43 UTCresolved

      We see that the issue within our cloud provider’s infrastructure has been mitigated, and we can confirm that the infrastructure is healthy, and we are not seeing further errors. Throughout the degradation, our platform was able to maintain service continuity. We appreciate your patience and understanding while we coordinated our efforts with the cloud provider’s engineers to address the issue.

    Performance degradation of our services

    Startede 20. januar 2026 kl. 16.24 UTC · 4h 12m

    IssuesMindre hændelse
    1. 20. januar 2026 kl. 16.24 UTCinvestigating

      We noticed a performance degradation in our services related to issues with our cloud provider. We're currently investigating this issue.

    2. 20. januar 2026 kl. 16.43 UTCidentified

      We identified the cause of this issue and are actively working on a fix.

    3. 20. januar 2026 kl. 17.01 UTCidentified

      We’re continuing to work on a fix. More updates will be shared soon.

    4. 20. januar 2026 kl. 17.22 UTCidentified

      We are actively working to fully restore normal service performance. Thank you for your patience.

    5. 20. januar 2026 kl. 17.43 UTCidentified

      We’re still working on the fix and continuing to monitor system stability. The issue is not spreading, but parts of the infrastructure are still experiencing degraded performance. Further updates to follow.

    6. 20. januar 2026 kl. 18.04 UTCidentified

      We’re making progress and are currently rolling out a fix. We’ll continue monitoring closely and share further updates as they become available.

    7. 20. januar 2026 kl. 18.32 UTCidentified

      We’re continuing to roll out a fix and are seeing services recover. Work is still ongoing; we’ll share another update shortly.

    8. 20. januar 2026 kl. 18.52 UTCidentified

      We’re continuing to roll out the fix and closely monitoring service health. We’ll provide another update soon.

    9. 20. januar 2026 kl. 19.22 UTCidentified

      **Brief status update and additional context on the ongoing incident** This incident is related to an issue within our cloud provider’s infrastructure. We’re actively coordinating with their engineering teams since the beginning of the incident and staying in continuous contact as they work through mitigation and recovery steps. Our platform has remained available throughout, thanks to built-in redundancy and failover across multiple locations. While parts of the underlying infrastructure are experiencing problems, we are continuing to serve traffic and deliver the service without a full outage. That said, customers may still experience intermittent degraded performance (for example, increased latency or occasional timeouts) while remediation is in progress. We’re monitoring service health closely and will provide further updates as we have more information from the cloud provider, but no later than one hour from now.

    10. 20. januar 2026 kl. 20.12 UTCmonitoring

      The issue within our cloud provider’s infrastructure has been mitigated, and all affected resources have been fully restored. Our platform continues to operate normally, and we are no longer observing the previously reported degraded performance. We are actively and continuously monitoring our internal services to ensure everything is functioning as expected and to confirm sustained stability. We will provide further updates within an hour

    11. 20. januar 2026 kl. 20.36 UTCresolved

      The issue within our cloud provider’s infrastructure has been mitigated, and we can confirm that all affected resources have been fully restored. Our platform has remained available throughout, thanks to built-in redundancy and failover across multiple locations. While parts of the underlying infrastructure were experiencing problems, we continued to serve traffic and deliver the service without a full outage. Thank you for your patience and understanding while we coordinated our efforts with cloud provider’s engineers to address the issue.

    Chat widget not working on Text websites

    Startede 20. januar 2026 kl. 14.50 UTC · 18m

    IssuesMindre hændelse
    1. 20. januar 2026 kl. 14.50 UTCinvestigating

      Chat widget on Text websites is not responding. Customer’s licenses are not affected.

    2. 20. januar 2026 kl. 14.56 UTCmonitoring

      Fixes have been applied, we are monitoring the performance

    3. 20. januar 2026 kl. 15.08 UTCresolved

      Communication is fully restored now.

    Chat widget performance degradation

    Startede 20. januar 2026 kl. 14.49 UTC · 18m

    IssuesMindre hændelse
    1. 20. januar 2026 kl. 14.49 UTCinvestigating

      Degradation in performance of sending and receiving messages through the chat widget.

    2. 20. januar 2026 kl. 14.56 UTCmonitoring

      Fixes have been applied, we are monitoring the performance

    3. 20. januar 2026 kl. 15.07 UTCresolved

      Full widget performance was restored.

    Some users might not be able to access the LiveChat app

    Startede 13. januar 2026 kl. 07.03 UTC · 9m

    IssuesMindre hændelse
    1. 13. januar 2026 kl. 07.03 UTCinvestigating

      We are currently investigating this issue. We will post further updates as soon as we know more.

    2. 13. januar 2026 kl. 07.11 UTCresolved

      The fix has been implemented and the issue has been resolved.

    App login issue

    Startede 9. december 2015 kl. 19.07 UTC · 0m

    Pending
    1. 22. december 2025 kl. 11.53 UTCinvestigating

      Some agents are experiencing app login issues. We are investigating the case.

    2. 22. december 2025 kl. 11.53 UTCmonitoring

      Issue seems to be fixed. We are monitoring servers' performance.

    3. 22. december 2025 kl. 11.53 UTCresolved

      This problem has been resolved.

    CDN provider issue

    Startede 8. december 2015 kl. 20.29 UTC · 0m

    Pending
    1. 22. december 2025 kl. 11.53 UTCinvestigating

      Due to our CDN provider issues some visitors might have problems with chat window loading.

    2. 22. december 2025 kl. 11.53 UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. 22. december 2025 kl. 11.53 UTCresolved

      Problem with CDN provider issues and chat window loading has been resolved.

    DDoS attack

    Startede 4. december 2015 kl. 14.21 UTC · 0m

    Pending
    1. 22. december 2025 kl. 11.53 UTCinvestigating

      We are under DDoS attack. Some of customers might have issues with the chat.

    2. 22. december 2025 kl. 11.53 UTCmonitoring

      DDoS is under control, service is fully functional again.

    3. 22. december 2025 kl. 11.53 UTCresolved

      Problem with DDoS attack has been resolved.