UpGuard Outage History
UpGuard is up right nowPingoru has recorded 18 incidents for UpGuard: 5 in the last 12 months and 3 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 1 | 7 of 744 (1%) |
| August 2026 | 2 | 0 of 744 (0%) |
| September 2026 | 1 | 1 of 720 (0%) |
| October 2026 | 0 | 0 of 509 (0%) |
Incidents, newest first
Critical September 23, 2026 A database outage is causing the platform to be unavailable 46m Web App, External API, Authentication
Started Sep 23, 2026, 01:55 AM UTC· resolved Sep 23, 2026, 02:41 AM UTC
- investigating Sep 23, 2026, 01:55 AM UTC
We are currently investigating.
- identified Sep 23, 2026, 02:00 AM UTC
We have restarted the database. We are continuing to investigate.
- monitoring Sep 23, 2026, 02:05 AM UTC
The database restart has successfully restored the platform. We are monitoring, and checking for a root cause.
- resolved Sep 23, 2026, 02:41 AM UTC
This incident is now resolved. The database ran out of connections due to a lock being held as part of the fortnightly release. Changes to the release process are being implemented to remove the risk of this happening again.
Minor August 10, 2026 An Issue has been identified regarding a disruption to login services. –
Started Aug 10, 2026, 05:00 AM UTC· resolved Aug 10, 2026, 05:00 AM UTC
- resolved Aug 10, 2026, 12:50 PM UTC
This incident has now been resolved
Notice July 8, 2026 Disruption to notification emails 7h 18m
Started Jul 08, 2026, 05:52 PM UTC· resolved Jul 09, 2026, 01:10 AM UTC
- investigating Jul 08, 2026, 05:52 PM UTC
We are currently investigating a delay/disruption in processing notification emails.
- identified Jul 08, 2026, 09:29 PM UTC
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.
- monitoring Jul 08, 2026, 09:52 PM UTC
New notification emails are now being delivered as expected. Previously delayed notifications are still being processed and may take some time to arrive.
- resolved Jul 09, 2026, 01:10 AM UTC
The incident is now resolved. All delayed notifications have now been sent.
Critical March 6, 2026 We are experiencing an issue where the platform will be offline for a period of time. 22m Web App, External API, Authentication
Started Mar 06, 2026, 01:30 AM UTC· resolved Mar 06, 2026, 01:52 AM UTC
- investigating Mar 06, 2026, 01:30 AM UTC
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.
- resolved Mar 06, 2026, 01:52 AM UTC
Our engineers have identified the issue, and it's been fully resolved. The platform is fully functional.
Major September 5, 2025 An issue has been identified where questionnaires are unable to be sent. 19m Web App
Started Sep 05, 2025, 07:12 PM UTC· resolved Sep 05, 2025, 07:32 PM UTC
- investigating Sep 05, 2025, 07:12 PM UTC
We are currently investigating.
- investigating Sep 05, 2025, 07:30 PM UTC
We have identified a backlog in our async jobs queue and are working towards a fix.
- investigating Sep 05, 2025, 07:32 PM UTC
The issue has been resolved.
- resolved Sep 05, 2025, 07:32 PM UTC
This incident has been resolved.
Notice August 6, 2025 Some Identity Breach data delayed due to processing errors –
Started Aug 06, 2025, 07:00 AM UTC· resolved Aug 06, 2025, 07:00 AM UTC
- resolved Aug 07, 2025, 07:12 AM UTC
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.
Notice July 3, 2025 Cloudflare 'Always use HTTPS' behavior change causing 'SSL not available' risks to be raised. 1d 6h Web App
Started Jul 03, 2025, 01:15 AM UTC· resolved Jul 04, 2025, 08:13 AM UTC
- investigating Jul 03, 2025, 01:15 AM UTC
In Cloudflare, there is a setting in SSL->'Edge Certificates'->'Always use HTTPS' that is used to redirect from http to https for Cloudflare proxied domains. The behavior of this setting changed last week (approx June 26) for non-standard ports. This change causes a failure when browsing to the port, instead of a successful redirect and response. This has caused UpGuard's scanning engine to detect these as not using HTTPS, and therefore raises a risk 'SSL Not Available'. The non-standard ports HTTP ports used by Cloudflare are: 8080, 8880, 2052, 2082, 2086, 2095. The default http port (80), has not changed behavior. Using upguard.in as an example, previously this setting would perform like this: http://upguard.in:8080 → redirect to https://upguard.in and now it behaves like this: http://upguard.in:8080 → redirect to https://upguard.in:8080 (and https fails on this http only port). Cloudflare support have not responded at this time, and we have found no documentation to support a change in behavior. Public risk waivers with an short expiry have been put in place against UpGuards domains, while we investigate.
- identified Jul 03, 2025, 01:18 AM UTC
We are currently developing and testing a change to UpGuard's scanning engine to ignore unused Cloudflare HTTP ports. This will cause the 'SSL Not Available' risks to be removed when the domains are rescanned next. The next update will be after this change has been implemented.
- monitoring Jul 03, 2025, 05:56 AM UTC
A change to UpGuard's scanning engine has been deployed. The additional 'SSL not found' risk detected on domains using Cloudflare proxy services, will be removed upon the next scan. All domains will be rescanned within 24 hours, and this issue will be resolved.
- resolved Jul 04, 2025, 08:13 AM UTC
All additional risks generated have now been removed. The score history graph may continue to show a dip for a period of a week. If needed, please use this incident as evidence of why the score dropped temporarily.
Minor June 18, 2025 Missing Notification and Integration events (20 minute gap) 21m
Started Jun 18, 2025, 02:09 AM UTC· resolved Jun 18, 2025, 02:30 AM UTC
- resolved Jun 18, 2025, 04:35 AM UTC
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.
- postmortem Jun 18, 2025, 04:36 AM UTC
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.
Critical December 5, 2024 System outage - cannot login 3h 18m Web App, Authentication
Started Dec 05, 2024, 10:03 AM UTC· resolved Dec 05, 2024, 01:21 PM UTC
- investigating Dec 05, 2024, 10:03 AM UTC
We are currently investigating an alert. Authentication is not accepting new logins.
- monitoring Dec 05, 2024, 10:11 AM UTC
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.
- resolved Dec 05, 2024, 01:21 PM UTC
This incident has been resolved.
Major November 18, 2024 Notifications are being processed slowly, and the current queue is 2 days long 4h 33m Web App, External API, Authentication
Started Nov 18, 2024, 02:29 AM UTC· resolved Nov 18, 2024, 07:02 AM UTC
- identified Nov 18, 2024, 02:29 AM UTC
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).
- identified Nov 18, 2024, 06:00 AM UTC
We are continuing to work on a fix for this issue.
- identified Nov 18, 2024, 06:01 AM UTC
Outage commencing now to increase CPU on database
- monitoring Nov 18, 2024, 06:16 AM UTC
Database update is complete. We are monitoring notification queue for performance.
- resolved Nov 18, 2024, 07:02 AM UTC
The notification queue is reducing, and will be recovered within 12 hours.