MyFoncia focuses on rental and co-ownership management for several million users in France. When the platform refuses to load or an account seems blocked, the first reaction is to suspect a server outage. Field reports show a more nuanced reality: most of the reported blockages in 2026 are due to account linking issues or local configuration problems, not global unavailability of the platform.
MyFoncia orphan account: the most common false outage
A change of manager, a transfer of mandate between Foncia agencies, or a simple email address update is enough to desynchronize an account. The user then encounters an error page or an empty space, interpreted as a technical bug.
This phenomenon of orphan accounts poorly linked to the agency cannot be resolved on the user side. Neither clearing the cache nor resetting the password changes anything. Only a manual intervention from the Foncia agency linked to the file can restore the connection between the online account and the management data.
Several co-owners who experienced a change of property manager within the Foncia network report variable recovery times, sometimes several business days. To quickly identify this type of blockage, it is useful to consult Chrono Immobilier’s solutions that detail the appropriate diagnostic procedure.
The reflex to adopt: check if the email associated with the account matches the one known by the current agency. In case of doubt, a call during business hours remains the most direct recourse.
Accessing MyFoncia from abroad: blocking DNS filters and proxies
Users trying to connect to MyFoncia from a hotel, a corporate network abroad, or via public Wi-Fi regularly encounter endless loading screens. This blockage has nothing to do with a geographical restriction imposed by Foncia.
The problem arises from DNS filters and proxies on certain networks that block technical subdomains of the platform. The main domain may remain accessible while requests to the authentication servers are silently cut off.
Three concrete ways to bypass this type of blockage:
- Switch to a mobile connection (4G/5G) instead of the establishment’s Wi-Fi, which bypasses local DNS filters
- Manually change the DNS servers on the device (using Google’s or Cloudflare’s) to avoid resolutions blocked by the host network
- Use the MyFoncia mobile app instead of the browser, as it manages its own network resolutions and bypasses certain web proxies
The mobile app is indeed a reliable alternative in general. It allows access to documents, receipts, and charge statements even when the website malfunctions on a given browser.
Anti-tracking extensions and browsers: invisible blockages
A login form that does not respond, a blank page after entering credentials: these symptoms often point to a conflict between MyFoncia and privacy protection tools installed in the browser.
Anti-tracking extensions block the authentication scripts of the platform. The tools most frequently responsible are uBlock Origin, Privacy Badger, Ghostery, and the enhanced tracking protection built into Firefox.
The quickest test is to open a private browsing window (which disables most extensions by default) and attempt to log in. If it succeeds, the problem is confirmed on the extensions side.
Rather than globally disabling an ad blocker, it is preferable to add the MyFoncia domain to the whitelist of the relevant extension. This manipulation preserves protection on other sites while restoring access to the client area.
Cache and cookies: targeted cleaning rather than global
Clearing the entire browser cache is a common but excessive recommendation. A targeted cleaning of cookies from the foncia domain is sufficient in most cases. On Chrome, this is done through the privacy settings by filtering by domain name. On Firefox, the procedure goes through the privacy preferences, cookies, and site data section.
MyFoncia server outage or local problem: distinguish between the two in less than two minutes
Before contacting support or spending an hour changing settings, a quick diagnosis can determine whether the unavailability is on Foncia’s side or a problem specific to the device or network used.
- Check a status tracking site like Statut Services or TotalBug, which aggregate real-time reports and display trends over the last hours
- Test the connection from a second device (phone on 4G, a friend’s computer) to isolate the network as a variable
- Check if other web services are functioning normally, as a local DNS problem often affects multiple sites simultaneously
If the tracking sites show no recent reports and the connection fails only from a specific device or network, the problem is local and not related to MyFoncia servers. Corrective actions then focus on the browser, extensions, or account linking.
In the case of a confirmed server outage, the available data does not allow predicting recovery times. Documented global incidents on tracking platforms show resolutions within a few hours in most observed cases. Contacting the local Foncia agency remains relevant to obtain urgent documents (receipts, fund requests) via email while waiting for a return to normal.