EntireDegraded GitHub API access affecting GitHub Mirroring
GitHub API errors have ceased. Repository mirroring has recovered.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
GitHub API errors have ceased. Repository mirroring has recovered.
Resolved
Builds failure rates have recovered. Resolving.
Resolved
GitHub API errors have subsided, and documentation updates are back to operating normally. If you continue to experience issues, please contact support@mintlify.com "support@mintlify.com": mailto:support@mintlify.com.
Resolved
EU payouts may have experienced some settlement delays. This is now resolved Impact start time: 19/07/2026, 23:02 BST Impact end time: 19/07/2026, 23:16 BST Client actions: None
Resolved
All impacted services have now fully recovered.
Resolved
This issue has been resolved and service is operating normally.
Resolved
Our Engineers have successfully restored full service to all affected sites in the Eemshaven (NL) 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
Our Engineering team has confirmed that the issue regarding volume attachment to Droplets in the NYC1, NYC3, SGP1, SYD1, and BLR1 regions has been fully resolved, and all services are now operating normally. If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.
Resolved
After a period of monitoring, we can confirm our mitigation was successful and site performance has returned to expected levels. This incident is now resolved. Some hosted pages with CMS content may have experienced intermittent 5xx errors during the following windows each lasting a few minutes (UTC): - 01:27–01:31 - 01:39–01:41 - 01:51–01:53 - 04:47–04:50 - 05:02–05:03 We appreciate your patience while we worked to investigate and resolve the issue.
Resolved
This incident has been resolved.
Resolved
This issue has been resolved, and new Threads comments should now be delivered normally. Our backup mechanism has also recovered recent comments that were delayed during the incident. We sincerely apologise for the disruption.
Resolved
Meta's Marketing API has recovered and Meta Ads data imports are succeeding normally again across US and EU. Failure rates are back to baseline. Any sources that failed during the incident will fully refresh on their next scheduled sync.
Resolved
This issue has now been fully resolved, and video posts to Instagram and Threads are publishing normally again. Any failed posts can be retried from the queue. Once again, we sincerely apologise for the disruption.
Resolved
Our engineering team has resolved the outbound network connectivity issue in the BLR1 region. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Resolved
We can confirm that the issues affecting Facebook and Instagram message and data delivery in Hootsuite have been resolved. If you continue to experience missing messages in Inbox or incomplete data in Analytics, please reach out to our customer support team.
Resolved
This incident has been resolved.
Resolved
Event ingestion has fully caught up and all delayed events have backfilled. Analytics data for EU Cloud projects is current again, and no data was lost.
Resolved
Scheduled Maintenance has been completed.
Resolved
This incident has been resolved.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
This incident has been resolved.
Resolved
EU Payouts experienced settlement delays. This is now resolved. Impact start time: 19/07/2026, 00:02 BST Impact end time: 19/07/2026, 00:14 BST Client actions: None
Resolved
Connection issues have been resolved. If you experience any further issues, please contact our support team.
Resolved
All impacted services have now fully recovered.
Resolved
Scheduled Maintenance has been completed
Resolved
All impacted services have now fully recovered.
Resolved
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/INC20000085](https://community.snowflake.com/s/article/INC20000085)
Resolved
Project actions have been sustained at normal performance. This incident is resolved.
Resolved
This incident has been resolved.
Resolved
Issue is resolved
Resolved
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/INC20000082](https://community.snowflake.com/s/article/INC20000082)
Resolved
All the statements should be running now.
Resolved
This incident has been resolved.
Resolved
We’ve published a [post-mortem on the July 16 service disruption](https://workos.com/blog/service-disruption-on-july-16-2026) to our blog, detailing what happened and how we’re strengthening the resiliency of WorkOS products.
Resolved
The issue has been resolved. All impacted systems are now operating normally. Event streams, data export integration, and journeys are all functioning normally now.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
Svix experienced elevated latency and a small number of errors in the US region between 19:45Z and 20:33Z due to a configuration change that enabled an experimental idempotency flow for an unexpectedly-large number of users. Approximately 12 requests saw 5XX errors during this period, and several thousand requests took longer than expected. This incident has been fully remediated.
Resolved
All impacted services have now fully recovered.
Resolved
This incident has been resolved.
Resolved
From 19:00–19:55 UTC on July 17, 2026, Issuing users did not receive real-time authorization request webhooks and experienced declined transactions. All systems have recovered and are operating normally.
Resolved