ChartHop API is not responding
Timeline · 2 updates
- investigating Mar 26, 2026, 10:35 PM UTC
We are currently investigating this issue.
- resolved Mar 26, 2026, 10:45 PM UTC
This incident has been resolved.
There were 3 ChartHop outages since February 9, 2026 totaling 2h 27m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
This incident has been resolved.
ChartHop leverages MongoDB as a primary data store. MongoDB experienced a major service outage impacting data stores in AWS. This impacts ChartHop and is caused our application to fail. The issue has been mitigated and we are monitoring.
This incident has been resolved.
We are seeing an increased rate of errors specifically coming from the ChartHop user interface. This is impacting users ability to navigate and use the product. API servers and Apps/integrations are not seeing increased error rates overall, and impacts are limited to UI access.
We have identified an issue with routing between our User Interface and API servers that was sending a portion of API traffic to the wrong servers. The routing issue has been addressed and service should be restored for all users.
The system is operating as expected and error rates have returned to normal.
Pingoru polls ChartHop's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required