An Issue has been identified regarding a disruption to login services.
Timeline · 1 update
- resolved Aug 10, 2026, 12:50 PM UTC
This incident has now been resolved
UpGuard had 9 outages in the last 2 years totaling 46h 49m of downtime — averaging 0.4 incidents per month.
There were 9 UpGuard outages since November 18, 2024 totaling 46h 49m of downtime. Each is summarised below — incident details, duration, and resolution information.
This incident has now been resolved
We are currently investigating a delay/disruption in processing notification emails.
We’ve identified an issue with our email service provider that is delaying delivery of some notification emails. Our team is working with the provider to restore normal processing. In-app functionality is not affected, but some email notifications may be delayed until processing resumes. Our engineering team is also working towards an alternative solution.
New notification emails are now being delivered as expected. Previously delayed notifications are still being processed and may take some time to arrive.
The incident is now resolved. All delayed notifications have now been sent.
We are aware of an issue impacting certain features, including the trust page, questionnaires, and user role adjustments. Our engineers are investigating and working on a solution which requires a temporary shut down of the platform.
Our engineers have identified the issue, and it's been fully resolved. The platform is fully functional.
We are currently investigating.
We have identified a backlog in our async jobs queue and are working towards a fix.
The issue has been resolved.
This incident has been resolved.
Errors were generated when processing updates from one of our Identity Breach data providers. Data from this one provider was delayed since May 8th 2025. The data feed has been refreshed, and any delayed data has now been delivered.
Immediately after our release process today, the notification events that should have been generated between 12:09PM AEST and 12:30PM AEST were not generated. This was rectified immediately, and the incident itself is resolved, but this has left a 20 minute gap where notifications are missing. The UpGuard Engineering and Support teams are continuing to investigate, in an attempt to manually extract the notification information from audit and event logs. We estimate only very few customers were impacted, and only for a small number of notifications. In the next few days our team will be in touch with any impacted customer.
UpGuard have started a Post-Incident Review process, and have already planned changes to remove the risk of this incident reoccurring. This Postmortem will be updated with the outcome of the PIR.
We are currently investigating an alert. Authentication is not accepting new logins.
Our Authentication provider Auth0 by Okta wasn't calling our platform correctly. The issue has resolved itself for now, we are monitoring for root cause.
This incident has been resolved.
We have identified the issue, and need to upgrade the CPU on a database to recover. A platform outage to recover from this issue, is being planned for 5pm AEDT (6am UTC/London, 11:30am IST).
We are continuing to work on a fix for this issue.
Outage commencing now to increase CPU on database
Database update is complete. We are monitoring notification queue for performance.
The notification queue is reducing, and will be recovered within 12 hours.