Incidents reported on status page for Openfort https://status.openfort.xyz/ https://d1lppblt9t2x15.cloudfront.net/logos/17c337005c86f95a9a5f9a8933027c09.png https://status.openfort.xyz/ en https://status.openfort.xyz/incident/560529 Sun, 11 May 2025 07:58:00 -0000 https://status.openfort.xyz/incident/560529#af7ff82bad4e7b63a582c68d67bb673bc0924d9fc19a79e0efecd46941e58a0a We suffered a downtime for 4 hours that was affecting several of our services, like monitoring and transactions. The cause of such downtime was that AWS banned one of our nodes, and we couldn’t interact with the RPCs and hosted services. https://status.openfort.xyz/incident/560529 Sun, 11 May 2025 07:58:00 -0000 https://status.openfort.xyz/incident/560529#af7ff82bad4e7b63a582c68d67bb673bc0924d9fc19a79e0efecd46941e58a0a We suffered a downtime for 4 hours that was affecting several of our services, like monitoring and transactions. The cause of such downtime was that AWS banned one of our nodes, and we couldn’t interact with the RPCs and hosted services. https://status.openfort.xyz/incident/560529 Sun, 11 May 2025 03:13:00 -0000 https://status.openfort.xyz/incident/560529#4255f12fc811b1da7ef3990e9086f30f991e9435437a4623d620c1ab1aa740ea Transaction and dashboard services are down. Services cannot connect to RPC nodes. https://status.openfort.xyz/incident/560529 Sun, 11 May 2025 03:13:00 -0000 https://status.openfort.xyz/incident/560529#4255f12fc811b1da7ef3990e9086f30f991e9435437a4623d620c1ab1aa740ea Transaction and dashboard services are down. Services cannot connect to RPC nodes. https://status.openfort.xyz/incident/506949 Tue, 04 Feb 2025 11:59:00 -0000 https://status.openfort.xyz/incident/506949#55c902711841b35de90c116c3d51ad8f3ea6dd3339495292aca769e89cc88a69 We've identified the issue and deployed a patch. Thanks! https://status.openfort.xyz/incident/506949 Tue, 04 Feb 2025 10:44:00 -0000 https://status.openfort.xyz/incident/506949#5185eea7c66748569d1435b8d1cdde83e8c7066289fcf3e283f00992d419f2a4 The transactions notifications are being delayed. The team is working to restore to normal service. Transactions are showed as pending in the dashboard if affected. https://status.openfort.xyz/incident/502065 Sun, 26 Jan 2025 15:00:00 -0000 https://status.openfort.xyz/incident/502065#85535580d7bb48dc641187d0e2af02aa51b3f4ac1adecbc99454358180e7224d We have identified the root cause and have issued a patch. The transactions with status pending should now be either confirmed or cancelled. https://status.openfort.xyz/incident/502065 Sat, 25 Jan 2025 19:30:00 -0000 https://status.openfort.xyz/incident/502065#d596a31ed8935513b5b4db1acc33e0db5f5acd2a78f99a558e0173c11b663927 Our indexer is taking longer to process the transactions meaning some of the processed transactions might show as pending and cancelled after 24hours in your dashboard. Our team is looking to restore the indexer to the correct status. https://status.openfort.xyz/incident/475827 Wed, 11 Dec 2024 09:13:00 -0000 https://status.openfort.xyz/incident/475827#bbdc4c6838ae313d0342458a02fd7260dc1d16d903396c14076f0cef0d553186 Post Mortem: We got a huge influx of requests that overwhelmed the API. Ee've scalated the services and are actively working on mitigating the issue in future occasions. https://status.openfort.xyz/incident/475827 Wed, 11 Dec 2024 09:13:00 -0000 https://status.openfort.xyz/incident/475827#bbdc4c6838ae313d0342458a02fd7260dc1d16d903396c14076f0cef0d553186 Post Mortem: We got a huge influx of requests that overwhelmed the API. Ee've scalated the services and are actively working on mitigating the issue in future occasions. https://status.openfort.xyz/incident/475827 Wed, 11 Dec 2024 06:40:00 -0000 https://status.openfort.xyz/incident/475827#711c961e2f5582fbc85dcbf9750eb48d54428d760983881f85a82a44be6a560d We're experiencing high load requests and our services are slowly catching up. Mainly affects dashboard and users authentication. We're issuing a fix this morning. Thank you for your patience https://status.openfort.xyz/incident/475827 Wed, 11 Dec 2024 06:40:00 -0000 https://status.openfort.xyz/incident/475827#711c961e2f5582fbc85dcbf9750eb48d54428d760983881f85a82a44be6a560d We're experiencing high load requests and our services are slowly catching up. Mainly affects dashboard and users authentication. We're issuing a fix this morning. Thank you for your patience https://status.openfort.xyz/incident/474878 Mon, 09 Dec 2024 14:34:00 -0000 https://status.openfort.xyz/incident/474878#70638e0f58fab9bbbd3526801a02211a4ba06abce28cc7ed0b3ccee242bdcc01 Over the weekend, during a period of unusually high load, our API experienced performance degradation caused by a database misconfiguration. The configuration inadvertently capped read/write operations and resulted in CPU resource constraints, creating a bottleneck under peak traffic conditions. Following a thorough investigation, we optimized the database configuration to address these limitations. This resolution has led to a measurable improvement in API latency of up to 20%. To mitigate the risk of similar occurrences, we are implementing enhanced monitoring and proactive configuration reviews to ensure consistent performance, even during high-demand scenarios. https://status.openfort.xyz/incident/474878 Mon, 09 Dec 2024 14:34:00 -0000 https://status.openfort.xyz/incident/474878#70638e0f58fab9bbbd3526801a02211a4ba06abce28cc7ed0b3ccee242bdcc01 Over the weekend, during a period of unusually high load, our API experienced performance degradation caused by a database misconfiguration. The configuration inadvertently capped read/write operations and resulted in CPU resource constraints, creating a bottleneck under peak traffic conditions. Following a thorough investigation, we optimized the database configuration to address these limitations. This resolution has led to a measurable improvement in API latency of up to 20%. To mitigate the risk of similar occurrences, we are implementing enhanced monitoring and proactive configuration reviews to ensure consistent performance, even during high-demand scenarios. https://status.openfort.xyz/incident/442398 Thu, 10 Oct 2024 11:36:00 -0000 https://status.openfort.xyz/incident/442398#0e5ed1fb887ad95f0563054bec3779a60d966e5e9564859535a3e3291316a20f We experienced a DNS misconfiguration that caused the API to return a 302 redirect, depending on the region. Our internal monitoring service, based in a different region, did not detect the issue immediately. We rolled out monitoring services across all regions to ensure earlier detection in the future. https://status.openfort.xyz/incident/442398 Thu, 10 Oct 2024 11:36:00 -0000 https://status.openfort.xyz/incident/442398#0e5ed1fb887ad95f0563054bec3779a60d966e5e9564859535a3e3291316a20f We experienced a DNS misconfiguration that caused the API to return a 302 redirect, depending on the region. Our internal monitoring service, based in a different region, did not detect the issue immediately. We rolled out monitoring services across all regions to ensure earlier detection in the future. https://status.openfort.xyz/incident/428075 Thu, 12 Sep 2024 08:30:00 +0000 https://status.openfort.xyz/incident/428075#38e7fb5082e988ed3c17a371c6e891318bf99d5981a4c21a2f2689a8d4c2a947 Maintenance completed https://status.openfort.xyz/incident/428075 Thu, 12 Sep 2024 07:00:00 -0000 https://status.openfort.xyz/incident/428075#2d8080ff6820f4d1b3566a9604b95a2bc3a90332b6dc7d015b76babfd6827e5e We're running an update in our database and the service will be down during the time of execution.