Fastly Engineers detected a performance impacting event affecting the Bangkok (BKK) data center.

All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

We are investigating elevated errors to our Chennai (MAA), Mumbai (BOM), New Delhi (DEL) Points of Presence (POPs).

All other products and services are unaffected by this incident.

Our engineers have identified the contributing factor and are applying a fix to our Chennai (MAA), Mumbai (BOM), New Delhi (DEL) POPs.

All other locations and services are unaffected.

Our engineers have identified the contributing factor and are continuing to apply the mitigation strategy to our Chennai (MAA), Mumbai (BOM), New Delhi (DEL) POPs.

All other locations and services are unaffected.

Engineering has confirmed the impact to our Chennai (MAA), Mumbai (BOM), New Delhi (DEL) POPs has been mitigated.

Engineering has confirmed that our Chennai (MAA), Kolkata (CCU), Mumbai (BOM), New Delhi (DEL) POPs have been fully restored. Customers may have experienced elevated errors and latency from 05:00 to 07:28 UTC.

This incident is resolved.

Affected customers may 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" 

Status Post, Created Date/Time: 2024-12-19 06:02:08 UTC 

Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team.

We are investigating elevated errors to our Tokyo (TYO) Point of Presence (POP). 

All other products and services are unaffected by this incident.

Our engineers have identified the contributing factor and are applying a fix to our Tokyo (TYO) Point of Presence (POP).

All other locations and services are unaffected.

Engineering has confirmed the impact to our Tokyo (TYO) Point of Presence (POP) has been mitigated.

Engineering has confirmed that our Tokyo (TYO) Point of Presence (POP) has been fully restored. Customers may have experienced increased 5xx errors and latency from 3:00 to 3:40 UTC.

This incident is resolved.

To offer feedback on our status page, click "Give Feedback" 

Status Post, Created Date/Time: 2024-12-18 03:37:38 UTC 

Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team.

As part of Fastly’s global network expansion, we will be adding Singapore (SIN) data center to Fastly's Asia network. 

Traffic served by our Singapore (SIN) data center will be aggregated into our Asia region for billing and stats purposes.

We expect that some traffic currently served by our data centers in neighboring regions will shift to Singapore (SIN). As such, some customers may see a change in their bills.

Fastly’s standard billing rates are located at https://www.fastly.com/pricing.

The scheduled maintenance has been completed.

To offer feedback on our status page, click "Give Feedback" 

We are investigating elevated errors to our Singapore (QPG) Point of Presence (POP).

All other products and services are unaffected by this incident.

Our engineers have identified the contributing factor and are applying a fix to our Singapore (QPG) POP.

All other locations and services are unaffected.

Engineering has confirmed the impact to Singapore (QPG) POP has been mitigated.

Engineering has confirmed that Singapore (QPG) POP has been fully restored. Customers may have experienced elevated errors or latency from 03:50 to 04:51 UTC.

This incident is resolved.

To offer feedback on our status page, click "Give Feedback" 

Status Post, Created Date/Time: 2024-11-13 04:35:37 UTC 

Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team.

Fastly will be migrating Tokyo (HND) shield customers to Tokyo (NRT). 

Customers can either apply a new shield in advance through their Fastly Application user interface, or their shielding configuration will be updated to Tokyo (NRT) on their behalf.

All changes are planned to be completed by 04 November 2024.

As these changes are applied, customers may observe additional origin traffic as cache nodes retrieve content from origin.

Customers with any questions or concerns should contact their dedicated technical account team or Fastly’s Support team at https://support.fastly.com.

We are investigating elevated errors to our Chennai (MAA), Hyderabad (HYD), Kolkata (CCU), Mumbai (BOM), New Delhi (DEL) Points of Presence (POPs).

All other products and services are unaffected by this incident.

Our engineers are continuing to investigate elevated errors to our Chennai (MAA), Hyderabad (HYD), Kolkata (CCU), Mumbai (BOM), New Delhi (DEL) POPs.

Our engineers have identified the contributing factor and are applying a fix to our Chennai (MAA), Hyderabad (HYD), Kolkata (CCU), Mumbai (BOM), New Delhi (DEL) POPs.

All other locations and services are unaffected.

Engineering has confirmed the impact to our Chennai (MAA), Hyderabad (HYD), Kolkata (CCU), Mumbai (BOM), New Delhi (DEL) POPs has been mitigated.

Engineering has confirmed that Chennai (MAA), Hyderabad (HYD), Kolkata (CCU), Mumbai (BOM), New Delhi (DEL) POPs have been fully restored. Customers may have experienced intermittent errors from 05:51 to 10:03 UTC.

This incident is resolved.

To offer feedback on our status page, click "Give Feedback" 

Status Post, Created Date/Time: 2024-10-09 09:36:33 UTC 

Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team.

We are investigating elevated errors to our Singapore (QPG), Bangkok (BKK) Points of Presence (POPs).

All other products and services are unaffected by this incident.

Our engineers have identified the contributing factor and are applying a fix to our Singapore (QPG), Bangkok (BKK) POPs. Our Singapore (QPG) POP has begun to show signs of recovery.

All other locations and services are unaffected.

Engineering has confirmed the impact to our Singapore (QPG), Bangkok (BKK) POPs has been mitigated.

Engineering has confirmed that our Singapore (QPG), Bangkok (BKK) POPs have been fully restored. Customers may have experienced elevated errors, latency, and timeouts from 01:30 to 2:10 UTC.

This incident is resolved.

Affected customers may 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" 

Status Post, Created Date/Time: 2024-10-09 02:05:18 UTC 

Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team.

Fastly Engineers detected a performance impacting event affecting the Hong Kong (HKG) data center.

All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

Fastly will be adding capacity at our Tokyo (NRT) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 01 October 2024 at 19:00 UTC.

Our estimated duration is 2 days and 4 hours. 

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).

The scheduled maintenance has been completed.

To offer feedback on our status page, click "Give Feedback"