Incidents reported on status page for Interfere https://status.interfere.com/ https://d1lppblt9t2x15.cloudfront.net/logos/93e138d4cc8999a87877415367e5a037.png https://status.interfere.com/ en https://status.interfere.com/incident/871058 Tue, 14 Apr 2026 04:01:00 -0000 https://status.interfere.com/incident/871058#79d029d301e9aaaf8c4a70b639a5f2d6c644978591e31095d96f22f02e987fc7 Partial degradation for events ingestion https://status.interfere.com/incident/869505 Sat, 11 Apr 2026 14:30:00 -0000 https://status.interfere.com/incident/869505#9633d5d99fd720b26d74e338ad5cee33df74dbe0894c0185acd80ee9021e4177 Maintenance completed https://status.interfere.com/incident/869505 Sat, 11 Apr 2026 13:30:00 -0000 https://status.interfere.com/incident/869505#fe5cb99c12dd3b5569c6e4b630c66557109975632f369beb57649dd4a47e7207 We're currently hardening our alerting and telemetry systems, and any notices of downtime or system outages that might occur during this window are incorrect and can safely be ignored. Thank you! https://status.interfere.com/incident/850634 Mon, 16 Mar 2026 18:16:00 -0000 https://status.interfere.com/incident/850634#2604fef2f110ba804897189d067670cd414df3009998eb74ed2119bc16be5a7a Due to an issue in which client-side events were unable to be ingested by our system, a thundering herd issue occurred as a result of aggressive client-side retry policies. We have both fixed the underlying issue as well as hardened our client SDK in `@interfere/next` v4.0.0, and improved our alerting and rollback systems to be more resilient to potential failures like this in the future. https://status.interfere.com/incident/850634 Mon, 16 Mar 2026 18:05:00 -0000 https://status.interfere.com/incident/850634#e198e334c1a335950fe94c003af514248126f0c20cf0ac12c2280cce8f4712f8 An issue with our ingestion pipeline has been identified. We're on it.