Fastly Engineers detected a performance impacting event affecting the Mumbai (BOM) 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 Mumbai (BOM) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 21 July 2025 at 21: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 at https://support.fastly.com.

The scheduled maintenance has been completed.

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

We are investigating elevated errors to our Chennai (MAA), Mumbai (BOM) 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 Chennai (MAA), Mumbai (BOM) (POP).

All other locations and services are unaffected.

Engineering has confirmed the impact to Chennai (MAA), Mumbai (BOM) (POP) has been mitigated.

Engineering has confirmed that Chennai (MAA), Mumbai (BOM) POPs has been fully restored. Customers may have experienced elevated errors and latency from 14:00 to 14:55 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2025-04-14 14:48: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 Engineers detected a performance impacting event affecting the Mumbai (BOM) 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), Kolkata (CCU), Mumbai (BOM), New Delhi (DEL) Point 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), Kolkata (CCU), Mumbai (BOM), New Delhi (DEL) POPs.

All other locations and services are unaffected.

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

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

This incident is resolved.

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

Status Post, Created Date/Time: 2025-02-23 09:28:22 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 Mumbai (BOM) 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 Mumbai (BOM) Point of Presence (POP).

All other locations and services are unaffected.

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

Engineering has confirmed that our Mumbai (BOM) Point of Presence (POP) has been fully restored. Customers may have experienced elevated errors and latency from 09:13 to 09:40 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2025-02-16 09:44:16 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 Mumbai (BOM) 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 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 Platform delivery services.

Our engineers are continuing to investigate the impact to our Platform delivery services.

Our engineers have identified the contributing factor and are applying a fix to our Platform delivery services.

Our engineers have identified the contributing factor and are continuing to apply the mitigation strategy to our Platform delivery services.

Engineering has deployed a fix and have confirmed a gradual recovery to our Platform delivery service. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.

Engineering has confirmed that our Platform delivery services have been fully restored. Customers may have experienced elevated errors and latency. In addition, Compute customers may have also experienced delayed configuration deployments from the 5th of September at 19:48 to the 6th of September at 00:48 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"