Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Apr 7, 2026

  1. GitHubActions is experiencing degraded availability

    On March 5, between 22:39 and 23:55 UTC, Actions was degraded due to a repeat of an incident a few hours prior. In this case, a Redis cluster topology change made as a follow-up to the earlier incident caused a repeat of the earlier degradation of Actions jobs. Details of both incidents and the follow-ups are shared at https://www.githubstatus.com/incidents/g5gnt5l5hf56.

    Resolved

  2. KinstaService disruption at the Sydney (AU) data center

    Our Engineers have successfully restored full service to all affected sites in the Sydney (AU) data center. If you are still seeing issues with your website please contact our support team. Thank you for your patience and we do apologize for any disruption to your business.

    Resolved

  3. BufferIssue Publishing Image Posts to Instagram and Threads

    Publishing success rates for both Instagram and Threads have returned to normal over the past few hours. The issues affecting both channels appear to have been intermittent and have now been resolved. We’re closing this incident. If you have any failed posts, using Retry Now should get them sent out. We apologize for any inconvenience caused. If you continue to experience any issues, please let us know.

    Resolved

  4. ZapierIntermittent agent execution failures

    This issue has been resolved, and agent executions are operating normally. Between April 6, 2026, at 22:12 UTC and 22:47 UTC, a dependency that powers Agents became unavailable due to internal load test traffic. Agents triggered during this window may have failed to execute and will not be automatically retried. Agents that run from a Zap have been replayed and succeeded as well. If an agent run failed during this window, re-run the agent (or trigger it again via its normal trigger mechanism). New executions should now succeed. We apologize for the disruption. If you’re still seeing the issue, please refresh and try again, or contact Support at https://zapier.com/app/get-help.

    Resolved

  5. ZapierDelayed or failed custom action requests

    The incident affecting some custom action steps has been resolved. Between 22:12 and 22:47 UTC on April 6, 2026, some customers experienced failed or delayed workflow executions when using custom actions. Systems are stable and we’ve successfully replayed impacted Zap runs. Thanks for your patience.

    Resolved

Apr 6, 2026

  1. ZapierFunctions not executing

    We've identified and resolved the root cause of the functions outage. The issue has been resolved and systems are operating normally. The team will continue to monitor performance and ensure full recovery across all impacted users.

    Resolved

  2. BrazeUS01 SDK errors

    Between 17:00 and 18:35 EST, Braze Engineers identified and resolved an issue causing intermittent SDK errors on the US01 cluster. As of 18:40 EST, services remain stable, and any failed SDK requests during the impact window were automatically retried.

    Resolved

  3. AssemblyAIPre-recorded STT requests that include Content Moderation failing

    Resolved – Content Safety Errors | April 6, 2026 Incident Window: 18:14 – 20:06 UTC Current Status: Resolved ✅ On April 6, 2026, during the incident window, customers using our Content Safety feature for Pre-recorded STT experienced errors for their requests. What happened: A configuration change inadvertently prevented our systems from processing Content Safety requests. This caused all Content Safety-enabled transcription jobs for Pre-recorded STT to fail during the affected period. Who was affected: Customers with the Content Safety feature enabled who submitted Pre-recorded STT requests between 18:14 and 20:06 UTC. What we did: Our team detected the issue and reverted the configuration change, fully restoring Content Safety functionality by 20:06 UTC. We sincerely apologize for the impact this had on your workflows. If you have any questions, please contact our team at support@assemblyai.com, and we'll be happy to assist.

    Resolved

  4. HubSpot"SSO Login Failure: Team Members Encounter 'portal_not_configured' Error on HubSpot Access"

    Between 02:32 PM (UTC -04:00) and 02:38 PM (UTC -04:00), all customers in all affected regions experienced issues with SSO Login. This was caused by a server impairment. As of 02:38 PM (UTC -04:00), our SSO Login are working properly and the incident has been fully resolved. HubSpot conducts a thorough review after each incident to understand the cause and prevent it from happening again. Learn more about HubSpot's commitment to reliability at www.HubSpot.com/reliability. The information on this page reflects our understanding of the incident and impact at the time of the update.

    Resolved

  5. SnowflakeINC0154408

    Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0154408](https://community.snowflake.com/s/article/INC0154408)

    Resolved

  6. GitHubDisruption with some GitHub services

    Between 15:20 and 20:18 UTC on Thursday April 2, Copilot Cloud Agent entered a period of reduced performance. Due to an internal feature being developed for Copilot Code Review, the Copilot Cloud Agent infrastructure started to receive an increased number of jobs. This load eventually caused us to hit an internal rate limit, causing all work to suspend for an hour. During this hour, some new jobs would time out, while others would resume once rate limiting ended. Roughly 40% of jobs in this period were affected.<br /><br />Once the cause of this rate limiting was identified, we were able to disable the new CCR feature via a feature flag. Once the jobs that were already in the queue were able to clear, we didn't see additional instances of rate limiting afterwards.

    Resolved

  7. SanityElevated API Error Rates

    Between 14:14 UTC and 14:20 UTC, we observed elevated error rates on our API for some customers. The issue has since been resolved and all systems are operating normally.

    Resolved

  8. SparkPostIncreased bounce or delay rate for Apple domains

    Delivery rates to Apple domains have returned to normal with no further elevated delays or bounces. We will perform any necessary post-incident cleanup of suppression lists to ensure no recipients were incorrectly suppressed during the outage. NOTE: As of Monday April 5th at 9PM EDT the cleanup has been completed. All recipient addresses to Apple or Apple Private Relay domains that were suppressed during Apple's incident window were removed.

    Resolved

  9. NetlifyAgent Runners Outage

    Between 08:50 UTC and 09:41 UTC, Agent Runner experienced an outage caused by an issue with a third-party dependency. Customers may have experienced failures or degraded performance when running agents during this period. The issue has been resolved.

    Resolved

Apr 5, 2026

Apr 4, 2026

Older incidents