2 posts tagged with "incident"

ConfigCat is NOT affected​

A remote code execution flaw was recently discovered in log4j. The vulnerability is fixed in log4j 2.15.0.

Between 28th and 30th September, our customers experienced long response times, timeouts, and failing responses from the ConfigCat CDN. Since this was a significant disruption in the ConfigCat service, we want to be upfront about it and share all the information about what happened, what we've done, and what changes we will implement.