Is Forest Admin down?

Last checked just now
Current status
Forest Admin is up

No incidents right now.

Official status page: https://status.forestadmin.com · Polled every 5 minutes · 1 component tracked

Forest Admin is operational right now. Last checked just now; the most recent incident resolved 3d ago.

Real-time Forest Admin status, recent outages, and incident history — pulled directly from Forest Admin's official status page at https://status.forestadmin.com every 5 minutes. Pingoru tracks 1 Forest Admin service and has captured 5 incidents in the last 90 days (94.44% uptime). Get email, Slack, Discord, or webhook alerts the moment Forest Admin reports a new incident — free for 5 monitors, no credit card.

Users who monitor Forest Admin also follow these Project Management services: Atlassian Jira Software Trello Asana Incident IQ Notion Shortcut Jira Service Management LaunchDarkly Basecamp View all 6,000+ providers
Forest Admin uptime 94.44% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 15h 31m
    Started Jun 10, 2026, 03:34 PM UTC · Resolved Jun 11, 2026, 07:05 AM UTC
    Timeline · 3 updates
    • investigating · Jun 10, 2025, 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, 2025, 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, 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.

    Latest: 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 p…

  2. Resolved 11m
    Started May 16, 2026, 03:58 PM UTC · Resolved May 16, 2026, 04:09 PM UTC
    Timeline · 3 updates
    • investigating · May 16, 2024, 04:09 PM UTC

      The team quickly investigated to understand the reasons of these errors. We have rollbacked a recent contribution that led to the current situation. All API services are now up and running.

    • investigating · May 16, 2025, 03:58 PM UTC

      All API endpoints respond with the 500 status code.

    • resolved · May 16, 2025, 04:09 PM UTC

      The team quickly investigated to understand the reasons of these errors. We have rollbacked a recent contribution that led to the current situation. All API services are now up and running.

    Latest: The team quickly investigated to understand the reasons of these errors. We have rollbacked a recent contribution that led to the current situation. All API services are now up and…

  3. Resolved
    Started Apr 15, 2026, 09:22 AM UTC · Resolved Apr 15, 2026, 09:22 AM UTC
    Timeline · 4 updates
    • investigating · Apr 18, 2024, 02:16 PM UTC

      All the missing activity logs have been re-introduced. This is the final update for this incident.

    • investigating · Apr 15, 2026, 09:22 AM UTC

      The team is currently investigating on this regression.

    • resolved · Apr 18, 2026, 01:25 PM UTC

      The service is now fully functional again. The team will re-introduce the missing activity logs via a dedicated migration, by the end of the week.

    • investigating · Apr 18, 2026, 02:16 PM UTC

      All the missing activity logs have been re-introduced. This is the final update for this incident.

    Latest: All the missing activity logs have been re-introduced. This is the final update for this incident.

  4. Resolved 21m
    Started Mar 26, 2026, 04:01 PM UTC · Resolved Mar 26, 2026, 04:22 PM UTC
    Timeline · 3 updates
    • 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

    Latest: Public API is now restored

Outage history

Past 90 days · 4 incidents View full outage history →