Fly.ioflyctl deploy timeouts
Earlier today, an issue caused elevated rate limiting and some deployment timeouts. A fix is in place and deployments are back to normal.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
Earlier today, an issue caused elevated rate limiting and some deployment timeouts. A fix is in place and deployments are back to normal.
Resolved
We're happy to share that this issue has been fully resolved and the dark mode setting within the Buffer dashboard is loading normally once again.
Resolved
We had a temporary outage between 13:26 and 13:56 UTC, which resulted in a number of post call webhook failures. This issue should now be resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue affecting video thumbnails and previews for uploads made through our mobile apps has been fully resolved. Thumbnails are now generating as expected, and videos uploaded via mobile are displaying correctly in the queue. Our apologies for the inconvenience, and thank you for your patience while we worked through this. Please reach out to us at hello@buffer.com if you're still experiencing issues.
Resolved
Performance has returned to normal levels. 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
A fix has been deployed and commands are fully restored. If you still encounter issues, please reset your conversation or restart the environment to apply the changes
Resolved
All impacted services have now fully recovered.
Resolved
This incident has now been resolved.
Resolved
**What Happened:** On February 16th \(09:04 AM EST\), our US customers experienced a 28-minute system downtime due to an application-level bug. **What caused it:** A recent code change in the billing subsystem responsible for updating account plans introduced an edge-case bug that dramatically increased platform load, which caused system downtime. **How we responded:** Our monitoring system promptly identified the issue, triggering an immediate response from our engineering team. By activating failover mechanisms, reverting the problematic code change, and blocking the affected endpoint, we restored normal service by 09:32 AM EST. **What we're doing to prevent recurrence:** To enhance system resilience, we are implementing database optimizations, additional guardrails, and limits to prevent load spikes on the platform. It also includes strengthening our error detection and recovery processes. We sincerely apologize for any disruption this caused to your workflow. Thank you for your understanding as we work to continuously improve our platform's reliability. Your team at [monday.com](http://monday.com)
Resolved
Upon further investigation, we have established that the impact actually began on 04/02/2026, 11:49 UTC. Please note that this is a correction to the previously communicated start time of 02/02/2026, 04:30 UTC Data API degradation has been resolved. Normal service has been restored. Impact start time: 04/02/2026, 11:49 UTC Impact end time: 16/02/2026 15:35 UTC Client actions: None
Resolved
This incident has been resolved.
Resolved
The issue occured due to the failures in the backend services. It has been fixed and the team is monitoring the health of the application.
Resolved
The root cause appeared to be an issue with an upstream dependency (database connection pooler), which we have replaced. We will be writing a full post-mortem with more details.
Resolved
Degraded performance in a Supavisor cluster resulted in elevated connection latency and increased p99 response times between 2026-02-15 22:00 and 2026-02-16 01:00. The problematic node was replaced and performance returned to normal levels.
Resolved
Issue was resolved
Resolved
This incident has been resolved.
Resolved
Issue fixed
Resolved
This incident has been resolved.
Resolved
Severity Level: Critical Our engineers have identified the root cause of the issue and they’re actively working on remediation. Starbase and other storage-dependent services in us-west-3 have been restored and are operating normally. The primary remaining issue is that some customer VMs are still experiencing stale or empty NFS mounts as a result of the earlier power event and mass reboots. We are recommending affected customers reboot their VMs to restore file system access. In cases where a VM reboot does not resolve the issue, a hypervisor reboot may be necessary. In the event you’re unsure as to whether your service is impacted by this incident, please open a support ticket. We’ll get back to you as soon as possible. • https://support.lambdalabs.com/hc/en-us/requests/new To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button. Thank you for your patience and understanding during this time.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
All impacted services have now fully recovered.
Resolved
The issue has been resolved. All impacted systems are now operating normally.
Resolved
This incident has been resolved.
Resolved
The error rates have now returned to normal levels
Resolved
This incident has now been resolved.
Resolved
All impacted services have now fully recovered.
Resolved
We’ve published a post-mortem on our blog: https://supabase.com/blog/supabase-incident-on-february-12-2026.
Resolved
Severity Level: Medium The incident has been resolved. Launches in us-east-1 should now work as expected.
Resolved
From Feb 12, 2026 09:16:00 UTC to Feb 12, 2026 11:01 UTC, users attempting to download repository archives (tar.gz/zip) that include Git LFS objects received errors. Standard repository archives without LFS objects were not affected. On average, the archive download error rate was 0.0042% and peaked at 0.0339% of requests to the service. This was caused by deploying a corrupt configuration bundle, resulting in missing data used for network interface connections by the service.<br /><br />We mitigated the incident by applying the correct configuration to each site. We have added checks for corruption in this deployment, and will add auto-rollback detection for this service to prevent issues like this in the future.
Resolved
The issue has been resolved. All impacted systems are now operating normally. All delayed messages have been processed.
Resolved
This incident has been resolved.
Resolved
The incident has been resolved.
Resolved
A inconsistência no disparo de SMS do RD Station Marketing foi resolvida com sucesso. O envio de SMS foi restabelecido e novos disparos já estão sendo processados. Nossa equipe seguirá monitorando ativamente a estabilidade do serviço para garantir o funcionamento integral. Caso você note que sua conta ainda contém alguma inconsistência, por favor, entre em contato com nosso Time de Suporte através da nossa Central de Ajuda "através da nossa Central de Ajuda": http://ajuda.rdstation.com/..
Resolved
On February 10th, 2026, between 14:35 UTC and 15:58 UTC web experiences on GitHub.com were degraded including Pull Requests and Authentication, resulting in intermittent 5xx errors and timeouts. The error rate on web traffic peaked at approximately 2%. This was due to increased load on a critical database, which caused significant memory pressure resulting in intermittent errors. <br /><br />We mitigated the incident by applying a configuration change to the database to increase available memory on the host. <br /><br />We are working to identify changes in load patterns and are reviewing the configuration of our databases to ensure there is sufficient capacity to meet growth. Additionally, we are improving monitoring and self-healing functionalities for database memory issues to reduce our time to detect and mitigation.
Resolved