[closed]

We're currently investigating an increase in discards with our Streaming Logs service. 

All other services are unaffected.

This issue has been identified and a fix is being implemented. 

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

[closed]

We have investigated performance issues with our Streaming Logs service. Customers may have experienced delay of log delivery or discarding of logs during the affected time window.

All other services were unaffected.

This incident has been resolved.

[closed]

On March 7th, 2023, Rapid7 will formally retire their Logentries product. As a result, Fastly will be completely removing the associated Logentries integration on the same date. We strongly advise all customers to replace their Logentries integration with a different logging integration (https://docs.fastly.com/en/guides/integrations#_logging-endpoints) in advance of this end-of-life date.

If you have a paid plan from Rapid7, you can choose to retain your Logentries data by following Rapid7’s archiving instructions (https://docs.logentries.com/docs/aws-s3-archiving).

This product has been retired.

[closed] We're currently investigating performance issues with our Compute@Edge Log Tailing service. All other services are unaffected.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

[closed] We're currently investigating performance issues with our Streaming Logs service for only Compute@Edge logs. All other services, edge traffic, and CDN logs are unaffected.

Update - Fastly teams are continuing to investigate performance issues causing delays with our Streaming Logs for Compute@Edge. There continues to be no impact to other Fastly services, edge traffic, and CDN log delivery.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

[closed] We're currently investigating performance issues with our Streaming Logs service. All other services are unaffected.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

[closed] We're currently investigating performance issues with our Streaming Logs service. All other services are unaffected.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

[closed] Fastly Engineers have confirmed reports of elevated errors impacting some streaming log services from approximately 06:00 UTC through to 12:00 UTC on the 30th of September 2021. This issue has been resolved and we are monitoring performance closely.

[closed] We're currently investigating performance issues with our Streaming Logs service. All other services are unaffected.

We are continuing to investigate this issue.

This incident has been resolved.

[closed] Fastly’s global network is growing, and with that growth comes changes and enhancements in some of our naming conventions and best practices. Refer to our server.identity and server.hostname pages on Developer Hub for an in depth explanation of the new cache naming schema. Starting no earlier than Thursday, 12 Aug 2021, we will begin populating the node name in some situations according to a new scheme. We’d like to share these changes so that if our customers are performing any troubleshooting or logging these values, one can not only know with certainty exactly what node processed a request, but also update any log parsing or automation to properly parse these values. Please note that for most of our existing infrastructure, the naming scheme is not changing, and you will continue to see these values set to the previous scheme for some of your traffic and log data. We suggest that if customers are parsing these fields out and breaking them down into individual values (such as the node name and POP) to adjust any tooling or automation to be able to handle both formats. Feel free to reach out to our support team if you have any questions on these changes. server.identity server.hostname

Maintenance will begin as scheduled in 60 minutes.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

The scheduled maintenance has been completed.