Rust has recently deployed a new version, v1.80.
- Shared on their blog: https://blog.rust-lang.org/2024/07/25/Rust-1.80.0.html
Our teams are currently in the process of upgrading our Rust SDK to be fully compatible with Rust v1.80. Until completed, we are asking our customers to please remain on v1.79.0 until we’ve released a new version of the SDK.
We expect this release will ship within several business days, this release will be shared via our standard practices on: https://docs.rs/fastly/latest/fastly/
Fastly will be performing scheduled maintenance on our Secret Store. During this time customers may experience intermittent write errors for Secret Store secrets when writing via http://api.fastly.com from 23 July 2024, 21:00 UTC - 23 July 2024, 21:30 UTC as a result of this maintenance.
The scheduled maintenance has been completed.
To offer feedback on our status page, click "Give Feedback"
At approximately 08:00 UTC our engineers began to investigate a large traffic event impacting performance within our Europe and North America regions.
Standard traffic engineering practices have been deployed in response to this event, in an effort to reduce the potential impact to our customers within the regions. Customer may continue to see elevated errors and latency as mitigation efforts continue to be deployed.
All other products and services are unaffected by this incident.
Our engineers are implementing adjusted mitigation strategies in our North America and Europe regions to continue to balance traffic and manage performance.
Error rates and latency have improved, although customers may still experience intermittent periods of performance impact as traffic engineering continues to be deployed.
Engineering has implemented mitigation strategies and has confirmed a gradual recovery in our North America and Europe regions.
We are closely monitoring performance in these regions as a top priority as this event continues and will provide a final update once customer and end user experience has been fully restored.
Engineering has confirmed that Europe and North America regions have been fully restored. Customers may have experienced elevated errors and latency from 08:00 to 16:37 UTC.
This incident is resolved.
Affected customers would have experienced impact to varying degrees and to a shorter duration than as set forth above.
To offer feedback on our status page, click "Give Feedback"
We are investigating elevated errors to our API Services.
Our engineers have identified the contributing factor and are applying a fix to our API Services.
Engineering has deployed a fix and have confirmed a gradual recovery to our API Services. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.
Engineering has confirmed that our API Services have been fully restored. Customers may have experienced both the UI and API endpoint failures from 21:13 to 23:30 UTC.
This incident is resolved.
Affected customers may have experienced impact to varying degrees and to a shorter or longer duration than as set forth above.
To offer feedback on our status page, click "Give Feedback"
Our engineers detected an unplanned event that contained impact to our Compute service.
This event is resolved, and there is no remaining impact.
Customers may have experienced delays in change requests to configurations on Compute from 17:29 to 17:46 UTC. (~17min duration)
All other Compute requests remain unaffected during the impact duration.
Please engage with our Support team through https://support.fastly.com if you have any questions and/or concerns.
Fastly has been alerted to an external outage impacting Windows-based systems.
All our products and services remain unaffected.
Fastly is actively monitoring the situation for any potential impact to customers.
Fastly will be adding capacity at our Paris (CDG) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 04 July 2024 at 03:00 UTC.
Our estimated duration is 6h.
When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. Please verify that your origin access lists allow the full range of Fastly IP addresses (https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges). Customers with any questions or concerns should contact Fastly’s Support team (support@fastly.com).
This planned capacity expansion has been postponed and will now begin on 17 July 2024 at 03:00 UTC.
Our estimated duration is 6h.The scheduled maintenance has been completed.
To offer feedback on our status page, click "Give Feedback"
We are investigating data display issues within our Dashboard Data service.
Our engineers have identified the contributing factor and are applying a fix to our Dashboard Data service.
Engineering has confirmed the impact to our Dashboard Data service has been mitigated.
Engineering has confirmed that our Dashboard Data service has been fully restored. Customers may have experienced data display issues from 14:12 to 17:47 UTC.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
Fastly Engineers detected a performance impacting event affecting the Singapore (QPG) data center.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
We have recently posted a thread on the Fastly Community Forum to ask for your feedback on the `fastly.toml` package manifest format as we look to design a new version that more effectively serves the needs of Compute developers:
We invite you to join the discussion and appreciate your insight on how these decisions should be made.