Is FloRecruit down?
Last checked 15m agoNo incidents right now.
FloRecruit is operational right now. Last checked 15m ago; the most recent incident resolved 41d ago.
Real-time FloRecruit status, recent outages, and incident history — pulled directly from FloRecruit's official status page at https://florecruit.statuspage.io every 5 minutes. Pingoru tracks 4 FloRecruit services and has captured 1 incident in the last 90 days (100.00% uptime). Get email, Slack, Discord, or webhook alerts the moment FloRecruit reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Flo UniversityFlo Employer
Timeline · 5 updates
- 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
Latest: **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 eng…
-
- Users are not able to login ResolvedStarted Aug 04, 2026, 03:10 PM UTC · Resolved Aug 04, 2026, 03:23 PM UTC · 12m