TelnyxWireless SIM Management Actions Delayed
The delays in SIM card management actions have been resolved. All operations are processing normally.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
The delays in SIM card management actions have been resolved. All operations are processing normally.
Resolved
The delays in SIM card management actions have been resolved. All operations are processing normally.
Resolved
This incident has been resolved and data has been restored for impacted customers across all regions.
Resolved
The observed behaviour was not due to degraded performance, our alerting was likely too sensitive. Payouts are processing as normal. Client actions: None
Resolved
Customers were unable to load Webflow Canvas and the Dashboard between 19:28 and 20:20 UTC. The issue has now been resolved and services are operating normally. Thank you for your patience while we addressed this issue.
Resolved
This incident has been resolved.
Resolved
All impacted services have now fully recovered.
Resolved
On March 11, 2026, between 13:00 UTC and 15:23 UTC the Copilot Code Review service was degraded and experienced longer than average review times. On average, Copilot Code Review requests took 4 minutes and peaked at just under 8 minutes. This was due to hitting worker capacity limits and CPU throttling. We mitigated the incident by increasing partitions, and we are improving our resource monitoring to identify potential issues sooner.
Resolved
The delays in SIM card management actions have been resolved. All operations are processing normally.
Resolved
The issue has been resolved, and the service is operating normally for all affected customers.
Resolved
This incident has been resolved.
Resolved
The issue affecting connections to Fidelity and Fidelity NetBenefits has been resolved. Item adds and API requests through Plaid have returned to normal operation. We will continue to monitor to ensure stability.
Resolved
The checkout page payment and tax modals are now functioning normally again. During this incident, you may have been unable to add or update payment or tax information during checkout. If you still have trouble updating payment or tax details, you can update your payment method from the billing settings page and then return to checkout. We apologize for the disruption and appreciate your patience as we got this resolved. If you do see any further issues, please reach out to our support team at https://zapier.com/app/get-help
Resolved
The issue has been resolved. All impacted systems are now operating normally.
Resolved
All impacted services have now fully recovered.
Resolved
The issue has been resolved
Resolved
This incident has been resolved.
Resolved
The delays in SIM card management actions have been resolved. All operations are processing normally.
Resolved
The incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The delays in SIM card management actions have been resolved. All operations are processing normally.
Resolved
We believe this incident has been successfully mitigated. If you continue to experience any issues, please contact support@render.com.
Resolved
The issue has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Error rates have returned to normal, and connectivity has stabilised.
Resolved
The delays in SIM card management actions have been resolved. All operations are processing normally.
Resolved
We're happy to see that publishing success rates for updates including videos to Facebook have returned to normal now, and we're no longer seeing the errors from Meta that were identified yesterday. If you have any failed posts still in your queue in Buffer, please can you retry sending again now? Thank you so much for your patience with us throughout this incident, and we're very sorry for the inconvenience it caused.
Resolved
This incident has been resolved.
Resolved
Search functionality experienced a service disruption affecting both unauthenticated and authenticated users. The incident lasted approximately 92 minutes. A fix for unauthenticated sites was deployed first, but authenticated sites required additional remediation due to a separate edge case in the authentication path. Impact • Affected window: 7:12 PM – 8:44 PM PT • Users affected: All users relying on search in authenticated contexts • User experience: Search queries returned errors or failed to return results during the affected period Timeline Time (PT) | Event 7:12 PM | Upstream provider begins index migration; search functionality starts failing ~7:20 PM | Incident detected via monitoring/alerts ~7:22 PM | On-call engineer begins investigation; root cause identified as upstream index migration ~7:30 PM | Decision made to fail over to backup indices 7:54 PM | Migration to backup indices complete; search restored for unauthenticated sites ~8:06 PM | Separate edge case identified affecting authenticated sites 8:44 PM | Fix deployed for authenticated sites; full resolution confirmed — search restored across all sites Root Cause An upstream provider initiated an index migration, which caused search functionality to begin failing. Unauthenticated and authenticated search requests followed different code paths, so failing over to backup indices resolved the issue for unauthenticated sites first. Authenticated sites hit a separate edge case that required additional remediation, extending the total incident duration. Note: We are completing our migration to a completely new search system tomorrow, which provide significantly improved stability going forward.
Resolved
We can confirm that the issues when publishing video content to Facebook have been resolved and are now functioning as normal. Any posts that may have failed during this time can now be rescheduled. We appreciate your patience and understanding.
Resolved
At approximately 6am Pacific we had a high rate of server errors for approximately 30 minutes for a subset of customer backends. This was caused by a 20x increase in traffic that saturated one of our databases and led to resource exhaustion on one of our function execution clusters, which is why the impact spilled beyond just that specific database. We’ve scaled up our infrastructure further and are deploying some changes to load shedding and retries to minimize the impact of such an event in future. While we aim to have no cascading impact on other customers from a load spike we’re also deploying dedicated isolated hardware for customers on our upcoming Business plan.
Resolved
A search outage affected all Mintlify-powered sites after our upstream search provider executed a migration on our search indices. The migration rendered existing indices unavailable, causing search functionality to return errors or no results across all customer sites. The incident was resolved by failing over to backup indices. Impact • Scope: All Mintlify sites with search functionality • User experience: Search queries returned errors or empty results for the duration of the outage • Duration of impact: ~42 minutes Timeline (all times PT) Time | Event 7:12 PM | Upstream provider begins index migration; search functionality starts failing ~7:20 PM | Incident detected via monitoring/alerts ~7:22 PM | On-call engineer begins investigation; root cause identified as upstream index migration ~7:30 PM | Decision made to fail over to backup indices 7:54 PM | Migration to backup indices complete; search functionality restored across all sites Root Cause Our upstream search provider initiated a migration of our search indices without adequate coordination. This migration caused the primary indices to become unavailable, which in turn broke search queries across all Mintlify sites. Resolution Within approximately 10 minutes of detecting the incident, the team initiated a failover to pre-existing backup indices. Once the migration to backup indices completed, full search functionality was restored.
Resolved
On March 12, 2026, affected Confluence Cloud users may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.
Resolved
All impacted services have now fully recovered.
Resolved
This incident has been resolved.
Resolved
All impacted services have now fully recovered.
Resolved
From 12:45 to 4:50 PM UTC today, we experienced an issue that prevented some users from previewing and publishing Figma Make files. We have updated this from Monitoring to Resolved.
Resolved
This has been resolved.
Resolved
We believe the 503s have been resolved.
Resolved