Fly.ioIncreased API latency
This incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has been resolved.
Resolved
The issue with opening files has been resolved, and services are operating normally. We’re sorry for any disruption this may have caused and thank you for your patience and understanding.
Resolved
Notification test
Resolved
Notification test
Resolved
From 02:25 - 03:24 UTC, we saw elevated card authorization errors related to an issuer-side degradation in Mexico. This is now resolved.
Resolved
On July 24th at 16:04 UTC, a loss of connectivity occurred in network paths in one of our three physical data center availability zones (AZs). This resulted in packet loss due to the remaining active paths becoming saturated. Our data centers use a leaf-spine switch fabric in each compute cage, and an aggregation layer interconnecting the spines from each cage within each AZ. The loss of connectivity affected links between one cage’s spine switches and the aggregation layer within that specific AZ. <br /><br />Workloads depending on compute resources in this cage became degraded due to packet loss, and exhibited intermittent errors: <br /><br />- Actions saw 10% of jobs fail during the impact window, and 5% of jobs succeeded but with delayed starts. <br />- 27% of GitHub issues interactions saw slow requests or timeouts. <br />- 4% of GitHub Copilot requests experienced errors, though most automatically retry. <br />- 4% of git push operations saw impacts during the affected window. <br />- Authentication requests saw increased latency during the affected window, but error rates, while elevated, were < 1% in all cases. <br /><br />We were able to mitigate the outage by re-routing affected connections to available fiber paths that were allocated for future capacity upgrades. Sufficient network capacity to eliminate packet loss was restored at 17:07, with most services showing full recovery by 17:16. All paths were restored and services healthy at 17:36. <br /><br />This incident affected 25% of available network interconnect capacity. Older cages utilize a 100Gbps network interface standard. To remove risk of reoccurrence, a planned upgrade to 400Gbps interfaces is being accelerated as much as possible, ensuring increased bandwidth available at all layers of the switch fabric for resiliency to path or device loss.
Resolved
All impacted services have now fully recovered.
Resolved
Incident resolved, systems are operating normally.
Resolved
This incident has been resolved, and service is operating normally again. Thanks for your patience.
Resolved
Shopify has found and mitigated the issue. The incident is now resolved
Resolved
This incident has been resolved.
Resolved
The fix has been successfully deployed, and validation is now complete. The issue preventing users from receiving incoming emails into Slack is fully resolved, and normal service functionality has been restored. We apologize for any disruptions to your day.
Resolved
The issue has been resolved. SSO login functionality in the us-east-1 region has returned to normal, and all services are operating as expected.
Resolved
After monitoring of the initial fixes implemented to resolve the issue, we have not seen any recurrences of the problem. We are marking this as resolved but will continue to monitor.
Resolved
This incident has been resolved, and service is operating normally again. Thanks for your patience.
Resolved
Notification latency for the affected shard is now under 5s.
Resolved
This incident has been resolved.
Resolved
The issue with session replay and error ingest has been resolved. We've caught up on all backlogged data as of 1:01pm PT.
Resolved
Between 07:41 AM PDT (UTC -07:00) and 12:37 PM PDT (UTC -07:00), some customers in North America experienced event ingestion and retrieval delays affecting Segments, Workflows, Timeline Events, and Report processing. This was caused by an underlying database infrastructure issue that increased read and write latency. As of 12:37 PM PDT (UTC -07:00), our affected tools 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.
Resolved
We've continued to observe no further issues and deploy failure reasons have been re-enabled.
Resolved
We have resolved the issues with the X sign in method when logging into your Hootsuite dashboard. If you continue to have issues logging into Hootsuite using the X sign in method, please reach out to our customer support team.
Resolved
The degradation in querying and triggers has been resolved and we're back to full functionality.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
All impacted services have now fully recovered.
Resolved
Between approximately 10:30 and 11:55 UTC on July 28, customers with telephony workloads in our London region experienced elevated error rates on SIP APIs. Small number of call transfers were affected. We mitigated by removing the affected infrastructure from service at 11:48 UTC, and error rates returned to normal by 11:55 UTC.
Resolved
This issue affecting the Close CRM integration has been resolved. Customers should now be able to connect or reconnect their Close account in Zapier normally. We have also replayed impacted delayed/held Zap runs that were paused during the incident. If you’re still seeing errors connecting or reconnecting Close, please retry and contact Zapier Support at: https://zapier.com/app/get-help.
Resolved
Documentation search functionality has been restored.
Resolved
Between July 19, 2026, at 23:05 UTC and July 20, 2026, at 03:55 UTC, Actions self-hosted and larger runners were unable to connect to GitHub. During this period, Actions jobs were delayed or failed when trying to acquire a runner. Jobs using standard and Mac hosted runners were not affected. Reconnection traffic from affected runners also increased load on GitHub APIs, resulting in 3-4 seconds of additional average request latency and elevated 5xx error rates.<br /><br />The incident was caused by a certificate lifecycle management failure in a subset of internal services, resulting in an SSL certificate expiration that disrupted runner connectivity. We restored service by rotating the affected certificate. Recovery began at 02:45 UTC. By 03:55 UTC, queued workflow backlog had been processed and workflow delay rates returned to normal.<br /><br />To prevent recurrence, we are strengthening certificate renewal automation, adding fallback expiry monitoring and alerting, and improving circuit-breaker protections during runner API disruptions to reduce the risk of cascading impact to other APIs.
Resolved
Payment requests for some participants in the Faster Payments Scheme might have experienced degradation for both Pay-In, VRP and Payouts during this incident's timeframe. Clients might have experienced settlement delays and minor volumes of failures for Pay-Ins, VRP and Payouts. Payments processing has returned to normal rates since 17:05 UTC on 27/07/2026, according to our logs. All impact across TrueLayer products leveraging Faster Payments is now resolved. Should you have any outstanding issues or questions, please reach out to our Client Operations team by raising a ticket with this form: https://support.truelayer.com/hc/en-us/p/ticket_type Impact start time: 27/07/2026, 10:44 UTC Impact end time: 27/07/2026, 17:05 UTC Client actions: None
Resolved
This incident has been resolved. Our services have returned to normal operations.
Resolved
This incident has been resolved.
Resolved
Root cause was identified to be the github outage: https://www.githubstatus.com/incidents/fmmsrcg5x638 Documentation updates are prorcessing normally between the times of 03:53 UTC and 04:09 UTC updates to GitHub failed to process to fix this manually run a manual update in the dashboard
Resolved
We are able to confirm that the difficulties with logging into Hootsuite have been resolved. If you encounter any further issues with logging into Hootsuite, please reach out to our customer support team. Thank you for your patience.
Resolved
Queue times have returned to normal
Resolved
Between 3:00 PM PT and 6:35 PM PT, customer-configured outbound webhooks were not being delivered as expected. This issue has now been resolved, and outbound webhook delivery is operating normally. Any form submissions received during this time were still successfully processed and remain available in the Forms tab within Site settings.
Resolved
Windows users faced an issue blocking login on the latest version of the Desktop App.
Resolved
The incident has been resolved
Resolved
All errors are resolved.
Resolved