HashiCorpGitHub sign-ins unavailable
GitHub has resolved their incident and we can confirm users are able to sign in using their service.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
GitHub has resolved their incident and we can confirm users are able to sign in using their service.
Resolved
This incident has been resolved.
Resolved
Multilingual transcription has been re-enabled. Service fully restored.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
On 2/7/2026 at approximately 11:00 UTC, the Apple blocks appear to have abruptly stopped, and have not recurred since, though we are carefully monitoring. We are continuing to follow up with Apple about this to determine the root cause of the issue and ensure it will not happen again.
Resolved
GitHub have closed their Actions incident.
Resolved
Sign in errors reported for GitHub.com have cleared and been resolved.
Resolved
This incident has been resolved.
Resolved
Standard and Basic clusters continue to function normally.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We are no longer seeing high error rates for this model.
Resolved
This incident has been resolved.
Resolved
Issue is fixed and instances are up and running.
Resolved
We have successfully resolved the high error ratio affecting Lovable cloud project creation. The issue began at approximately 10:12 UTC and was fully resolved by 10:28 UTC on February 9, 2026. We sincerely apologize for the disruption this caused. Thank you for your patience and understanding as we worked to resolve this issue. If you experienced any failed project creation attempts during this window, please feel free to retry them now—they should complete successfully.
Resolved
Runs, traces and events data are all caught up from their temporary backlog. The dashboard metrics are all being processed with no backlog.
Resolved
Logs appear to be working normally again.
Resolved
An API key had expired and has been rotated. EVI appears functional again.
Resolved
This incident has been resolved.
Resolved
This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour
Resolved
This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour
Resolved
This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour
Resolved
We have identified all indices which are half complete and ran manual updates to repair them.
Resolved
The service is still healthy and this incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Status: Resolved / Post-Recovery Validation Impact: Services Restored JFrog services are now fully operational following the resolution of a significant upstream infrastructure outage within Azure. Our internal automated monitoring confirms that all our core functionalities have returned to expected performance levels. Recovery & Ongoing Validation While primary connectivity and service layers have been restored, the JFrog engineering team remains in an active monitoring phase. We are currently performing comprehensive validations across all Azure services including storage and compute components. This process ensures that all dependent systems have achieved full synchronization and are performing at optimal capacity. Incident Timeline (UTC) 12:30 UTC: The infrastructure provider confirmed the restoration of facility power and physical network connectivity. Subsequent Window: Azure Cloud services were recovered, enabling the sequential restoration and stabilization of the JFrog service layers. For further technical details regarding the root cause of the underlying infrastructure failure, please refer to the official Azure Status Page - https://azure.status.microsoft/en-us/status
Resolved
This incident has been resolved.
Resolved
After a period of monitoring, we can confirm that the issue affecting AliPay payments has been fully resolved, and the payment method is successfully processing for all buyers. Between 12.40pm and 01.57pm GMT on 6 Feb, we experienced an issue that prevented buyers from completing payments using AliPay. During the incident, this payment method was unavailable at checkout or resulted in errors for attempted transactions. Normal service was restored once the issue was resolved. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at sellers@paddle.com "sellers@paddle.com": mailto:sellers@paddle.com.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved. Thank you for your patience.
Resolved
All impacted services have now fully recovered.
Resolved
This incident has been resolved.
Resolved
On February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
From Jan 31, 2026 00:30 UTC to Feb 2, 2026 18:00 UTC Dependabot service was degraded and failed to create 10% of Automated Pull Requests. This was due to a cluster failover that connected to a read-only database.<br /><br />We mitigated the incident by pausing Dependabot queues until traffic was properly routed to healthy clusters. We’re working on identifying and rerunning all failed jobs during this time.<br /><br />We’re adding new monitors and alerts to reduce our time to detection and prevent this in the future.
Resolved