FBS Outage History

Started Oct 21, 2026, 05:45 PM UTC· resolved Oct 22, 2026, 02:59 PM UTC

1. monitoring Oct 21, 2026, 05:45 PM UTC

   **Upcoming Temporary Change to Flexmls.com** We want to make you aware of a temporary change to the Flexmls.com website. **This change will not affect your ability to log in to or use Flexmls.** While we work with a software vendor to address a recently identified issue, we'll be temporarily taking portions of our public website offline. During this time, visitors to Flexmls.com will be automatically redirected to the Flexmls login page, rather than seeing the usual website content. The Flexmls Academy will also be temporarily unavailable during this time. However, our help and support resources at **help.flexmls.com** will remain fully accessible. We appreciate your patience and understanding while we work to restore these websites to their normal operation.

2. resolved Oct 22, 2026, 02:59 PM UTC

   Website Services Restored The necessary software updates have been applied, and our websites have been restored to normal operation. Flexmls.com and Flexmls Academy are once again available, with all website content and functionality restored. We appreciate your patience and understanding while we worked to resolve this issue.

Read the full incident report →

Started Oct 16, 2026, 05:48 PM UTC· resolved Oct 19, 2026, 02:06 PM UTC

1. investigating Oct 16, 2026, 05:48 PM UTC

   We are aware of a connectivity issue when trying to access Flexmls and are actively researching the problem.

2. monitoring Oct 16, 2026, 06:29 PM UTC

   Service availability has improved, and systems appear to be operating normally. We suspect the disruption may have been related to an upstream network provider, but the cause has not yet been confirmed. We are continuing to monitor for any further issues.

3. resolved Oct 19, 2026, 02:06 PM UTC

   Services have remained stable following Friday's disruption, and we have observed no further issues. We are closing this incident while continuing to investigate the underlying cause with our network service provider.

Read the full incident report →

Started Oct 12, 2026, 02:07 PM UTC· resolved Oct 12, 2026, 06:19 PM UTC

1. investigating Oct 12, 2026, 02:07 PM UTC

   We are currently investigating an issue causing some customers to encounter 503 errors when attempting to log in to Flexmls. Our team is actively working to identify the cause and restore normal functionality. We will provide updates as more information becomes available.

2. identified Oct 12, 2026, 02:13 PM UTC

   We have identified the source of the issue and implemented a workaround to restore normal login functionality. Customers who were experiencing 503 errors should now be seeing improvement. We will continue to monitor the system to ensure stability.

3. resolved Oct 12, 2026, 06:19 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 25, 2026, 01:07 AM UTC· resolved Aug 25, 2026, 04:04 PM UTC

1. investigating Aug 25, 2026, 01:07 AM UTC

   We are investigating a networking event that began around 8:00pm (US/Central). Flexmls users may experience slow or failed page delivery.

2. investigating Aug 25, 2026, 01:46 AM UTC

   We continue to investigate this event. Most Flexmls services are currently functioning normally. We are working to resolve remaining issues affecting photo delivery and photo uploads, including those provided through RETS services. We will provide additional updates as more information becomes available.

3. identified Aug 25, 2026, 03:14 AM UTC

   We continue to investigate issues affecting photo delivery and uploads. We have engaged our storage vendor and are actively working with them to resolve the remaining issues. Most Flexmls services remain functional at this time. We will provide additional updates as more information becomes available.

4. monitoring Aug 25, 2026, 07:05 AM UTC

   The issues affecting photo delivery and uploads have been resolved, and Flexmls services are operating normally. Data shares and photo imports may experience some delays as queued activity is processed and systems catch up. We appreciate your patience while we worked to resolve this issue.

5. resolved Aug 25, 2026, 04:04 PM UTC

   Systems have remained stable following the resolution of this incident. Data shares and photo imports have continued to process their queued activity, and we are closing this incident. Thank you for your patience while we worked to restore full service.

Read the full incident report →

Started Jun 02, 2026, 03:46 PM UTC· resolved Jun 02, 2026, 06:28 PM UTC

1. investigating Jun 02, 2026, 03:46 PM UTC

   We are currently investigating an issue related to DNS resolution that may prevent some users from accessing Flexmls services. Our team is actively working to identify the root cause and restore normal access as quickly as possible. Users may experience intermittent connectivity issues or be unable to reach Flexmls systems during this time. We will provide additional updates as more information becomes available.

2. monitoring Jun 02, 2026, 03:55 PM UTC

   Service Recovery in Progress We are seeing signs of recovery and access to Flexmls services appears to be returning to normal for most users. Our team continues to actively monitor the situation and verify service stability. Some users may still experience intermittent access issues as DNS changes continue to propagate. We will continue to provide updates and will post a final resolution once we have confirmed that service has been fully restored.

3. resolved Jun 02, 2026, 06:28 PM UTC

   We have not observed any recurrence since service recovery began. We will continue to monitor the environment as a precaution. Our investigation indicates the disruption was likely related to a routine DNS configuration change. While the configuration itself was validated, there appears to have been an issue during the distribution of the updated DNS information by our upstream DNS provider, which resulted in unexpected resolution failures for some users. We have opened a support case with the provider to better understand the circumstances surrounding this event and to identify any recommended safeguards or process improvements to help prevent similar issues in the future. We apologize for the disruption and appreciate your patience while we worked to restore service.

Read the full incident report →

Started Feb 17, 2026, 08:59 PM UTC· resolved Feb 17, 2026, 11:02 PM UTC

1. investigating Feb 17, 2026, 08:59 PM UTC

   We are currently investigating a slowdown impacting the Flexmls system. Users may experience slow page loads or intermittent page load failures. We are actively working to identify the cause and will provide updates as more information becomes available.

2. monitoring Feb 17, 2026, 09:09 PM UTC

   Traffic levels are returning to normal, and system performance is stabilizing. We are continuing to monitor the Flexmls system closely to ensure full recovery and will provide additional updates if needed.

3. resolved Feb 17, 2026, 11:02 PM UTC

   Monitoring has been completed, and system performance has remained stable. The earlier slowdown impacting the Flexmls system has been resolved.

Read the full incident report →

Started Jan 30, 2026, 08:14 PM UTC· resolved Feb 02, 2026, 07:09 PM UTC

1. identified Jan 30, 2026, 08:14 PM UTC

   Sharing listings via text message is being blocked by Twilio, the service we use to send SMS messages. We're working on a fix but do not have an exact timeline. The rest of the system remains fully functional.

2. identified Jan 30, 2026, 08:58 PM UTC

   Our SMS provider is working on the problem.

3. resolved Feb 02, 2026, 07:09 PM UTC

   Our provider has resolved the issue. Sharing listings via SMS text is working again.

Read the full incident report →

Started Jul 14, 2025, 08:57 PM UTC· resolved Jul 15, 2025, 09:05 PM UTC

1. investigating Jul 14, 2025, 08:57 PM UTC

   We are currently investigating an issue affecting a subset of users interacting with search results on mobile platforms. This includes both native mobile apps and mobile-delivered links. Affected users may experience degraded performance or inconsistent behavior when engaging with search features on these platforms. Our engineering team is actively working to identify the root cause and implement a fix. We will continue to provide updates as we learn more. Thank you for your patience.

2. monitoring Jul 14, 2025, 10:15 PM UTC

   We’ve identified and resolved the issue that was causing degraded performance for users interacting with search results on mobile platforms, including mobile apps and mobile-delivered links. The issue has been mitigated and normal service has been restored. We are continuing to monitor closely to ensure stability. Thank you for your patience while we worked to resolve this.

3. resolved Jul 15, 2025, 09:05 PM UTC

   Following the resolution of the issue impacting search results on mobile apps and mobile-delivered links, we kept the incident open overnight to monitor for any recurrence. We’re happy to report that no further problems have been observed, and the system has remained stable throughout the monitoring period. The incident is now fully resolved and the status page post has been closed. Thank you for your patience and understanding.

Read the full incident report →

Started Jul 10, 2025, 03:44 PM UTC· resolved Jul 10, 2025, 08:10 PM UTC

1. investigating Jul 10, 2025, 03:44 PM UTC

   We are currently investigating an issue that is degrading performance and causing connectivity issues for both Flexmls and the Spark API.

2. monitoring Jul 10, 2025, 04:37 PM UTC

   We identified the root cause of the earlier performance and connectivity issues affecting Flexmls and the Spark API. System performance has since stabilized, and services are operating normally. While there is currently no customer impact, we are continuing to monitor closely and are prepared to respond quickly if needed. We’ll provide further updates as necessary.

3. resolved Jul 10, 2025, 08:10 PM UTC

   Performance and connectivity to Flexmls and the Spark API have remained stable, and we have not observed any further issues. This incident is now considered resolved.

Read the full incident report →

Started May 08, 2025, 08:48 PM UTC· resolved May 09, 2025, 12:58 AM UTC

1. investigating May 08, 2025, 08:48 PM UTC

   We are currently investigating an issue with our phone carrier which is not allowing phone calls to be routed to our Support team. While we work on this issue, we remain available to help you via email at [email protected].

2. monitoring May 08, 2025, 09:13 PM UTC

   Our phone system is now fully operational. Our provider has confirmed that the issue has been resolved. We will continue to monitor for stability, but no further disruption is expected at this time. Thank you for your patience.

3. resolved May 09, 2025, 12:58 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 01, 2025, 09:41 PM UTC· resolved May 01, 2025, 11:27 PM UTC

1. investigating May 01, 2025, 09:41 PM UTC

   We are currently investigating an issue where some property photos are not displaying correctly in our system. This may affect photo visibility in listing searches, reports, or client portals. Our team is actively working to identify the root cause and restore full functionality. We will provide updates here as we learn more and will notify you once the issue is resolved. We apologize for the inconvenience and appreciate your patience as we work to resolve this as quickly as possible.

2. monitoring May 01, 2025, 10:30 PM UTC

   We've implemented a temporary workaround that has restored most photo functionality across the system. At this time, photos should be displaying as expected for the majority of users. We are continuing to monitor the situation closely and are working toward a full confirmation that the issue has been fully resolved. Thank you for your continued patience.

3. resolved May 01, 2025, 11:27 PM UTC

   This issue has been fully resolved. Photo functionality has been restored across the system, and all affected services are now operating normally. We’ve confirmed that property photos are displaying as expected in listing searches, reports, and client portals. No further impact is anticipated. Thank you for your patience while we worked to address this.

4. postmortem May 02, 2025, 02:16 PM UTC

   # **Incident Summary** On May 1st, 2025, users reported issues with loading listing photos. It was determined that the problem was related to our storage vendor, Backblaze. While deploying changes to our failover mechanisms to restore user-facing services, we were also working with our Content Delivery Network \(CDN\) vendor, who provided troubleshooting assistance. Shortly after, Backblaze identified and resolved the underlying issue, restoring backend services. ## **Timeline of Events** | **Time \(CDT\)** | **Event** | | --- | --- | | 15:43 | Initial reports of listing photos not loading | | 16:17 | Hosting team engaged | | 16:28 | Additional Hosting team resources engaged | | 16:41 | [Status page event](http://fbs.statuspage.io/incidents/l42hhhmfgp5g) posted | | 17:04 | Root cause identified | | 17:07 | Failover mechanism tweaked/deployed. End-user service restored. | | 17:15 | Engagement with CDN vendor for additional troubleshooting support. | | 17:18 | Notification to Backblaze regarding potential storage issues. | | 17:30 | Status page event updated \(Investigating->Monitoring\) | | 17:40 | Backblaze acknowledges the issue and identifies the root cause. | | 18:00 | Backblaze implements remediation efforts. | | 18:27 | Status page event closed \(Monitoring->Resolved\) | ‌ ## **Root Cause** The root cause of the issue was identified by Backblaze as an increase in HTTP 400 responses from their storage platform. ‌ While multiple failover safeguards are in place to prevent storage outages from affecting the end-user experience, they didn’t cover all failure scenarios. This allowed the backend errors to be delivered to the user, instead of engaging our backup storage platforms. ## **Resolution** The first resolution came shortly after the root cause was identified, when FBS modified the failover mechanism to include this failure scenario. ‌ Backblaze remediated the underlying 400 issue to correct the problems and restore service from their platform. ## **Lessons Learned and Follow-Up Actions** From this incident, we have identified several areas for improvement: ‌ * **Monitoring Enhancements:** We will enhance monitoring systems to allow for quicker identification of problems, as well as provide more proactive alerts for storage and delivery issues. * **Vendor Communication Protocol:** We will verify the communication protocols that we have in place with all vendors for incident reporting and escalation. * **Redundancy and Failover:** We will review and strengthen our redundancy and failover strategies for critical data storage.

Read the full incident report →

Started Feb 20, 2025, 08:50 PM UTC· resolved Feb 21, 2025, 09:28 PM UTC

1. identified Feb 20, 2025, 08:50 PM UTC

   FBS has been made aware of an issue that is impacting multiple Flexmls services. We've identified the underlying issue and are working to mitigate the impact to our users.

2. monitoring Feb 20, 2025, 09:52 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Feb 21, 2025, 09:28 PM UTC

   After monitoring the impacted services for the last day, we're confident that everything is now operating normally. We appreciate your patience and apologize for any inconvenience this may have caused.

Read the full incident report →