Is Foleon Down Right Now? Check if there is a current outage ongoing.

This incident has been resolved.

The team is currently investigating the issue.

This incident has been resolved.

Users may be experiencing platform access issues. Our team is currently investigating and working to resolve the issue as quickly as possible. We appreciate your patience.

This incident has been resolved.

Our team has identified the following issues and is actively working on a resolution: - We are currently investigating an issue where saving Domain settings at the Workspace level fails silently. Our team is working on a fix, and we will provide updates as soon as possible.

The SSO issue has been resolved. Access should return to normal as systems propagate the change. Thank you for your patience!

We have identified that the SSO issue affects a very small number of customers with specific configurations. As a workaround, users can log in using email and password if their account allows it.

We are aware of an issue where SSO login may not work for users from agency partner accounts. Our team is investigating, and we will provide updates as soon as possible. Thank you for your patience.

The issue causing images to not load for some users has been identified and resolved. Our team has implemented a fix, and all systems are now fully operational.

This incident has been resolved.

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented.

We are currently experiencing downtime with Foleon Analytics. Our team is actively working to resolve the issue as quickly as possible.

The issue has been successfully resolved. However, changes made to the Doc settings and Global Doc settings between 11:50 and 15:20 CEST may not have been saved. Therefore, it is necessary to reapply these Doc settings and Global Doc settings and republish the affected Docs.

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

We are currently experiencing an outage with one of our database hosts. To ensure continued service, we are in the process of migrating our databases to a different region.

We are currently experiencing an outage with one of our database hosts. To ensure continued service, we are in the process of migrating our databases to a different region.

The Foleon platform is currently experiencing technical difficulties. The Development team is working to resolve the issue.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue. The data is still being stored, it's only not visual in the reporting.

This incident has been resolved.

The Foleon platform is currently experiencing technical difficulties. The Development team is working to resolve the issue.

The issue affecting SSO login and document access has been resolved. All users should now have full access to their documents. The incident was caused by a communication problem between our internal services, which was promptly identified and addressed by our team. We apologize for the disruption and appreciate your patience as we worked to resolve the issue.

We are currently investigating reports of login errors for some users attempting to access our services via Single Sign-On (SSO). Affected users have also reported that their documents are not accessible. Our team is actively working to identify and resolve the issue. We apologize for the inconvenience and will provide further updates as soon as more information becomes available. Thank you for your patience and understanding.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We are currently investigating reports of login errors for some users attempting to access via Single Sign-On (SSO) following this morning's maintenance. Our team is actively working to resolve the issue, and we will provide further updates as soon as possible.

This incident has now be resolved.

We noticed that in some cases the Foleon Doc will not show after the user has logged in through SSO.

We have a fix in place. If you are experiencing any problems with your Foleon Docs hosted on a custom domain using a proxy, please contact our Support Team. They will guide you through the necessary steps to bring your Foleon Docs back online.

We have identified the issue and have a fix. If you are experiencing any problems with your Foleon Docs hosted on a custom domain using a proxy, please contact our Support Team. They will guide you through the necessary steps to bring your Foleon Docs back online.

At the moment we are experiencing an issue with custom domains that are setup with a proxy (e.g. Cloudflare, Azure). We are looking into the issue.

This incident has been resolved. A postmortem will be initiated to prevent future incidents.

A fix has been implemented. We are monitoring the performance.

We are currently investigating the issue

The issue is now resolved.

A fix has been implemented and the team is currently monitoring.

The cause has been identified and the team is working on a fix.

We are aware of an issue in the editor where you are not able to scroll through the pages overview.

This incident has been resolved.

We have implemented a fix and are currently monitoring the stability.

We are currently experiencing stability issues with regards to duplicating Foleon Documents within the platform. Our team is working hard to resolve the issue ASAP.

This incident has been resolved.

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

We are currently investigating this issue.

The fix is stable and the incident has been resolved.

We found the cause and immediately implemented a fix. The issue is now resolved. We are now monitoring.

We found an issue that blocks users from logging in. We are investigating the issue.

This incident has been resolved.

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

We are continuing to work on a fix for this issue.

We have identified an issue where public previews are not accessible when the user is not logged in on the Foleon Platform. We have already identified the cause and are working on a fix.

We’ve been able to resolve the issue but still monitoring the root cause.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are experiencing issues with the certificate renewal workflow. We are optimising the process and will keep you updated. This can potentially result in a certificate not being renewed in time automatically. We are doing everything we can to resolve the issue as soon as possible.

We’ve experience 2 hours downtime on imagery during our maintenance window. The scheduled maintenance window wasn’t updated accordingly. The security maintenance have been successfully updated and all systems are running accordingly.

This incident has been resolved. All SAML responses are being handled correctly.

A fix has been implemented and we are not seeing any failed SAML responses coming in. We will keep monitoring the issue.

For a small portion of our customers, SAML is not working. This can result in 404 pages on logging into the platform or published Foleon Docs that are gated with SAML/SSO. If you’re not using SAML, everything is working as expected. We are continuing to investigate this issue.

We are continuing to investigate this issue

We are still investigating the problems with SAML. However, to fix the issue permanently; we advice our customers who are using *.instantmagazine.com/saml as their EntityID to update it to *.foleon.com/saml. This is also true for EntityIDs that use api.instantmagazine.com/auth/saml/*. Please update those to api.foleon.com/auth/saml/*.

We are continuing to investigate this issue

For a small portion of our customers, SAML is not working. This can result in 404 pages on logging into the platform or published Foleon Docs that are gated with SAML/SSO. If you’re not using SAML, everything is working as expected. We’re currently working on a way to resolve this.

This incident has been resolved.

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

The issue has been identified and a fix is being implemented.

Doc urls (alias) without a slash at the end, will not match and will be redirected to the default document of the project. We are working on a fix to correctly redirect these docs again.

This incident has been resolved.

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

The issue has been identified and a fix is being implemented.

We are currently investigating an issue, which blocks users from accessing folders in Media library. A workaround, for now, is to refresh the Editor to access the folder. Updates will follow.

A malfunction in the cache system caused our static files not to be executed by the browser, affecting the interactivity of Foleon Docs. We apologize for the inconvenience.

This issue has now been resolved! Thank you for patience.

Our application is now fully operational again. We are currently monitoring for full resolution.

We are continuing to investigate the issue.

Our application is running unstable. This can impact loading the preview, editor and doing changes in the editor. Updates will follow.

This issue has now been resolved! Thank you for patience.

We have identified the cause of this error and applied a fix. We are currently monitoring for full resolution.

This incident is caused by the expired certificate that prevented all of the files that were served from assets.foleon.com from loading correctly on Foleon. Our team is currently working on implementing a fix.

We are currently investigating an issue with the images not loading across Foleon Docs, starting from approximately 23/11/2022 at 04:00 AM CET. It’s currently unclear whether other parts of our platform are also affected by this issue. Updates will follow.

We’ve experienced an issue with one of our services which caused our Viewer to be very slow in a period from 5 PM to 5.20 PM CET. The development team has already implemented the fix and Viewer response time is back to normal speed. Sorry for the inconvenience!

We've been experiencing inconsistency in performance with Editor, Preview and Publisher due to issues with CS Prod starting from around 08/08/2022 at 12 PM CET. The dev team has already implemented the fix and this issue has now been resolved. All affected Publisher jobs were processed successfully. Thank you for your patience!

This issue has now been resolved. Thank you for your patience.

This issue has now been resolved. Thank you for your patience.

We have identified the cause of this error and applied a fix. We are currently monitoring for full resolution.

Our development team is working to identify the root cause and implement a solution.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently investigating an issue with the performance of the Editor (slow loading + auto-save functionality), starting from approximately 29/06/2022 at 9 a.m. CET. Updates will follow.

Some users has been experiencing trouble when logging in to https://app.foleon.com/dashboard since 8:30p.m. CEST. During this time, our development team had been investigating issues related to traffic not reaching the cluster. Currently the traffic has been restored and all services are operational. Thanks for your patience.

Due to an incident with tracking, both Foleon Analytics and Google Analytics of Foleon Docs did not record traffic for Foleon Docs that have been published on March 31st. This issue has been addressed on April 1st and all affected Foleon Docs have undergone a fix. It is possible that customers with affected Foleon Docs are missing tracking data for the day of March 31st.

This incident has been resolved.

We are currently investigating an issue with the performance of the preview, starting from approximately 02/03/2022 at 11:21 CET. Updates will follow.

This incident has been resolved.

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

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

Foleon Docs hosted with DNS settings s1.instantmagazine.com are experiencing issues. Make sure to move your DNS to s1.foleon.com instead of s1.instantmagazine.com. Our team is working on a solution to get the legacy domain back online.

This incident is no longer affecting our platform.

All services are fully recovered and have been stable for 50+ minutes. However, we are continuing to monitor the upstream incident that caused this: https://status.cloud.google.com/incidents/6PM5mNd43NbMqjCZ5REh

We are continuing to monitor for any further issues.

Due to networking issues our service was unavailable for 20 minutes. The issue has been resolved. We are currently monitoring the situation. Published Foleon Docs have not been affected

This incident has been resolved.

We are continuing to work on a definitive fix. For now, we ask that you clear your Foleon Docs cookies to resolve the issue. To do this, go to https://app.foleon.com and clear cookies from that page. Updates will follow.

The issue has been identified and a fix is being implemented.

We’ve noticed that part of our users are currently unable to log into our platforms, starting from approximately 20/10/2021 at 12:15 CET. Updates will follow. Our developers are investigating this issue.

We have identified the cause of this error and applied a fix. The problem has been resolved.

We are continuing to investigate this issue.

We are currently investigating an issue with the availability/performance of part of the data of our native reports, starting from approximately 14/10/2021 at 11:30 CET. Currently we can verify that no other parts of the platform are affected. Updates will follow.

There have been connection issues in our network which caused preview to experience down time. The problem has been resolved permanently.

There have been connection issues in our network which caused SAML and preview to experience down time. The problem has been resolved permanently.

We are currently investigating an issue with the availability/performance of the previews, starting from approximately 30/09/2021 at 16:14 CET. At the moment SSO and SAML are also affected by this issue. Updates will follow.

This incident was caused by failed automatic software updated causes a momentary interruption. We found that all live publications were affected from 17/08/2021 at 8:03 CET until 8:17 CET. This issue has now been resolved. No additional steps required.

This incident has been resolved.

This issue has now been resolved. No additional steps required.

This incident is caused by certificate auto-renewing failure on one of our services. We found that the entire editor and the dashboard are affected. Our team is currently working on implementing a fix.

We are currently investigating an issue with the login of our platform, starting from approximately 10/08/2021 at 10:58 CET.

We have been informed that this issue has now been resolved. Unsplash images and Vimeo videos are back in the editor, preview and published Foleon Docs. No further actions required.

The issue has been identified, we're dependent of external platforms and are closely monitoring them.

We have been informed that a cloud computing service provider that’s been used by a lot of bigger companies is currently facing downtime. For our platform this means videos from Vimeo and images coming from our native Unsplash integration are currently not showing on editor, preview and published Foleon Docs. We’re monitoring this closely and will inform you once these services are available again.

This incident has been resolved and is continuously being monitored by our development team.

Due to a temporary interference in our API, the Foleon platform (Dashboard & editor) is currently unavailable. Live publications are not affected.

This incident has been resolved.

We are continuing to work on a fix for this issue.

Due to a temporary interference in our API, the Foleon platform (Dashboard & editor) is currently unavailable. Live publications are not affected.

This incident has been resolved.

Logging in to publications or the Foleon platform through SSO is unavailable right now for Foleon hosted Federation Metadata XML files. Starting from approximately 11/03/2021 at 09:00 CET. If the metadata is hosted by our customers logging in through SSO should still work. Please note this only applies for accounts or publications that are gated with our SSO for which Foleon hosts Federation Metadata XML files. All other publications and accounts are available and fully operational

The issue has now been resolved. All Name Servers are up and running again and live publications are all available again. Furthermore, creation of new projects and screenshots of older Media Library assets were also temporarily unavailable. These too, are now working as intended again.

There was a power outage in one of our data centers impacting our Instant Magazine Name Server. This caused part of the live publications (hosted via s1.instantmagazine.com) to be unavailable for +/- 30 minutes. This issue mainly impacts Instant Magazine Origin customers.

Due to a large amount of \(non-human\) bot traffic, our services got overloaded. This unfortunately caused downtime on live publications for a lot of our visitors. We have implemented the following to prevent outage in the future: * Upgraded servers * Improved monitoring alerting systems We are still investigating the details of this issue. We are also looking into more long-term solutions such as an escalations plan for outside our office hours and more. The estimated impact window is approximately 6 hours \(11:45 - 17:30 CET\).

Publications hosted on custom domains, hosted by Foleon experienced downtime during the day. Visitors were prompted with a Foleon branded 404 page. This issue has now been fixed. We're still investigating the cause.

This incident has been resolved. The publishing queue will be resumed now.

Due to problems with our TLS certificates we are facing some downtime on the API. Live publications are not affected, but it could be that you face issues accessing our Dashboard, editor or the preview of your publication. The publishing queue is also on hold for now.

This incident has been resolved.

We are working on an issue with reporting that infects our publishing queue. This means the publishing queue is currently on hold and publishing is not possible.

Part of the cluster failed to come back up after reconfiguration