Incidents reported on status page for Hyperline https://status.hyperline.co/ https://d1lppblt9t2x15.cloudfront.net/logos/c4abf027516b82ff89092d2470221ee2.png https://status.hyperline.co/ en https://status.hyperline.co/incident/907144 Thu, 28 May 2026 10:01:00 -0000 https://status.hyperline.co/incident/907144#9f3c3f38475546f62e0e845522bf2858d78d29a4a9976e0f0633253072953912 The fix has been rolled out and the app should be back to normal. The team continues to monitor the systems. https://status.hyperline.co/incident/907144 Thu, 28 May 2026 09:39:00 -0000 https://status.hyperline.co/incident/907144#bce8c0664821058b6fa856489f9751f54f52b8bf3184312f4a8e67f50ab490b6 We have identified a potential cause and are currently rolling out mitigation changes https://status.hyperline.co/incident/907144 Thu, 28 May 2026 09:03:00 -0000 https://status.hyperline.co/incident/907144#243ee307ed56a456795c26e541c806b2729cbc3640f8ff4f544590e47464c888 We are currently investigating an incident impacting app latency. The UI is partially unavailable for some customers. API and event ingestion is not impacted. Our teams are actively working to identify the root cause. https://status.hyperline.co/ Wed, 29 Apr 2026 17:01:29 +0000 https://status.hyperline.co/#abf352a0cbca55386c0f674d7d686f6fe961a69a5874d1e8a471eec75483a7b1 App recovered https://status.hyperline.co/ Wed, 29 Apr 2026 16:58:39 +0000 https://status.hyperline.co/#abf352a0cbca55386c0f674d7d686f6fe961a69a5874d1e8a471eec75483a7b1 App went down https://status.hyperline.co/ Tue, 28 Apr 2026 14:28:37 +0000 https://status.hyperline.co/#f905329baa72a39282f31da0d1fcfd05d4cc6f3433426e3115ce7e0e7eaaa7d0 App recovered https://status.hyperline.co/ Tue, 28 Apr 2026 14:25:29 +0000 https://status.hyperline.co/#f905329baa72a39282f31da0d1fcfd05d4cc6f3433426e3115ce7e0e7eaaa7d0 App went down https://status.hyperline.co/ Mon, 27 Apr 2026 11:19:15 +0000 https://status.hyperline.co/#cdea4a6c6749dcd6b11679b8a26290a52f245c6ed9e525e620c5dfe9b252dd76 Ingest API recovered https://status.hyperline.co/ Mon, 27 Apr 2026 11:16:35 +0000 https://status.hyperline.co/#cdea4a6c6749dcd6b11679b8a26290a52f245c6ed9e525e620c5dfe9b252dd76 Ingest API went down https://status.hyperline.co/ Mon, 27 Apr 2026 11:12:01 +0000 https://status.hyperline.co/#6006da59f9d49d280f3e9dd9f9d1feb0639614dcc90dc90fc5deafd0bd8b26a5 API recovered https://status.hyperline.co/ Mon, 27 Apr 2026 11:06:37 +0000 https://status.hyperline.co/#6006da59f9d49d280f3e9dd9f9d1feb0639614dcc90dc90fc5deafd0bd8b26a5 API went down https://status.hyperline.co/incident/862630 Wed, 01 Apr 2026 16:29:00 -0000 https://status.hyperline.co/incident/862630#214ae4a436183161ec6be65f198cb0d88e9026231e5022d1b10c0265c039720c The issue has been identified and is now fully resolved. We are implementing the necessary actions and guardrails to prevent this from happening again. https://status.hyperline.co/incident/862630 Wed, 01 Apr 2026 15:54:00 -0000 https://status.hyperline.co/incident/862630#25c71625567f7be1e8ae7491b8d472a618302f85ec57b0ab78fe631ed42ced5b We experienced increased API latency, caused by unexpected usage of a specific API endpoint https://status.hyperline.co/ Mon, 30 Mar 2026 17:40:43 +0000 https://status.hyperline.co/#d3626fb59554959c833665b58d3d8e2fec854e72c3cb714ed174b99265070384 Ingest API recovered https://status.hyperline.co/ Mon, 30 Mar 2026 17:37:42 +0000 https://status.hyperline.co/#d3626fb59554959c833665b58d3d8e2fec854e72c3cb714ed174b99265070384 Ingest API went down https://status.hyperline.co/ Mon, 30 Mar 2026 16:01:36 +0000 https://status.hyperline.co/#25910c241cc5484e1b6559f5a53c784ed27bc130c65c70ea5ddc0eb7f08f0018 Ingest API recovered https://status.hyperline.co/ Mon, 30 Mar 2026 15:58:42 +0000 https://status.hyperline.co/#25910c241cc5484e1b6559f5a53c784ed27bc130c65c70ea5ddc0eb7f08f0018 Ingest API went down https://status.hyperline.co/ Fri, 27 Mar 2026 12:10:49 +0000 https://status.hyperline.co/#48e2e94bfa8a4de06e0418a107d17e9ae84966bb99028293ea9e1412e009cb0c App recovered https://status.hyperline.co/ Fri, 27 Mar 2026 12:07:47 +0000 https://status.hyperline.co/#48e2e94bfa8a4de06e0418a107d17e9ae84966bb99028293ea9e1412e009cb0c App went down https://status.hyperline.co/incident/793489 Wed, 24 Dec 2025 11:06:00 -0000 https://status.hyperline.co/incident/793489#912f2bd0c469dee41fc154a8e1a52bfc808233ef35f1349be3fc7ae68e0eaa5d All missing events from the API ingestion calls have been fully recovered and processed in Hyperline. All services are back to normal, and data is fully up to date. https://status.hyperline.co/incident/793489 Wed, 24 Dec 2025 09:37:00 -0000 https://status.hyperline.co/incident/793489#a08d31a31bab6cc96391a83842b41e8e6d85a4acd6ca6b07b09d61d078d55eeb We have identified the events from the API ingestion calls that were not successful during the incident. This issue impacted a very small number of customers. Hyperline will replay the affected events to ensure usage is processed correctly. No action is required on your side, and usage should be reflected as expected once the replay is completed. Our team is actively working on the replay process and will continue monitoring until the situation is fully resolved. We will provide another update once the replay is complete. https://status.hyperline.co/incident/793489 Wed, 24 Dec 2025 07:50:00 -0000 https://status.hyperline.co/incident/793489#a672551aaf641e52e183d89cb1f8dc791d06ce182ac76b30d5d63c28f628f87b We have identified the cause of the incident as unexpectedly large event ingestion volumes, which impacted some customers. Core services have been restored and are back to normal operation. We are continuing to monitor closely to ensure stability. Event ingestion status: - Events ingested via dataloaders have been processed normally. - Events sent through the API have not been ingested during this period. We are actively investigating recovery options and determining how to safely reprocess or restore the impacted API events. https://status.hyperline.co/incident/793489 Wed, 24 Dec 2025 02:01:00 -0000 https://status.hyperline.co/incident/793489#a2efc9cd31119206f777155e0be9b70d1e3f720305d10100123017d8eeb0f46a We are currently investigating an incident impacting service availability. The UI is partially unavailable for some customers, and API event ingestion is currently unavailable. Our teams are actively working to identify the root cause and restore normal operations. We will provide an update as soon as more information becomes available. https://status.hyperline.co/incident/746997 Tue, 21 Oct 2025 06:43:00 -0000 https://status.hyperline.co/incident/746997#cfc643a706c4e186d4f86cf05b0f74390a90787dcdd34e28587c65c8dde6cd3f All systems are back to normal https://status.hyperline.co/incident/746997 Mon, 20 Oct 2025 09:58:00 -0000 https://status.hyperline.co/incident/746997#db1668df792b6172d4c036b87e5732a970172f6d32c6d2dbc7271a5cb7987f3b Traffic and usage on Hyperline have now largely returned to normal. The CRM widget may still experience degraded service. https://status.hyperline.co/incident/746997 Mon, 20 Oct 2025 09:32:00 -0000 https://status.hyperline.co/incident/746997#a657197ad54d739024031d582b5bc335a9fcacccc024344b9dd97b88d902e951 This incident was caused by ongoing issues in the AWS us-east-1 data center, which affected some of our dependent tools. Upstream incident: https://health.aws.amazon.com/health/status https://status.hyperline.co/incident/746997 Mon, 20 Oct 2025 07:15:00 -0000 https://status.hyperline.co/incident/746997#82bdba585c149e0b5ee21d8c4c506e15d43e32e0df062b85e2ca237092e96027 AWS is experiencing a major outage. Hyperline services are partially impacted, which may cause the app or CRM widget to fail to load, or lead to API timeouts. We are monitoring the situation closely. https://status.hyperline.co/incident/735752 Wed, 01 Oct 2025 13:35:00 -0000 https://status.hyperline.co/incident/735752#42bf25efc92c8793d8cb65dada2eaa6a8e8aaaed03cacf0940ba0daae2adda20 The fix has been rolled out and services are back to normal. The team continues to monitor the systems. https://status.hyperline.co/incident/735752 Wed, 01 Oct 2025 13:03:00 -0000 https://status.hyperline.co/incident/735752#67cf22742398eb6a39906ca18e6215f83e4d8b7177d2a9c63eee39f2e19ab090 The problem has been identified by the engineering team. A remediation related to data storage has been planned and is currently being rolled out. https://status.hyperline.co/incident/735752 Wed, 01 Oct 2025 12:38:00 -0000 https://status.hyperline.co/incident/735752#ff27520411734c1ee6839801867641f027773547685e25da3710504ffb2b3251 Some customers may experience degraded performance when accessing the product or using the API.