Incidents reported on status page for Stellate https://status.stellate.co/ https://d1lppblt9t2x15.cloudfront.net/logos/f549fb43982dced37cd1ec820ea134b7.png https://status.stellate.co/ en https://status.stellate.co/incident/829568 Tue, 24 Feb 2026 22:31:00 -0000 https://status.stellate.co/incident/829568#f7c4f195580ca33d56e63e7a8ed5acda64cad02b99521a91a2fb1ee8c9951813 Our edge provider also rolling out additional updates to infra that should fix any issues left. If you see any issues please reach out to us. https://status.stellate.co/incident/829568 Tue, 24 Feb 2026 22:31:00 -0000 https://status.stellate.co/incident/829568#f7c4f195580ca33d56e63e7a8ed5acda64cad02b99521a91a2fb1ee8c9951813 Our edge provider also rolling out additional updates to infra that should fix any issues left. If you see any issues please reach out to us. https://status.stellate.co/incident/829568 Tue, 24 Feb 2026 22:31:00 -0000 https://status.stellate.co/incident/829568#f7c4f195580ca33d56e63e7a8ed5acda64cad02b99521a91a2fb1ee8c9951813 Our edge provider also rolling out additional updates to infra that should fix any issues left. If you see any issues please reach out to us. https://status.stellate.co/incident/829568 Tue, 24 Feb 2026 15:32:00 -0000 https://status.stellate.co/incident/829568#5287011442841d696c9cc784b46889bae44038d8150da4385f37c526cbadc2cd Mitigation deployed for garbled responses issue We have deployed a mitigation for the issue where some GraphQL responses were previously returned as garbled (compressed/binary) data. The mitigation decodes gzip-encoded responses at the edge if necessary, ensuring that clients consistently receive valid JSON GraphQL responses. Initial testing with multiple repeated requests confirms that all responses are now correctly parsed and no garbled responses are observed. https://status.stellate.co/incident/829568 Tue, 24 Feb 2026 15:32:00 -0000 https://status.stellate.co/incident/829568#5287011442841d696c9cc784b46889bae44038d8150da4385f37c526cbadc2cd Mitigation deployed for garbled responses issue We have deployed a mitigation for the issue where some GraphQL responses were previously returned as garbled (compressed/binary) data. The mitigation decodes gzip-encoded responses at the edge if necessary, ensuring that clients consistently receive valid JSON GraphQL responses. Initial testing with multiple repeated requests confirms that all responses are now correctly parsed and no garbled responses are observed. https://status.stellate.co/incident/829568 Tue, 24 Feb 2026 15:32:00 -0000 https://status.stellate.co/incident/829568#5287011442841d696c9cc784b46889bae44038d8150da4385f37c526cbadc2cd Mitigation deployed for garbled responses issue We have deployed a mitigation for the issue where some GraphQL responses were previously returned as garbled (compressed/binary) data. The mitigation decodes gzip-encoded responses at the edge if necessary, ensuring that clients consistently receive valid JSON GraphQL responses. Initial testing with multiple repeated requests confirms that all responses are now correctly parsed and no garbled responses are observed. https://status.stellate.co/incident/829568 Tue, 24 Feb 2026 12:51:00 -0000 https://status.stellate.co/incident/829568#cce08624bc5d2b660b9d67ac6bc1c3ed353d5e1e0f084c15e67261e0fc13610c We have continued investigating this issue together with our infrastructure partners and have been able to further narrow down the root cause. The issue is related to intermittent inconsistencies in how compressed responses are handled at the edge. In affected cases, responses may be delivered in a compressed format (e.g. gzip) without the appropriate Content-Encoding header, or may undergo unintended transformations that corrupt the compressed payload. This results in garbled or unreadable responses in the browser. While initial findings suggested a possible correlation with Cloudflare proxying, we have since observed similar behavior in scenarios where Cloudflare is not involved. This indicates the issue may occur across multiple layers of the delivery path, and we are continuing to work closely with partners including Fastly to isolate and resolve it. The overall error rate remains low (a small percentage of requests), but we understand the impact of these intermittent failures and are treating this with high priority. We are actively working on mitigation strategies and will provide another update as soon as we have confirmed improvements or a full resolution. https://status.stellate.co/incident/829568 Tue, 24 Feb 2026 12:51:00 -0000 https://status.stellate.co/incident/829568#cce08624bc5d2b660b9d67ac6bc1c3ed353d5e1e0f084c15e67261e0fc13610c We have continued investigating this issue together with our infrastructure partners and have been able to further narrow down the root cause. The issue is related to intermittent inconsistencies in how compressed responses are handled at the edge. In affected cases, responses may be delivered in a compressed format (e.g. gzip) without the appropriate Content-Encoding header, or may undergo unintended transformations that corrupt the compressed payload. This results in garbled or unreadable responses in the browser. While initial findings suggested a possible correlation with Cloudflare proxying, we have since observed similar behavior in scenarios where Cloudflare is not involved. This indicates the issue may occur across multiple layers of the delivery path, and we are continuing to work closely with partners including Fastly to isolate and resolve it. The overall error rate remains low (a small percentage of requests), but we understand the impact of these intermittent failures and are treating this with high priority. We are actively working on mitigation strategies and will provide another update as soon as we have confirmed improvements or a full resolution. https://status.stellate.co/incident/829568 Tue, 24 Feb 2026 12:51:00 -0000 https://status.stellate.co/incident/829568#cce08624bc5d2b660b9d67ac6bc1c3ed353d5e1e0f084c15e67261e0fc13610c We have continued investigating this issue together with our infrastructure partners and have been able to further narrow down the root cause. The issue is related to intermittent inconsistencies in how compressed responses are handled at the edge. In affected cases, responses may be delivered in a compressed format (e.g. gzip) without the appropriate Content-Encoding header, or may undergo unintended transformations that corrupt the compressed payload. This results in garbled or unreadable responses in the browser. While initial findings suggested a possible correlation with Cloudflare proxying, we have since observed similar behavior in scenarios where Cloudflare is not involved. This indicates the issue may occur across multiple layers of the delivery path, and we are continuing to work closely with partners including Fastly to isolate and resolve it. The overall error rate remains low (a small percentage of requests), but we understand the impact of these intermittent failures and are treating this with high priority. We are actively working on mitigation strategies and will provide another update as soon as we have confirmed improvements or a full resolution. https://status.stellate.co/incident/829568 Mon, 23 Feb 2026 08:43:00 -0000 https://status.stellate.co/incident/829568#8eae9cb1d5a31fdb90ddb9f7ffad513c34428094e3fa677d374a3f079eeffd90 We are continuing to closely monitor the situation together with our infrastructure partners to ensure the issue is fully resolved and stable. At this point, the rate of garbled (compressed) responses has significantly decreased, but we are keeping the incident open until we are confident the behavior has fully subsided. We will provide another update once monitoring confirms full resolution. https://status.stellate.co/incident/829568 Mon, 23 Feb 2026 08:43:00 -0000 https://status.stellate.co/incident/829568#8eae9cb1d5a31fdb90ddb9f7ffad513c34428094e3fa677d374a3f079eeffd90 We are continuing to closely monitor the situation together with our infrastructure partners to ensure the issue is fully resolved and stable. At this point, the rate of garbled (compressed) responses has significantly decreased, but we are keeping the incident open until we are confident the behavior has fully subsided. We will provide another update once monitoring confirms full resolution. https://status.stellate.co/incident/829568 Mon, 23 Feb 2026 08:43:00 -0000 https://status.stellate.co/incident/829568#8eae9cb1d5a31fdb90ddb9f7ffad513c34428094e3fa677d374a3f079eeffd90 We are continuing to closely monitor the situation together with our infrastructure partners to ensure the issue is fully resolved and stable. At this point, the rate of garbled (compressed) responses has significantly decreased, but we are keeping the incident open until we are confident the behavior has fully subsided. We will provide another update once monitoring confirms full resolution. https://status.stellate.co/incident/829568 Sun, 22 Feb 2026 09:33:00 -0000 https://status.stellate.co/incident/829568#5aa56a68b44c63e6ce0ff7ea71bd4583ccad8bb2853c86c8f150fc6896e675a3 **Investigating** We are currently investigating an issue where a small percentage of requests may return garbled (compressed) responses. Our analysis indicates this may occur when traffic is proxied through Cloudflare. We are in contact with the provider and awaiting further clarification to ensure a stable resolution. As a temporary workaround, users can switch their DNS records to **DNS only** (disable Cloudflare proxying), which appears to mitigate the issue. We will provide further updates as soon as more information becomes available. https://status.stellate.co/incident/829568 Sun, 22 Feb 2026 09:33:00 -0000 https://status.stellate.co/incident/829568#5aa56a68b44c63e6ce0ff7ea71bd4583ccad8bb2853c86c8f150fc6896e675a3 **Investigating** We are currently investigating an issue where a small percentage of requests may return garbled (compressed) responses. Our analysis indicates this may occur when traffic is proxied through Cloudflare. We are in contact with the provider and awaiting further clarification to ensure a stable resolution. As a temporary workaround, users can switch their DNS records to **DNS only** (disable Cloudflare proxying), which appears to mitigate the issue. We will provide further updates as soon as more information becomes available. https://status.stellate.co/incident/829568 Sun, 22 Feb 2026 09:33:00 -0000 https://status.stellate.co/incident/829568#5aa56a68b44c63e6ce0ff7ea71bd4583ccad8bb2853c86c8f150fc6896e675a3 **Investigating** We are currently investigating an issue where a small percentage of requests may return garbled (compressed) responses. Our analysis indicates this may occur when traffic is proxied through Cloudflare. We are in contact with the provider and awaiting further clarification to ensure a stable resolution. As a temporary workaround, users can switch their DNS records to **DNS only** (disable Cloudflare proxying), which appears to mitigate the issue. We will provide further updates as soon as more information becomes available. https://status.stellate.co/incident/829568 Fri, 20 Feb 2026 15:10:00 -0000 https://status.stellate.co/incident/829568#e2fb3740a5013ccdf734f630fac7ada862de2a42f0ac61acf594f1d2d81fdc2b Our internal caching service is partially impacted, causing some requests (including those to the Dashboard) to experience delayed or incorrectly compressed responses. https://status.stellate.co/incident/829568 Fri, 20 Feb 2026 15:10:00 -0000 https://status.stellate.co/incident/829568#e2fb3740a5013ccdf734f630fac7ada862de2a42f0ac61acf594f1d2d81fdc2b Our internal caching service is partially impacted, causing some requests (including those to the Dashboard) to experience delayed or incorrectly compressed responses. https://status.stellate.co/incident/829568 Fri, 20 Feb 2026 15:10:00 -0000 https://status.stellate.co/incident/829568#e2fb3740a5013ccdf734f630fac7ada862de2a42f0ac61acf594f1d2d81fdc2b Our internal caching service is partially impacted, causing some requests (including those to the Dashboard) to experience delayed or incorrectly compressed responses. https://status.stellate.co/incident/783683 Sun, 14 Dec 2025 09:39:33 -0000 https://status.stellate.co/incident/783683#1385b2459e2ba6c2cf9f25f490cb844ebbe8261e5f75af96b4ba3e4182b842e6 Maintenance completed https://status.stellate.co/incident/783683 Sun, 14 Dec 2025 09:39:33 -0000 https://status.stellate.co/incident/783683#1385b2459e2ba6c2cf9f25f490cb844ebbe8261e5f75af96b4ba3e4182b842e6 Maintenance completed https://status.stellate.co/incident/783683 Sun, 14 Dec 2025 09:39:33 -0000 https://status.stellate.co/incident/783683#1385b2459e2ba6c2cf9f25f490cb844ebbe8261e5f75af96b4ba3e4182b842e6 Maintenance completed https://status.stellate.co/incident/783683 Sun, 14 Dec 2025 09:39:33 -0000 https://status.stellate.co/incident/783683#1385b2459e2ba6c2cf9f25f490cb844ebbe8261e5f75af96b4ba3e4182b842e6 Maintenance completed https://status.stellate.co/incident/783683 Sun, 14 Dec 2025 09:00:44 -0000 https://status.stellate.co/incident/783683#b09e406e2db9d84466436adb6a1d54af4435306590813ae466afc6a84cb337de We will perform scheduled maintenance on our Aiven Kafka cluster to apply recommended connector and security updates. A brief service interruption may occur. No impact beyond a short interruption is expected. https://status.stellate.co/incident/783683 Sun, 14 Dec 2025 09:00:44 -0000 https://status.stellate.co/incident/783683#b09e406e2db9d84466436adb6a1d54af4435306590813ae466afc6a84cb337de We will perform scheduled maintenance on our Aiven Kafka cluster to apply recommended connector and security updates. A brief service interruption may occur. No impact beyond a short interruption is expected. https://status.stellate.co/incident/783683 Sun, 14 Dec 2025 09:00:44 -0000 https://status.stellate.co/incident/783683#b09e406e2db9d84466436adb6a1d54af4435306590813ae466afc6a84cb337de We will perform scheduled maintenance on our Aiven Kafka cluster to apply recommended connector and security updates. A brief service interruption may occur. No impact beyond a short interruption is expected. https://status.stellate.co/incident/783683 Sun, 14 Dec 2025 09:00:44 -0000 https://status.stellate.co/incident/783683#b09e406e2db9d84466436adb6a1d54af4435306590813ae466afc6a84cb337de We will perform scheduled maintenance on our Aiven Kafka cluster to apply recommended connector and security updates. A brief service interruption may occur. No impact beyond a short interruption is expected. https://status.stellate.co/incident/783683 Sun, 14 Dec 2025 09:00:44 -0000 https://status.stellate.co/incident/783683#b09e406e2db9d84466436adb6a1d54af4435306590813ae466afc6a84cb337de We will perform scheduled maintenance on our Aiven Kafka cluster to apply recommended connector and security updates. A brief service interruption may occur. No impact beyond a short interruption is expected. https://status.stellate.co/incident/783683 Sun, 14 Dec 2025 09:00:44 -0000 https://status.stellate.co/incident/783683#b09e406e2db9d84466436adb6a1d54af4435306590813ae466afc6a84cb337de We will perform scheduled maintenance on our Aiven Kafka cluster to apply recommended connector and security updates. A brief service interruption may occur. No impact beyond a short interruption is expected. https://status.stellate.co/incident/783683 Sun, 14 Dec 2025 09:00:44 -0000 https://status.stellate.co/incident/783683#b09e406e2db9d84466436adb6a1d54af4435306590813ae466afc6a84cb337de We will perform scheduled maintenance on our Aiven Kafka cluster to apply recommended connector and security updates. A brief service interruption may occur. No impact beyond a short interruption is expected. https://status.stellate.co/incident/783683 Sun, 14 Dec 2025 09:00:44 -0000 https://status.stellate.co/incident/783683#b09e406e2db9d84466436adb6a1d54af4435306590813ae466afc6a84cb337de We will perform scheduled maintenance on our Aiven Kafka cluster to apply recommended connector and security updates. A brief service interruption may occur. No impact beyond a short interruption is expected. https://status.stellate.co/incident/768888 Tue, 18 Nov 2025 12:20:00 -0000 https://status.stellate.co/incident/768888#89453585d3dc8b0166312385d41efe11352c4e2430f5736d96c5057afdf12859 https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 https://status.stellate.co/incident/762426 Wed, 12 Nov 2025 17:39:00 -0000 https://status.stellate.co/incident/762426#daa09c039f0c135efa899e9ef1703203546c216e86b49c030c78588b8575f4a6 We’ve monitored the system for several hours after applying the patch, and everything appears stable — the issue should now be resolved. https://status.stellate.co/incident/762426 Wed, 12 Nov 2025 11:35:00 -0000 https://status.stellate.co/incident/762426#356a663ad7fcf4ad1dadaa1b22842bdc0e011fa6da63a221ee89b8a489dae1fe We’ve applied the vendor patch to our infrastructure and are currently monitoring system stability and performance. https://status.stellate.co/incident/762426 Wed, 12 Nov 2025 00:24:00 -0000 https://status.stellate.co/incident/762426#08fdbaa3823d9dd1d131be5da87959a37acce8d5db2757891976013ded888607 Our vendor has identified an underlying issue in the Kafka infrastructure affecting SASL connections, and a fix has been released. We’re currently reviewing how to apply the patch and will proceed once confirmed. https://status.stellate.co/incident/762426 Mon, 10 Nov 2025 09:00:00 -0000 https://status.stellate.co/incident/762426#bb21df7ad44a6a624f3c5c1132091a839021bfd47a133b996ab69139eaeccf58 We’re currently experiencing connectivity issues between our Clickpipe instances and the Kafka cluster. This is causing backlogs in data processing, which may result in metrics appearing with delays on your dashboard. We are actively working with our Kafka vendor to identify and resolve the underlying network issue.