Looking for an update now? Check the current status, or follow Loop for future changes.
100%of 37 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
100%
30
0
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 2Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
September 2026
"Policy verification not available" appearing throughout the app
We expect invoices from the last month to have policy verification details available in the app by tomorrow morning. We'll provide updates on the remaining invoices afterwards.
monitoring
We have a method in place to restore policy verification for invoices received before Saturday, September 26, and expect to begin running it shortly. This first pass covers invoices received in the last month. We will share another update once it completes, including next steps for older invoices.
identified
We are aware of an issue causing invoices received before Saturday to read "Policy verification not available." No data was lost and we are working on restoring historical data.
Legacy Incident Archive
3 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
July 2026
Data processing delays
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are experiencing bursts of instability related to the issues from last week. During this time, document ingestion and processing may be delayed — this can affect policy evaluations and other automated workflows. No data has been lost. We're actively working through the backlog and will post updates as it clears.
monitoring
All systems have been stable since Friday afternoon. The backlog has been cleared and new data is being processed according to the usual timeline. We are continuing to monitor the fixes we put in place.
monitoring
During recovery, we observed another set of system-wide delays around midnight CDT. We have implemented a mitigation this morning and our systems are continuing to recover. We are working on processing all data we received during this time, and no data was lost.
monitoring
We've identified and resolved the issue causing delays and are working through the backlog. We are working on processing all affected data. No data was lost.
investigating
Delays will primarily be visible in cost allocation, business policies, and search results. We are working to get this resolved.
investigating
We are investigating delayed in our asynchronous data processing
June 2026
Web app is intermittently down
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The issue causing server crashes has been identified and resolved. The app is now fully operational. We will continue to monitor.
investigating
The Loop app is intermittently down due to a spike in resource utilization. We are investigating the issue.
April 2026
Delays in artifact processing
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The majority of the backlog has been processed and artifact processing has returned to normal throughput. A small number of long-tail artifacts remain affected, and we are continuing to work through them. We will post another update once all remaining artifacts have been processed.
monitoring
We are continuing to work through the backlog from earlier today's delayed artifact processing. The fix remains in place and the system is processing normally. Based on current throughput, we estimate it will take approximately 3 more hours to fully catch up. We will post another update when the backlog has cleared.
monitoring
We identified an issue causing delayed processing of artifacts. A fix has been deployed and processing has resumed. We are now working through the backlog and currently estimate it will take approximately 5 hours to fully catch up, though this timeline may shift as we monitor progress. We will post another update once the backlog has cleared.
identified
We have identified issues with the ingestion of artifacts from all sources, causing a delay in all downstream processing. Engineers are working on a fix. No data loss is expected.
