Partial Service Disruption
June 17, 2026 17:53 JST
June 17, 2026 08:53 UTC
INVESTIGATING
Currently, some labeled metrics without the service.name attribute may not be displayed. We are investigating the cause and working on a resolution. We apologize for the inconvenience.June 17, 2026 19:56 JST
June 17, 2026 10:56 UTC
IDENTIFIED
[Update] Regarding the issue where some labeled metrics without the service.name attribute are not displayed, we have identified the cause, and recovery work is currently in progress. If you configure this attribute, you can avoid the impact of this issue. We will provide the next update on 6/18 around 11:00 (JST). We apologize for the inconvenience and appreciate your patience.June 18, 2026 11:04 JST
June 18, 2026 02:04 UTC
IDENTIFIED
[Update] Regarding the issue where some labeled metrics without the service.name attribute are not displayed, recovery is currently ongoing. Additionally, we have confirmed that query monitoring referencing these metrics does not work properly. If you configure this attribute, it will allow you to avoid the impact on both metrics and monitoring. We will provide the next update on 6/18 around 13:00 (JST). We apologize for the inconvenience and appreciate your patience.June 18, 2026 12:33 JST
June 18, 2026 03:33 UTC
IDENTIFIED
[Update] The fix is complete for the issue with labeled metrics without service.name. Newly posted metrics and query monitoring are now functioning correctly. However, metrics posted during the outage remain unavailable. Recovery is ongoing. We will provide the next progress by around 15:00 (JST) on June 18. We apologize for the inconvenience.June 18, 2026 15:04 JST
June 18, 2026 06:04 UTC
IDENTIFIED
[Update] Regarding the issue with labeled metrics without the service.name attribute, the system fix has been completed. Newly posted metrics are working correctly for both display and query monitoring. Meanwhile, recovery work to restore visibility for the affected metrics posted during the outage period remains in progress. We will provide the next progress by around 17:00 (JST) on June 18. We apologize for the inconvenience and appreciate your continued patience.June 18, 2026 17:11 JST
June 18, 2026 08:11 UTC
IDENTIFIED
[Update] Regarding the issue with labeled metrics without the service.name attribute, data recovery for the affected metrics posted during the outage period is currently in progress. We will provide the next progress by around 11:00 (JST) on June 19 at the latest. We apologize for the continued inconvenience and appreciate your patience.June 19, 2026 11:10 JST
June 19, 2026 02:10 UTC
IDENTIFIED
[Update] Regarding the issue with labeled metrics without the service.name attribute, we are currently working on data recovery for the affected metrics posted during the outage period. After reviewing the recovery procedures, we have determined that the process will take some time, and completion is scheduled for next week. Our next update will be around 15:00 (JST) on Monday, June 22. However, if any significant progress is made or notable events occur before then, we will inform you immediately. We apologize for the inconvenience and appreciate your continued patience.June 22, 2026 14:56 JST
June 22, 2026 05:56 UTC
IDENTIFIED
[Update] Regarding the issue with labeled metrics without the service.name attribute, we are currently working on data recovery for the affected metrics posted during the outage period. We have determined that the process will take some more time before completion. Our next update will be around 15:00 (JST) on Tuesday, June 23. However, if any significant progress is made or important matters to share arise before then, we will inform you immediately. We apologize for the inconvenience and appreciate your continued patience.June 23, 2026 15:00 JST
June 23, 2026 06:00 UTC
RESOLVED
From 11:24 on April 6 to 12:08 on June 23, 2026 (JST), an issue occurred where some labeled metrics without service.name were not displayed, and their query monitoring didn't work properly. All fixes and data recovery are now complete, and the system is operating normally. We sincerely apologize for the long-standing inconvenience.
