Is FBS down?
Last checked 11m agoNo incidents right now.
FBS is operational right now. Last checked 11m ago; the most recent incident resolved 11d ago.
Real-time FBS status, recent outages, and incident history — pulled directly from FBS's official status page at https://fbs.statuspage.io every 5 minutes. Pingoru tracks 6 FBS services and has captured 5 incidents in the last 90 days (99.63% uptime). Get email, Slack, Discord, or webhook alerts the moment FBS reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Flexmls Web
Timeline · 3 updates
- 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.
- 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.
- 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.
Latest: 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…
-
- Service Access Issues ResolvedStarted Jun 02, 2026, 03:46 PM UTC · Resolved Jun 02, 2026, 06:28 PM UTC · 2h 41m