FloRecruit Outage History
FloRecruit is up right nowPingoru has recorded 14 incidents for FloRecruit: 2 in the last 12 months and 1 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 | 0 | 0 of 744 (0%) |
| August 2026 | 1 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 512 (0%) |
Incidents, newest first
Notice August 4, 2026 Users are not able to login 12m Flo University, Flo Employer
Started Aug 04, 2026, 03:10 PM UTC· resolved Aug 04, 2026, 03:23 PM UTC
- investigating Aug 04, 2026, 03:10 PM UTC
We are currently working on an issue where users are experiencing problems logging in and performing actions inside our applications. Engineers are working on this now and we will be providing updates every 15 minutes.
- investigating Aug 04, 2026, 03:22 PM UTC
All systems should now be operational
- investigating Aug 04, 2026, 03:23 PM UTC
We are continuing to investigate this issue.
- resolved Aug 04, 2026, 03:23 PM UTC
This incident has been resolved.
- postmortem Aug 31, 2026, 04:34 PM UTC
**Leadup & Detection** * At 9:50 AM on 8/4/26, the daily deployment workflow failed because of a timed out database migration. At 10 AM, while being investigated by the On Call engineer, customers started reporting that they were unable to access the platform—all pages seemed to be affected. **Cause** * A long-running process held a lock on a critical database table. A migration attempted to apply a foreign key constraint to that table, and because of the held lock, the operation was unable to be completed—it retried until it timed out, causing excess load on the RDS writer instance of the primary MySQL database. **Response** * Threads were created in high visibility slack channels to raise awareness, and the Engineering team started a call to identify the cause and a path forward. VP of Engineering updated the status page to indicate a systemwide issue at 10:10 AM. **Recovery** * An engineer rebooted the production database writer instance at 10:12 AM, taking about ~5 minutes, which resolved the lock issue and allowed users to resume access the platform around 10:18 AM. The status page was updated at 10:23 AM. **Full Timeline** * 9:50 AM - Flyway migration fails, blocking daily production deployment * 9:50 AM - Customer Success team posts in Slack asking if the site is down—refreshing a logged-in session produced an error page * 10:00 AM - CEO posts to internal high-visibility Slack channel * 10:04 AM - Engineering huddle starts in Slack * 10:10 AM - VP of Engineering updates the status page * 10:12 AM - Engineering team initiates a reboot of the writer instance * 10:17 AM - Reboot completes, platform is once again accessible * 10:23 AM - After some cursory verification by engineering to ensure the application is live again, VP of Engineering updates the status page
Minor January 22, 2026 Microsoft Outage 16h 47m
Started Jan 22, 2026, 10:15 PM UTC· resolved Jan 23, 2026, 03:02 PM UTC
- investigating Jan 22, 2026, 10:15 PM UTC
We are currently monitoring the Microsoft outage that is affecting users’ ability to receive emails. As a result, some users who depend on Microsoft-specific email may experience delays in receiving Flo Recruit emails, which could impact notifications and access to Flo Forward.
- investigating Jan 22, 2026, 10:15 PM UTC
We are continuing to investigate this issue.
- resolved Jan 23, 2026, 03:02 PM UTC
Microsoft has reported all systems are operational
Critical October 20, 2025 Issues with logging into the Flo's platform due to AWS outage 8h 11m Flo University, Flo Employer, E-mail Service, Video Hosting
Started Oct 20, 2025, 01:35 PM UTC· resolved Oct 20, 2025, 09:47 PM UTC
- identified Oct 20, 2025, 01:35 PM UTC
We’re currently investigating issues affecting customer logins.
- identified Oct 20, 2025, 01:45 PM UTC
We are still seeing issue with the third party vendor (AWS). Customers may still experience delays or errors when trying to log-in. We will provide another update in an hour or as soon as more information becomes available.
- identified Oct 20, 2025, 02:23 PM UTC
We are still seeing issue with the third party vendor (AWS - link below). Customers may still experience delays or errors when trying to log in. We will provide another update in an hour or as soon as more information becomes available. https://health.aws.amazon.com/health/status
- monitoring Oct 20, 2025, 03:42 PM UTC
We are still seeing issue with the third party vendor (AWS - link below). Customers may still experience delays or errors when trying to log in. We will provide another update in an hour or as soon as more information becomes available. https://health.aws.amazon.com/health/status
- monitoring Oct 20, 2025, 04:53 PM UTC
AWS is still experiencing issues, however we have verified that all video chat interview experiences are working as normal. Admins can still not login to the platform due to the AWS outage - https://health.aws.amazon.com/health/status We will provide another update in an hour or as soon as more information becomes available.
- monitoring Oct 20, 2025, 06:22 PM UTC
AWS is still experiencing issues, however we have verified that all video chat interview experiences are working as normal. Admins can still not login to the platform due to the AWS outage - https://health.aws.amazon.com/health/status We will provide another update in an hour or as soon as more information becomes available.
- monitoring Oct 20, 2025, 07:00 PM UTC
At this time, login pages are active again. We are continuing monitoring at this time. Please see our status page below for live updates.
- resolved Oct 20, 2025, 09:47 PM UTC
This incident has been resolved.