Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Phreesia 中断历史

    67 Phreesia incidents · 2024年11月 — official updates, affected components, duration and resolution details.

    返回当前状态

    2FA 用户登录延迟

    开始时间 2026年10月22日 UTC 13:23 · 42m

    Issues轻微事件
    受影响的组件
    Phreesia DashboardPhreesia DashboardPhreesia DashboardPhreesia DashboardPhreesia DashboardPhreesia Dashboard
    1. 2026年10月22日 UTC 13:23investigating

      我们目前正在调查一个可能在用户试图登录时造成两个要素认证码(2FA)交付被延迟的问题. 这个问题仅限于用户登录过程. 工程正积极调查. 一旦获得更多信息,我们将提供最新资料.

    2. 2026年10月22日 UTC 14:05resolved

      在用户登录期间造成延迟交付双因子认证(2FA)代码的问题已经解决. 用户现在应该像预期的那样得到2FA代码.

    自动翻译自官方事件更新。

    装入分析的问题

    开始时间 2026年10月14日 UTC 14:40 · 3h 9m

    Issues轻微事件
    受影响的组件
    Phreesia DashboardPhreesia DashboardPhreesia DashboardPhreesia DashboardPhreesia DashboardPhreesia Dashboard
    1. 2026年10月14日 UTC 14:40investigating

      我们目前正在调查一个可能导致某些报告没有如预期的那样显示的问题。 我们的工程组正在积极调查,并与我们的第三方伙伴密切合作来解决这个问题。 一旦获得更多信息,我们将提供最新资料.

    2. 2026年10月14日 UTC 14:48monitoring

      报告目前正在我们第三方伙伴的缓解努力后成功地上载。 我们的工程小组正在继续监测情况,以确保报告功能恢复正常。 一旦获得更多信息,我们将提供更多最新情况.

    3. 2026年10月14日 UTC 17:49resolved

      在我们的第三方伙伴作出缓解努力之后,影响报告提供的问题已经得到解决.

    自动翻译自官方事件更新。

    第1和第2区自行安排的问题

    开始时间 2026年10月14日 UTC 13:47 · 27m

    Issues轻微事件
    受影响的组件
    Self-SchedulingSelf-Scheduling
    1. 2026年10月14日 UTC 13:47investigating

      我们目前正在调查一个影响第一区和第二区的自我安排的问题。 患者在试图安排预约时可能遇到核实错误. 工程正积极调查.

    2. 2026年10月14日 UTC 14:14resolved

      造成"一一"和"二"自定计划核查错误的问题已经解决. 自定计划现在如所预期的那样运作.

    自动翻译自官方事件更新。

    2FA 用户登录延迟

    开始时间 2026年9月28日 UTC 15:08 · 1h 52m

    Issues轻微事件
    受影响的组件
    Phreesia DashboardPhreesia DashboardPhreesia DashboardPhreesia DashboardPhreesia Dashboard
    1. 2026年9月28日 UTC 15:08investigating

      我们目前正在调查一个可能在用户试图登录时造成两个要素认证码(2FA)交付被延迟的问题. 这个问题仅限于用户登录过程. 工程正积极调查. 一旦获得更多信息,我们将提供最新资料.

    2. 2026年9月28日 UTC 17:00resolved

      在用户登录期间造成延迟交付双因子认证(2FA)代码的问题已经解决. 用户现在应该像预期的那样得到2FA代码.

    自动翻译自官方事件更新。

    板板延迟 - 所有区域

    开始时间 2026年9月9日 UTC 15:40 · 32m

    Issues轻微事件
    受影响的组件
    Phreesia DashboardPhreesia DashboardSingle Sign-On to Phreesia DashboardSingle Sign-On to Phreesia DashboardPhreesia DashboardPhreesia DashboardSingle Sign-On to Phreesia DashboardPhreesia DashboardSingle Sign-On to Phreesia DashboardPhreesia DashboardSingle Sign-On to Phreesia DashboardSingle Sign-On to Phreesia Dashboard
    1. 2026年9月9日 UTC 15:40investigating

      我们目前正在调查一个可能在所有地区造成达什板延误的问题。 一旦获得更多信息,我们将提供最新资料.

    2. 2026年9月9日 UTC 15:57identified

      Dashboard的性能正在各区恢复,但对于一些客户来说可能仍然比预期的要慢. 我们还正在调查一个影响通过特别安全局登录的问题。 我们的工程团队正积极致力于恢复正常功能. 一旦获得更多信息,我们将提供最新资料.

    3. 2026年9月9日 UTC 16:12resolved

      Dashboard 性能在所有地区都恢复正常,影响通过SSO登录的问题已经解决. 所有服务都按预期运作.

    自动翻译自官方事件更新。

    Dashboard Performance Issues - Regional Network Disruption

    开始时间 2026年8月14日 UTC 18:00 · 0m

    Pending
    1. 2026年8月14日 UTC 20:58resolved

      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.

    Elevated Eligibility API Transaction Failures

    开始时间 2026年8月14日 UTC 14:53 · 2d 2h

    Issues轻微事件
    受影响的组件
    Eligibility and Benefits API
    1. 2026年8月14日 UTC 14:53investigating

      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. 2026年8月16日 UTC 17:28resolved

      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.

    Export Delays on Zone 1 / Zone 2

    开始时间 2026年8月7日 UTC 13:14 · 1h 25m

    Issues轻微事件
    受影响的组件
    Export FunctionsExport Functions
    1. 2026年8月7日 UTC 13:14investigating

      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. 2026年8月7日 UTC 14:38resolved

      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.

    Apriva 支付网关问题

    开始时间 2026年7月23日 UTC 15:57 · 3h 8m

    Outage严重事件
    受影响的组件
    Payment Services - GatewayPayment Services - GatewayPayment Services - GatewayPayment Services - GatewayPayment Services - GatewayPayment Services - Gateway
    1. 2026年7月23日 UTC 15:57investigating

      调查 - 我们知道影响阿普里瓦的一个问题正在阻止支付交易的处理。 阿普里瓦承认这一问题,并正在积极调查和努力恢复服务。 一旦获得更多信息,我们将提供更多最新情况.

    2. 2026年7月23日 UTC 16:58investigating

      最新消息 — — Apriva指出微软Azure目前正面临影响其平台的多重问题, 阿普里瓦及其服务提供商正积极致力于尽快恢复服务. 我们正在继续密切监测局势,并将在获得更多信息后提供更多最新情况.

    3. 2026年7月23日 UTC 18:41monitoring

      Apriva已经解决了付款处理问题,并正在报告受影响系统中的积极恢复情况。 我们正在密切监测局势,以确认付款处理服务保持稳定。 我们将继续提供最新情况,直至这一问题得到全面解决.

    4. 2026年7月23日 UTC 18:57monitoring

      我们正看到,在阿普里瓦执行的固定措施之后,支付交易处理顺利进行。 我们将继续密切监测付款处理情况,以确保服务保持稳定,然后将这一事件定为已解决事件。 我们将视需要提供补充资料.

    5. 2026年7月23日 UTC 19:05resolved

      影响到Apriva的付款处理问题已经解决。 支付交易处理成功,服务正常运行. 我们赞赏你在处理这一问题时的耐心.

    自动翻译自官方事件更新。

    第3区任命中心/博士学位问题

    开始时间 2026年7月8日 UTC 12:56 · 2h 14m

    Outage重大事件
    受影响的组件
    Phreesia DashboardPhreesiaPads
    1. 2026年7月8日 UTC 12:56investigating

      我们发现一个问题,即第3区的用户在访问任用中心时可能遇到延迟装载时间或出错。 我们的工程团队正在积极调查这个问题并努力恢复正常的性能. 一旦获得更多信息,我们将提供最新资料.

    2. 2026年7月8日 UTC 13:09investigating

      我们的调查显示,除了在访问预约枢纽时延迟载货时间和出错外,PhreesiaPads还可能无法为3区用户装入采访. 我们的工程组继续调查这一问题,并正在努力恢复正常功能。 一旦获得更多信息,我们将提供最新资料.

    3. 2026年7月8日 UTC 14:37investigating

      我们正在继续调查这一问题.

    4. 2026年7月8日 UTC 15:10resolved

      影响Phreesia Dashboard、预约枢纽和PhreesiaPads在第3区业绩的问题已经解决。 用户不应再经历延迟加载时间,出错,或与PhreesiaPads加载访谈发生问题. 我们为任何不便道歉 这个问题可能已经 和欣赏你的耐心 当我们的工程团队 努力恢复正常的性能.

    自动翻译自官方事件更新。

    Appointment Import Issues on Zone 5

    开始时间 2026年7月7日 UTC 13:14 · 5h 32m

    Issues轻微事件
    受影响的组件
    Import Functions
    1. 2026年7月7日 UTC 13:14investigating

      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. 2026年7月7日 UTC 18:46resolved

      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.

    PatientSearch for ConnectOnCall — Athena

    开始时间 2026年6月23日 UTC 16:04 · 20h 32m

    Issues轻微事件
    受影响的组件
    Import FunctionsExport Functions
    1. 2026年6月23日 UTC 16:04investigating

      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. 2026年6月23日 UTC 20:54monitoring

      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. 2026年6月24日 UTC 12:36resolved

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

    VoiceAI Dashboard Issues

    开始时间 2026年6月22日 UTC 14:51 · 1d 0h

    Issues轻微事件
    受影响的组件
    VoiceAI Dashboard
    1. 2026年6月22日 UTC 14:51investigating

      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. 2026年6月23日 UTC 13:28monitoring

      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. 2026年6月23日 UTC 15:05resolved

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

    VoiceAI Disconnection Issues

    开始时间 2026年6月19日 UTC 17:15 · 2h 38m

    Issues轻微事件
    受影响的组件
    VoiceAI Dashboard
    1. 2026年6月19日 UTC 17:15investigating

      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. 2026年6月19日 UTC 19:52resolved

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

    VoiceAI Disconnection Issues

    开始时间 2026年6月19日 UTC 14:58 · 20m

    Issues轻微事件
    受影响的组件
    Patient Phone Communication
    1. 2026年6月19日 UTC 14:58investigating

      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. 2026年6月19日 UTC 15:17resolved

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

    Phreesia Dashboard Issues

    开始时间 2026年6月17日 UTC 15:00 · 1h 3m

    Outage严重事件
    受影响的组件
    Phreesia DashboardPhreesia DashboardSingle Sign-On to Phreesia DashboardSingle Sign-On to Phreesia DashboardPhreesia DashboardPhreesia DashboardSingle Sign-On to Phreesia DashboardPhreesia DashboardSingle Sign-On to Phreesia DashboardPhreesia DashboardSingle Sign-On to Phreesia DashboardSingle Sign-On to Phreesia Dashboard
    1. 2026年6月17日 UTC 15:00investigating

      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. 2026年6月17日 UTC 15:36monitoring

      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. 2026年6月17日 UTC 16:02resolved

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

    VoiceAI Calls Not Connecting

    开始时间 2026年6月17日 UTC 13:00 · 0m

    Pending
    1. 2026年6月18日 UTC 13:56resolved

      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

    Dashboard Performance Issues - Regional Network Disruption

    开始时间 2026年6月10日 UTC 20:18 · 1d 2h

    Issues轻微事件
    受影响的组件
    PhreesiaPadsPhreesiaPadsPhreesia DashboardPhreesia DashboardPhreesia DashboardPhreesiaPadsPhreesiaPadsPhreesiaPadsPhreesia DashboardPhreesia DashboardPhreesia DashboardPhreesiaPads
    1. 2026年6月10日 UTC 20:18investigating

      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. 2026年6月10日 UTC 23:37investigating

      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. 2026年6月11日 UTC 13:32monitoring

      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. 2026年6月11日 UTC 23:11resolved

      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.

    Zone 3 Dashboard Issues

    开始时间 2026年6月4日 UTC 12:07 · 1h 23m

    Pending
    受影响的组件
    Phreesia Dashboard
    1. 2026年6月4日 UTC 12:07investigating

      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. 2026年6月4日 UTC 12:18monitoring

      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. 2026年6月4日 UTC 13:30resolved

      This incident has been resolved.

    Zone 5 Insurance and Copay Issues

    开始时间 2026年5月7日 UTC 13:15 · 5h 8m

    Issues轻微事件
    受影响的组件
    Eligibility and Benefits Verification
    1. 2026年5月7日 UTC 13:15investigating

      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. 2026年5月7日 UTC 14:30identified

      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. 2026年5月7日 UTC 18:23resolved

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