Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

May 14, 2024

May 13, 2024

  1. NeonRestrictive limits applied to database connections

    The incident has been successfully resolved, and normal operations have been restored to all affected systems and services. Our team conducted a thorough investigation, implemented necessary actions, and analyzed the underlying cause to prevent similar incidents in the future.

    Resolved

May 10, 2024

  1. FigmaService disruption

    Figma observed delays with notifications from 11:00am PT to 11:45am PT. This incident has been resolved.

    Resolved

May 9, 2024

May 6, 2024

  1. HotjarHotjar.com outage

    From approximately 10:20 to 10:40 am CET, the Hotjar.com website and careers pages were inaccessible. This issue has been resolved, thanks for bearing with us!

    Resolved

May 3, 2024

May 1, 2024

  1. NeonConsole degradation

    The incident has been successfully resolved, and normal operations have been restored to all affected systems and services. Our team conducted a thorough investigation, implemented necessary actions, and analyzed the underlying cause to prevent similar incidents in the future.

    Resolved

Apr 30, 2024

Apr 29, 2024

  1. StreamHigh error rate on Chat API endpoints

    At 21:02 CET, a high error rate was recorded on the Chat API endpoints in one of our us-east shards. Our team resolved the issue at 21:18 CET, and the service is now operating normally.

    Resolved

  2. MailChannelsHigh SMTP Connection Latency

    The postmortem is posted here - [https://blog.mailchannels.com/mailchannels-service-disruption-all-the-gory-details/](https://blog.mailchannels.com/mailchannels-service-disruption-all-the-gory-details/)

    Resolved

Apr 25, 2024

Apr 23, 2024

Apr 22, 2024

  1. PusherSSL certificate renewal for our legacy telemetry endpoint

    The SSL certificate for our client stats endpoint expired at 00:00 UTC, but the issue was resolved at 8:49 AM UTC. During this period, clients who opted to send client stats using older versions of the JavaScript SDK for web (PusherJS) encountered some errors and were unable to send telemetry data to our servers. This does not impact any functionalities of our SDK, even in older versions. However, it's worth mentioning that we are unable to verify this on much older versions of our SDKs, as our team no longer monitors them. We have replaced the certificate on this endpoint with an auto-renewable certificate to prevent this issue from happening. The client stats endpoint is a legacy endpoint and is not being used in newer versions of our SDKs.

    Resolved

Apr 21, 2024

Apr 18, 2024

Apr 17, 2024

Apr 16, 2024

  1. CodecovDegraded Performance

    Intermittent 50X errors. We have mitigated the issue and are continuing to monitor.

    Resolved

  2. NeonConsole UI unavailable for 15m

    The incident has been successfully resolved, and normal operations have been restored to all affected systems and services. Our team conducted a thorough investigation, implemented necessary actions, and analyzed the underlying cause to prevent similar incidents in the future.

    Resolved

  3. LaunchDarkly FederalElevated SDK connection errors

    From 10:16 to 10:23 PT on Apr 16 our service experienced an elevated level of API errors in responding to new SDK requests. Existing streaming connections were not impacted. The issue is resolved and the service is operating normally.

    Resolved

Apr 15, 2024

Apr 12, 2024

  1. TypeformTypeform Embeds - Embedded typeforms are not loading

    We are glad to inform you that the fix has been implemented and the incident resolved. We will run a problem investigation to understand what happened and how to prevent it from happening again. Thanks for your understanding & sorry for any inconvenience this has caused.

    Resolved

Apr 11, 2024

  1. KeeperLogin errors - Resolved

    The issue has been resolved. An underlying AWS database error resulted in a failover event which was handled successfully after a few minutes. We are working with the AWS team to identify the root cause.

    Resolved

Apr 10, 2024

Older incidents