Phreesia driftsforstyrrelser

1. 22. oktober 2026 kl. 13.23 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et problem, der kan være årsag til forsinkelser i leveringen af to-faktor autentificering (2FA) koder, når brugerne forsøger at logge ind. Dette spørgsmål er begrænset til brugerlogin proces. Engineering undersøger aktivt. Vi vil levere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

2. 22. oktober 2026 kl. 14.05 UTCresolved

   Spørgsmålet, der forårsager forsinkelser i leveringen af to-faktor autentificering (2FA) koder under bruger login er blevet løst. Brugerne bør nu modtage 2FA-koder som forventet.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 14. oktober 2026 kl. 14.40 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et problem, der kan få nogle rapporter til ikke at vise som forventet. Vores ingeniørhold undersøger og arbejder tæt sammen med vores tredjepartspartner for at løse problemet. Vi vil levere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

2. 14. oktober 2026 kl. 14.48 UTCmonitoring

   Rapporter læsser nu med succes efter afbødning af vores tredjeparts partner. Vores Engineering team fortsætter med at overvåge situationen for at sikre rapportering funktionalitet vender tilbage til normal. Vi vil give yderligere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

3. 14. oktober 2026 kl. 17.49 UTCresolved

   Spørgsmålet om, hvorvidt rapporten er tilgængelig, er blevet løst efter vores tredjepartspartners afbødning.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 14. oktober 2026 kl. 13.47 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et problem, der påvirker Self-Planlægning i zone 1 og zone 2. Patienter kan støde på verifikationsfejl, når de forsøger at planlægge udnævnelser. Engineering undersøger aktivt.

2. 14. oktober 2026 kl. 14.14 UTCresolved

   Spørgsmålet, der forårsager verifikationsfejl i Self- Planlægning for zone 1 og zone 2 er blevet løst. Self-Planlægning fungerer nu som forventet.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 28. september 2026 kl. 15.08 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et problem, der kan være årsag til forsinkelser i leveringen af to-faktor autentificering (2FA) koder, når brugerne forsøger at logge ind. Dette spørgsmål er begrænset til brugerlogin proces. Engineering undersøger aktivt. Vi vil levere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

2. 28. september 2026 kl. 17.00 UTCresolved

   Spørgsmålet, der forårsager forsinkelser i leveringen af to-faktor autentificering (2FA) koder under bruger login er blevet løst. Brugerne bør nu modtage 2FA-koder som forventet.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 9. september 2026 kl. 15.40 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et spørgsmål, der kan forårsage forsinkelser i Dashboard på tværs af alle zoner. Vi vil levere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

2. 9. september 2026 kl. 15.57 UTCidentified

   Dashboard ydeevne er i færd med at komme sig på tværs af alle zoner, men kan stadig være langsommere end forventet for nogle kunder. Vi undersøger også et problem, der påvirker login via SSO. Vores ingeniørhold arbejder aktivt på at genoprette normal funktionalitet. Vi vil levere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

3. 9. september 2026 kl. 16.12 UTCresolved

   Dashboard ydeevne er vendt tilbage til normal på tværs af alle zoner, og problemet påvirker login via SSO er blevet løst. Alle tjenester fungerer som forventet.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 14. august 2026 kl. 20.58 UTCresolved

   Earlier today, some users in certain geographic regions, primarily on the West Coast, may have experienced slowness while accessing the Phreesia platform and completing intake forms. Our investigation indicates this was related to regional ISP/network routing degradation and was not a widespread Phreesia platform issue. Phreesia systems and infrastructure remained operating normally. We are no longer receiving reports of slowness, and performance has remained stable.

1. 14. august 2026 kl. 14.53 UTCinvestigating

   We are investigating elevated transaction failures affecting eligibility requests routed through our Eligibility API. Some affected API requests may time out or return errors, preventing eligibility responses from being returned successfully for external vendors leveraging this service. Eligibility & Benefits results accessed through the Phreesia Dashboard are not impacted. Our teams are actively investigating and monitoring the impact. We will provide an update as more information becomes available.

2. 16. august 2026 kl. 17.28 UTCresolved

   One of our vendors identified and implemented a fix on Friday afternoon August 14th. We are seeing a return to normal functionality through the Eligibility API.

1. 7. august 2026 kl. 13.14 UTCinvestigating

   We are currently investigating an issue in Zone 1 and Zone 2, which may be causing delays when exporting information from Phreesia to EMR/PM systems. We will provide updates as more information becomes available.

2. 7. august 2026 kl. 14.38 UTCresolved

   The issue causing delays when exporting information from Phreesia to EMR/PM systems in Zone 1 and Zone 2 has been resolved. Exports are processing as expected.

1. 23. juli 2026 kl. 15.57 UTCinvestigating

   Undersøgelse - Vi er klar over et problem, der berører Apriva, og som forhindrer, at betalingstransaktioner behandles. Aprima har erkendt problemet og er aktivt undersøger og arbejder på at genoprette tjenesten. Vi vil give yderligere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

2. 23. juli 2026 kl. 16.58 UTCinvestigating

   Opdatering - Apriva har rådet til, at Microsoft Azure er i øjeblikket oplever flere problemer, som påvirker deres platform, hvilket resulterer i betaling behandling problemer, vi observerer gennem gateway. Aprima og deres tjenesteudbydere arbejder aktivt på at genoprette tjenesten så hurtigt som muligt. Vi fortsætter med at overvåge situationen nøje og vil give yderligere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

3. 23. juli 2026 kl. 18.41 UTCmonitoring

   Aprima har implementeret en rettelse for betalingsbehandling problem og rapporterer positiv inddrivelse på tværs af berørte systemer. Vi overvåger nøje situationen for at bekræfte, at betalingstjenesterne forbliver stabile. Vi vil fortsætte med at levere opdateringer, indtil problemet er løst fuldt ud.

4. 23. juli 2026 kl. 18.57 UTCmonitoring

   Vi ser betalingstransaktioner behandling med succes efter fix gennemført af Apriva. Vi vil fortsat nøje overvåge betalingsbehandlingen for at sikre, at tjenesterne forbliver stabile, før denne hændelse markeres som løst. Vi vil levere yderligere opdateringer efter behov.

5. 23. juli 2026 kl. 19.05 UTCresolved

   Spørgsmålet om betalingsbehandling af Apriva er blevet løst. Betalingstransaktioner behandles med succes, og tjenesterne fungerer normalt. Vi sætter pris på Deres tålmodighed, mens dette spørgsmål blev behandlet.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 8. juli 2026 kl. 12.56 UTCinvestigating

   Vi har opdaget et problem, hvor brugere i Zone 3 kan opleve forsinkede belastningstider eller støde fejl, når adgang til udnævnelser Hub. Vores ingeniørhold undersøger aktivt problemet og arbejder på at genoprette normal ydeevne. Vi vil levere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

2. 8. juli 2026 kl. 13.09 UTCinvestigating

   Vores undersøgelse viser, at ud over forsinkede belastningstider og fejl, når adgang til udnævnelser Hub, kan PhreesiaPads også undlade at indlæse interviews for brugere i Zone 3. Vores Engineering team fortsætter med at undersøge problemet og arbejder på at genoprette normal funktionalitet. Vi vil levere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

3. 8. juli 2026 kl. 14.37 UTCinvestigating

   Vi fortsætter med at undersøge dette spørgsmål.

4. 8. juli 2026 kl. 15.10 UTCresolved

   Problemet påvirker performance for Phreesia Dashboard, Udnævnelser Hub, og PhreesiaPads i Zone 3 er blevet løst. Brugerne bør ikke længere opleve forsinkede belastningstider, fejl eller problemer med PhreesiaPads loading interviews. Vi undskylder for eventuelle ulemper dette problem kan have forårsaget og værdsætter din tålmodighed, mens vores Engineering team arbejdede for at genoprette normal præstation.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 7. juli 2026 kl. 13.14 UTCinvestigating

   We are currently investigating an issue affecting the Zone 5 Dashboard that is sporadically preventing appointments from being created as expected. While the issue is primarily limited to future-date appointments, we are continuing to assess the full scope of impact. Our Engineering team is working to restore normal functionality as quickly as possible. We will provide updates as more information becomes available.

2. 7. juli 2026 kl. 18.46 UTCresolved

   The issue affecting appointment creation in the Zone 5 Dashboard has been resolved. Shortly after the issue was identified earlier this morning, our Engineering team restored normal functionality. We also reprocessed all appointments that were not initially created to ensure accurate and up-to-date appointment lists in the Dashboard. We apologize for any inconvenience and appreciate your patience.

1. 23. juni 2026 kl. 16.04 UTCinvestigating

   We are currently investigating connectivity issues affecting ConnectOnCall/VoiceAI for a subset of practices using Athena. Patient search and matching capabilities may be impacted during this time. We are actively working to resolve this issue and will provide updates as they become available.

2. 23. juni 2026 kl. 20.54 UTCmonitoring

   Our engineering team was able to identify and resolve the issue affecting ConnectOnCall/VoiceAI for a subset of practices using Athena. Patient search and matching capabilities are currently operating as expected. We are continuing to monitor and will confirm full resolution shortly.

3. 24. juni 2026 kl. 12.36 UTCresolved

   ConnectOnCall/VoiceAI patient search and matching functionality performance issues have been fully resolved. We apologize for any inconvenience and thank you for your patience.

1. 22. juni 2026 kl. 14.51 UTCinvestigating

   We are currently investigating an issue with the VoiceAI dashboard that may be causing some users to experience performance issues when launching or using the service. Engineering is actively investigating, and we will provide updates as more information becomes available.

2. 23. juni 2026 kl. 13.28 UTCmonitoring

   VoiceAI Dashboard logins and performance have returned to normal following investigation and remediation by our engineering team. We are continuing to monitor and will confirm full resolution shortly.

3. 23. juni 2026 kl. 15.05 UTCresolved

   VoiceAI Dashboard login and performance issues have been fully resolved. We apologize for any inconvenience and thank you for your patience.

1. 19. juni 2026 kl. 17.15 UTCinvestigating

   We are currently investigating an issue with VoiceAI where calls may be disconnected when being transferred to staff. Engineering is actively investigating. We will provide updates as more information becomes available.

2. 19. juni 2026 kl. 19.52 UTCresolved

   The VoiceAI issue has been resolved and calls are now transferring to staff as expected.

1. 19. juni 2026 kl. 14.58 UTCinvestigating

   We are currently investigating an issue with VoiceAI where calls may be disconnected when being transferred to staff. Engineering is actively investigating. We will provide updates as more information becomes available.

2. 19. juni 2026 kl. 15.17 UTCresolved

   The VoiceAI issue has been resolved and calls are now transferring to staff as expected.

1. 17. juni 2026 kl. 15.00 UTCinvestigating

   We are currently investigating an issue that may be causing some users to experience difficulty logging into Dashboard and/or navigating within Dashboard. Engineering is actively investigating. We will provide updates as more information becomes available.

2. 17. juni 2026 kl. 15.36 UTCmonitoring

   We are no longer seeing issues with navigation in the Phreesia Dashboard. At this time, we are monitoring some performance issues related to SSO login. We will provide updates as more information becomes available.

3. 17. juni 2026 kl. 16.02 UTCresolved

   Performance across the Phreesia Dashboard and SSO login has returned to normal and all systems are operational.

1. 18. juni 2026 kl. 13.56 UTCresolved

   We identified an issue where calls made using our VoiceAI product were sporadically not connecting. This may have impacted some VoiceAI call attempts during the affected window. The issue has been resolved, and VoiceAI calls are now connecting as expected. We apologize for any inconvenience this may have caused. Affected timeframe: 9:00 AM - 10:10 AM Eastern Time

1. 10. juni 2026 kl. 20.18 UTCinvestigating

   We are aware of reports from some users experiencing slowness while navigating the Phreesia dashboard and completing intake forms. Our investigation indicates this is related to regional ISP/network routing degradation and is not a widespread platform issue. The issue is limited to users in certain geographic regions, primarily on the West Coast. Phreesia systems and infrastructure are operating normally. We are monitoring network conditions and tracking affected routes. We will provide an update as additional information becomes available.

2. 10. juni 2026 kl. 23.37 UTCinvestigating

   We are continuing to investigate reports from some users experiencing slowness while navigating the Phreesia dashboard and completing intake forms. At this time, monitoring indicates error rates have decreased from earlier elevated levels. Some users may also be seeing improved performance, and reports of issues have slowed. Current information continues to indicate the issue is related to regional ISP/network routing degradation impacting a limited number of clients on the West Coast and is not a widespread Phreesia platform issue. Phreesia systems and infrastructure continue to operate normally. We will continue to monitor network conditions, internal error trends, and user reports through the morning as normal traffic volumes return to validate that performance remains stable. We will provide another update as additional information becomes available.

3. 11. juni 2026 kl. 13.32 UTCmonitoring

   We continue to monitor reports from some users experiencing slowness while navigating the Phreesia Dashboard and completing intake forms. Network conditions that may have been contributing to the issue improved overnight, and monitoring indicates performance has remained stable. We also received information indicating that a major regional internet connectivity issue impacted parts of the West Coast during the same timeframe, which aligns with the limited client impact observed. Phreesia systems and infrastructure continued to operate normally, and this does not appear to have been a widespread Phreesia platform issue.

4. 11. juni 2026 kl. 23.11 UTCresolved

   We are no longer receiving reports of slowness while navigating the Phreesia Dashboard or completing intake forms. Performance has remained stable, and Phreesia systems and infrastructure continue to operate normally.

1. 4. juni 2026 kl. 12.07 UTCinvestigating

   We are currently investigating an issue affecting the Zone 3 Dashboard. This issue may be causing issues with the completion of some actions in the Dashboard. Engineering is actively investigating. We will provide updates as more information becomes available.

2. 4. juni 2026 kl. 12.18 UTCmonitoring

   The issue affecting the Zone 3 Dashboard has been resolved, and the Dashboard is now displaying as expected for users in Zone 3. Engineering will continue to monitor and provide additional updates if needed.

3. 4. juni 2026 kl. 13.30 UTCresolved

   This incident has been resolved.

1. 7. maj 2026 kl. 13.15 UTCinvestigating

   We are currently investigating an issue that is causing insurance and copays to not be tied to new visits on the Dashboard. Our Engineering team is actively investigating, and we will provide updates as more information becomes available.

2. 7. maj 2026 kl. 14.30 UTCidentified

   The issue has been identified, and our team is making progress towards a full recovery. We’re working through a backlog of messages and appreciate your patience.

3. 7. maj 2026 kl. 18.23 UTCresolved

   The insurance and copay issue affecting new visits on the Dashboard has been resolved and information is now displaying as expected.