The latency issue affecting our Customer Metric Integration endpoints has been resolved. All services operate normally now, and timeout errors should no longer occur.
Posted May 22, 2025 - 09:09 UTC
Monitoring
The issue has been resolved, and we are currently monitoring the system to ensure continued stability.
If you were experiencing timeouts while fetching metrics, those should now be resolved. We will continue to observe the system and provide further updates if necessary.
Posted May 22, 2025 - 07:37 UTC
Update
Our Engineering team is continuing to investigate the root cause of the issue.
If you are seeing timeouts when attempting to fetch metrics, we recommend temporarily increasing your timeout value to 20 seconds until this incident is resolved.
Posted May 22, 2025 - 04:30 UTC
Update
Engineering are continuing to investigate the root cause of the issue.
If you are seeing timeouts when attempting to fetch metrics we recommend increasing your timeout value to 20 seconds temporarily until this incident is resolved.
Posted May 22, 2025 - 00:45 UTC
Update
Engineering are continuing to investigate the root cause of the issue.
If you are seeing timeouts when attempting to fetch metrics we recommend increasing your timeout value to 20 seconds temporarily until this incident is resolved.
Posted May 21, 2025 - 23:46 UTC
Update
Engineering are continuing to investigate the root cause of the issue.
If you are seeing timeouts when attempting to fetch metrics we recommend increasing your timeout value to 20 seconds temporarily until this incident is resolved.
Posted May 21, 2025 - 22:47 UTC
Update
Engineering are continuing to investigate the root cause of the issue.
If you are seeing timeouts when attempting to fetch metrics we recommend increasing your timeout value to 20 seconds temporarily until this incident is resolved.
Posted May 21, 2025 - 21:48 UTC
Update
Engineering are continuing to investigate the root cause of the issue.
If you are seeing timeouts when attempting to fetch metrics we recommend increasing your timeout value to 20 seconds temporarily until this incident is resolved.
Posted May 21, 2025 - 20:50 UTC
Update
Engineering are continuing to investigate the root cause of the issue.
If you are seeing timeouts when attempting to fetch metrics we recommend increasing your timeout value to 20 seconds temporarily until this incident is resolved.
Posted May 21, 2025 - 19:57 UTC
Update
Engineering are continuing to investigate the root cause of the issue.
If you are seeing timeouts when attempting to fetch metrics we recommend increasing your timeout value to 20 seconds temporarily until this incident is resolved.
Posted May 21, 2025 - 18:51 UTC
Update
Engineering are continuing to investigate the root cause of the issue.
If you are seeing timeouts when attempting to fetch metrics we recommend increasing your timeout value to 20 seconds temporarily until this incident is resolved.
Posted May 21, 2025 - 17:35 UTC
Update
Engineering are continuing to investigate the root cause of the issue.
If you are seeing timeouts when attempting to fetch metrics we recommend increasing your timeout value to 20 seconds temporarily until this incident is resolved.
Posted May 21, 2025 - 16:13 UTC
Update
Engineering are continuing to investigate the root cause of the issue.
If you are seeing timeouts when attempting to fetch metrics we recommend increasing your timeout value to 20 seconds temporarily until this incident is resolved.
Posted May 21, 2025 - 14:44 UTC
Investigating
Engineering have identified an increase in latency with our Customer Metric Integration endpoints, they are currently investigating the cause.
If you are seeing timeouts when attempting to fetch metrics we recommend increasing your timeout value to 20 seconds temporarily until this incident is resolved.
Posted May 21, 2025 - 13:40 UTC
This incident affected: AuraDB Virtual Dedicated Cloud (*.databases.neo4j.io) (AuraDB Virtual Dedicated Cloud on AWS (*.databases.neo4j.io), AuraDB Virtual Dedicated Cloud on Azure (*.databases.neo4j.io), AuraDB Virtual Dedicated Cloud on GCP (*.databases.neo4j.io)), AuraDB Professional (*.databases.neo4j.io) (AuraDB Professional on AWS (*.databases.neo4j.io), AuraDB Professional on Azure (*.databases.neo4j.io), AuraDB Professional on GCP (*.databases.neo4j.io)), AuraDS (*.databases.neo4j.io) (AuraDS on AWS (*.databases.neo4j.io), AuraDS on Azure (*.databases.neo4j.io), AuraDS on GCP (*.databases.neo4j.io)), AuraDS Enterprise (*.databases.neo4j.io) (AuraDS Enterprise on AWS (*.databases.neo4j.io), AuraDS Enterprise on Azure (*.databases.neo4j.io), AuraDS Enterprise on GCP (*.databases.neo4j.io)), AuraDB Business Critical (*.databases.neo4j.io) (AuraDB Business Critical (*.databases.neo4j.io) on AWS, AuraDB Business Critical (*.databases.neo4j.io) on Azure, AuraDB Business Critical (*.databases.neo4j.io) on GCP), and AuraDB Free (*.databases.neo4j.io).