Forest Admin Outage History
Forest Admin is up right nowPingoru has recorded 19 incidents for Forest Admin: 1 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 194 of 720 (27%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 744 (0%) |
| November 2026 | 0 | 0 of 99 (0%) |
Incidents, newest first
Major April 9, 2026 Users cannot bootstrap customization on Cloud projects. 8d 2h Cloud Gateway
Started Apr 09, 2026, 10:00 AM UTC· resolved Apr 17, 2026, 12:14 PM UTC
- resolved Apr 17, 2024, 12:14 PM UTC
The patch has been released and the service is now restored.
- investigating Apr 09, 2026, 10:00 AM UTC
An error is raised: "✖ Bootstrap failed: Please install sqlite3 package manually." The contribution that introduced the regression is identified, the team is currently looking for a way to patch it and resume the customization feature on Cloud projects.
- resolved Apr 17, 2026, 12:14 PM UTC
The patch has been released and the service is now restored.
Minor October 21, 2025 Backend service degradation 7m
Started Oct 21, 2025, 09:30 AM UTC· resolved Oct 21, 2025, 09:37 AM UTC
- resolved Oct 21, 2025, 09:37 AM UTC
Incident resolved
- investigating Oct 21, 2026, 09:30 AM UTC
We experienced a brief service degradation between 11:30 and 11:49 CEST where some users encountered errors when accessing the platform. The issue was caused by some of our servers reaching their connection capacity during peak usage. All services are now operating normally. We sincerely apologize for the inconvenience and appreciate your patience.
- resolved Oct 21, 2026, 09:37 AM UTC
Incident resolved
Major October 20, 2025 Backend unavailable 30m Cloud Gateway
Started Oct 20, 2025, 08:00 AM UTC· resolved Oct 20, 2025, 08:30 AM UTC
- investigating Oct 20, 2025, 08:30 AM UTC
End of the incident
- investigating Oct 20, 2026, 08:00 AM UTC
Starting at 10:00 a.m., our backend experienced downtime due to simultaneous outages affecting AWS and Heroku services worldwide. By 10:30 a.m., we successfully updated our routing policy on AWS to fully switch our backend to our multi–availability zone AWS infrastructure, restoring service stability. Thank you for your patience and understanding 🙏
- resolved Oct 20, 2026, 08:30 AM UTC
End of the incident
Minor July 5, 2025 API failing to authenticate users 365d
Started Jul 05, 2025, 02:33 PM UTC· resolved Jul 05, 2026, 02:33 PM UTC
- investigating Jul 05, 2025, 02:33 PM UTC
The issue has been identified and solved. All services are up and running. We apologize for any inconvenience this may have caused and thank you for your patience. Incident report : https://forest.slite.page/p/8Iik3jo9_MXQZn/Incident-2025-07-05
- investigating Jul 05, 2026, 11:08 AM UTC
Our API is currently failing to authenticate users. Our technical team is actively investigating the issue.
- resolved Jul 05, 2026, 02:33 PM UTC
The issue has been identified and solved. All services are up and running. We apologize for any inconvenience this may have caused and thank you for your patience. Incident report : https://forest.slite.page/p/8Iik3jo9_MXQZn/Incident-2025-07-05
Major June 11, 2025 App unavailable 365d
Started Jun 11, 2025, 07:05 AM UTC· resolved Jun 11, 2026, 07:05 AM UTC
- resolved Jun 11, 2025, 07:05 AM UTC
The issue with our provider has been fully resolved. All services are back up and running normally. We apologize for any inconvenience this may have caused and thank you for your patience.
- investigating Jun 10, 2026, 03:34 PM UTC
We are currently experiencing a service disruption due to an ongoing outage at our hosting provider, Heroku. You can follow their status updates here: https://status.heroku.com/incidents/2822. Our technical team is actively investigating the impact on our services and is closely monitoring the situation. We will continue to provide updates here as we learn more. Thank you for your patience and understanding.
- investigating Jun 10, 2026, 06:04 PM UTC
We've mitigated the issue by deploying our application on AWS. The application should be back but custom domains are still not working. If you are on a custom domain, please add app.forestadmin.com to your CORS configuration and access https://app.forestadmin.com instead.
- resolved Jun 11, 2026, 07:05 AM UTC
The issue with our provider has been fully resolved. All services are back up and running normally. We apologize for any inconvenience this may have caused and thank you for your patience.
Major March 26, 2025 Outage on service: Public API 365d
Started Mar 26, 2025, 04:22 PM UTC· resolved Mar 26, 2026, 04:22 PM UTC
- resolved Mar 26, 2025, 04:22 PM UTC
Public API is now restored
- investigating Mar 26, 2026, 04:01 PM UTC
Outage started at 17:01 (GMT+1) Outage ended at 17:22 (GMT+1) Servers have stopped responding to requests due to incorrect configuration. After a reconfiguration, systems have been able to start up properly and we could answer to requests. https://docs.forestadmin.com/public-api
- resolved Mar 26, 2026, 04:22 PM UTC
Public API is now restored
Minor January 22, 2025 Smart Charts And Alter values issue 365d
Started Jan 22, 2025, 11:47 AM UTC· resolved Jan 22, 2026, 11:47 AM UTC
- resolved Jan 22, 2025, 11:47 AM UTC
The issue is now resolved. We want you to know that we’re working internally to prevent similar issues in the future and are deeply sorry for the inconvenience.
- investigating Jan 22, 2026, 09:48 AM UTC
We’re currently investigating reports of a potential issue on Smart Charts and Alter values. We apologize for any inconvenience and will post another update as soon as we learn more.
- investigating Jan 22, 2026, 11:17 AM UTC
We have identified the source of the issue and are rolling back one of this morning's releases to resolve it.
- resolved Jan 22, 2026, 11:47 AM UTC
The issue is now resolved. We want you to know that we’re working internally to prevent similar issues in the future and are deeply sorry for the inconvenience.
Minor January 20, 2025 Collections are hidden 365d
Started Jan 20, 2025, 09:51 AM UTC· resolved Jan 20, 2026, 09:51 AM UTC
- resolved Jan 20, 2025, 09:51 AM UTC
The issue is now resolved. We want you to know that we’re working internally to prevent similar issues in the future and are deeply sorry for the inconvenience.
- investigating Jan 17, 2026, 04:00 PM UTC
Some customers have reported that their collections are not visible. We are currently investigating the issue.
- investigating Jan 20, 2026, 09:38 AM UTC
We identified the cause of the hidden collections issue some clients were experiencing. Those affected were using the new folder feature. They were able to generate unexpected requests that resulted in folders being created but not listed. As a result, after a refresh, those folders and their contents would disappear. We have addressed the issue on our backend, and a migration is currently underway to fix the affected projects. The issue should be resolved within a few minutes. We are still investigating how these requests were generated.
- resolved Jan 20, 2026, 09:51 AM UTC
The issue is now resolved. We want you to know that we’re working internally to prevent similar issues in the future and are deeply sorry for the inconvenience.
Major January 8, 2025 Forest is unavailable 364d 23h
Started Jan 08, 2025, 10:49 AM UTC· resolved Jan 08, 2026, 10:19 AM UTC
- investigating Jan 08, 2025, 10:49 AM UTC
A migration of our database has been incorrectly propagated across our instances, preventing some of our customers to have access to their project.
- investigating Jan 08, 2026, 10:19 AM UTC
We are currently experiencing a service outage. This outage has affected our api. The engineering team is working to identify the root cause and fix the issue. We apologize for any inconvenience and we'll keep you updated on the status.
- resolved Jan 08, 2026, 10:33 AM UTC
The service is back to normal! We want you to know that we’re working internally to prevent similar issues in the future and are deeply sorry for the inconvenience. We are still investigating the reason behind.
- investigating Jan 08, 2026, 10:49 AM UTC
A migration of our database has been incorrectly propagated across our instances, preventing some of our customers to have access to their project.
Minor December 16, 2024 Collections suddenly disappeared from the navigation bar 365d
Started Dec 16, 2024, 05:34 PM UTC· resolved Dec 16, 2025, 05:34 PM UTC
- investigating Dec 16, 2024, 05:34 PM UTC
We released a contribution that introduced a regression on some project. Some of their collections were not visible anymore because of data inconsistency on our side. We have reverted the culprit contribution to take the time to investigate more on it.
- investigating Dec 16, 2025, 04:32 PM UTC
Some collections are not showing anymore in the navigation bar on the left
- resolved Dec 16, 2025, 05:34 PM UTC
We released a contribution that introduced a regression on some project. Some of their collections were not visible anymore because of data inconsistency on our side. We have reverted the culprit contribution to take the time to investigate more on it.
Minor December 3, 2024 Related data displays more items than expected 365d
Started Dec 03, 2024, 12:53 PM UTC· resolved Dec 03, 2025, 12:53 PM UTC
- investigating Dec 03, 2024, 12:53 PM UTC
The issue is now solved, you will need to refresh your page to fix it. This regression was introduced while doing a technical migration of our app framework. We want you to know that we’re working internally to prevent similar issues in the future and are deeply sorry for the inconvenience.
- investigating Dec 03, 2025, 10:23 AM UTC
Our app is currently experiencing an issue where "belongs to" data is unexpectedly displayed as a record alongside the actual records in the Related Data views
- investigating Dec 03, 2025, 11:36 AM UTC
We’re currently investigating the issue and will keep you updated once we got more information.
- resolved Dec 03, 2025, 12:53 PM UTC
The issue is now solved, you will need to refresh your page to fix it. This regression was introduced while doing a technical migration of our app framework. We want you to know that we’re working internally to prevent similar issues in the future and are deeply sorry for the inconvenience.
Minor November 28, 2024 A current technical migration is locking our main database for unexpected reasons. 364d 16h
Started Nov 28, 2024, 05:04 PM UTC· resolved Nov 28, 2025, 09:12 AM UTC
- investigating Nov 28, 2024, 05:04 PM UTC
This morning, our Technical Team triggered a release containing a database migration to prepare a new important feature. This migration aimed to update our main database. The migration locked the main database to execute schema and data transformation. For the entire time the migration was running, a transaction lock prevented users from accessing our main database, via API calls, for their own needs. All requests ended up in error. This migration used a new utility function that was introduced last week to prevent migrations from running more than once (in very rare concurrent cases) but its usage requires further work. Our Technical Team is currently working on aligning migration practices and documentation for this new utility function. This will prevent similar events in the future. Thank you for your patience during this incident.
- investigating Nov 28, 2025, 09:12 AM UTC
The migration should be finalized soon. Our team is investigating why such generic migration led to the current situation.
- resolved Nov 28, 2025, 09:16 AM UTC
The locks are decreasing and the service is now available. We will continue to investigate why this specific technical migration degraded our service.
- investigating Nov 28, 2025, 05:04 PM UTC
This morning, our Technical Team triggered a release containing a database migration to prepare a new important feature. This migration aimed to update our main database. The migration locked the main database to execute schema and data transformation. For the entire time the migration was running, a transaction lock prevented users from accessing our main database, via API calls, for their own needs. All requests ended up in error. This migration used a new utility function that was introduced last week to prevent migrations from running more than once (in very rare concurrent cases) but its usage requires further work. Our Technical Team is currently working on aligning migration practices and documentation for this new utility function. This will prevent similar events in the future. Thank you for your patience during this incident.