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

All other products and services are unaffected by this incident.

Our engineers have identified the contributing factor, developed a fix, and confirmed that the impact to our Singapore (SIN) POP has been mitigated.

Engineering has confirmed that our Singapore (SIN) POP has been fully restored. Customers may have experienced elevated errors and increased latency from 04:20 to 04:35 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2025-05-14 04:46:17 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 Bangkok (BKK) data center.

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

Fastly Engineers detected a performance impacting event affecting the Singapore (SIN) 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 Osaka (ITM) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 12 May 2025 at 16:00 UTC.

Our estimated duration is 8h. 

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 at https://support.fastly.com.

The scheduled maintenance has been completed.

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

Fastly will be performing scheduled maintenance on our Osaka (ITM) data center from 07 May 2025, 16:00 UTC - 08 May 2025 00:00 UTC.

During this time frame traffic will be redirected to neighboring POPs in the region.

The scheduled maintenance has been completed.

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

Fastly Engineers detected a performance impacting event affecting the Manila (MNL) data center.

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

Fastly will be performing scheduled maintenance on our Osaka (ITM) data center from 06 May 2025, 16:00 UTC - 07 May 2025 00:00 UTC.

During this time frame traffic will be redirected to neighboring POPs in the region.

The scheduled maintenance has been completed.

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

Fastly Engineers detected a performance impacting event affecting the Hyderabad (HYD) data center.

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

Fastly Engineers detected a performance impacting event affecting the Tokyo (NRT) POP between 14:00 to 16:00 UTC and 18:00 to 20:15 UTC. During this time customers may have experienced elevated errors and/or latency. 

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 Hyderabad (HYD) 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 Hyderabad (HYD) Point of Presence (POP).

All other locations and services are unaffected.

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

Engineering has confirmed that our Hyderabad (HYD) Point of Presence (POP) has been fully restored. Customers may have experienced latency and network timeouts from 06:30 to 06:40 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2025-04-22 06:42:30 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.