Follow-up report: Report on the Overcounting of Cloud Integration Metrics

We have been investigating the impact of the Overcounting of AWS integration metrics, which was announced in the following blog post, by expanding the scope to include all cloud integrations. We have completed the investigation and would like to inform you of the results. The scope of impact has been changed since the previous announcement.

We would like to inform you of the details of this issue and how we intend to respond to it.


In some hosts registered with cloud integration, numbers of metrics in excess of numbers that could actually be confirmed were counted. When this resulted in the upper limit of metrics per host (standard host: 200 metrics, microhost: 30 metrics) being exceeded, billings in excess of actual use may have occurred.

Time period of the issue

  • Since February 2019

Scope of impact

Hosts registered with the following cloud integrations:

  • AWS Integration WAF
  • AWS Integration Redshift
  • AWS Integration Step Functions
  • Google Cloud Integration Compute Engine
  • Google Cloud Integration App Engine

Current status

  • On April 11, 2022, we released a fundamental fix to prevent overcounting of metrics.
  • Investigation into the status of occurrence of similar issues in AWS Integration, Azure Integration, and Google Cloud integration has been completed.
  • Investigation into organizations affected by the issue has been completed for the entire period.

Root cause

  • When posting metrics with the cloud integrations noted in the scope of influence, some metrics were posted in duplicate and were counted in duplicate in the billing process.

Future actions

  • With sincere apologies for the inconvenience, billings for April 2022 usage (early May 2022) will incorporate the duplicated amounts.
  • Individual refunds will be made for organizations that were affected by the issue.
  • We will contact organizations individually regarding handling of the refunds.

We apologize sincerely for the inconvenience caused to users.

We will continue making efforts to further improve our quality of service, and ask for your continued patronage of Mackerel.