Mumbai (BOM)

Platform Asia Chennai (MAA) Mumbai (BOM)
 
14 April 2025, 14:00 UTC

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.

 
14 April 2025, 15:15 UTC

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.

 
14 April 2025, 15:16 UTC

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

 
14 April 2025, 15:36 UTC

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.


Platform Asia Mumbai (BOM)
 
03 March 2025, 06:44 UTC

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.

Platform Asia Chennai (MAA) Kolkata (CCU) Mumbai (BOM) New Delhi (DEL)
 
23 February 2025, 09:00 UTC

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.


 
23 February 2025, 09:46 UTC

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.

 
23 February 2025, 10:07 UTC

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

 
23 February 2025, 10:44 UTC

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.


16 February 2025, 09:13 UTC
Platform Asia Mumbai (BOM)
 
16 February 2025, 09:13 UTC

We are investigating elevated errors to our Mumbai (BOM) Point of Presence (POP).

All other products and services are unaffected by this incident.

 
16 February 2025, 09:54 UTC

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.

 
16 February 2025, 10:10 UTC

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

 
16 February 2025, 10:12 UTC

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.


Platform Asia Mumbai (BOM)
 
29 January 2025, 17:22 UTC

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.

Platform Asia Chennai (MAA) Kolkata (CCU) Mumbai (BOM) New Delhi (DEL)
 
19 December 2024, 05:00 UTC

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.


 
19 December 2024, 06:02 UTC

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.

 
19 December 2024, 07:10 UTC

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.

 
19 December 2024, 07:36 UTC

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

 
19 December 2024, 07:42 UTC

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.


Platform Asia Chennai (MAA) Hyderabad (HYD) Kolkata (CCU) Mumbai (BOM) New Delhi (DEL)
 
09 October 2024, 05:51 UTC

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.


 
09 October 2024, 10:03 UTC

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

 
09 October 2024, 10:31 UTC

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.

 
09 October 2024, 10:48 UTC

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

 
09 October 2024, 10:56 UTC

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.


05 September 2024, 19:48 UTC
Platform North America Europe Asia South America Oceania Africa Amsterdam (AMS) Adelaide (ADL) Bangkok (BKK) Bogota (BOG) Cape Town (CPT) Chennai (MAA) Auckland (AKL) Buenos Aires (EZE) Ghana (ACC) Ashburn (IAD) Brussels (BRU) Brisbane (BNE) Curitiba (CWB) Johannesburg (JNB) Dubai (FJR) Copenhagen (CPH) Christchurch (CHC) Dubai (DXB) Fortaleza (FOR) Dublin (DUB) Fujairah (FJR) Melbourne (MEL) Lima (LIM) Hyderabad (HYD) Frankfurt (FRA) Perth (PER) Atlanta (PDK) Frankfurt (HHN) Hong Kong (HKG) Rio de Janeiro (GIG) Boston (BOS) Kolkata (CCU) Helsinki (HEL) Sydney (SYD) Santiago (SCL) Calgary (YYC) London (LCY) Kuala Lumpur (KUL) Wellington (WLG) Sāo Paulo (CGH) Chicago (CHI) London (LON) Manila (MNL) Sao Paulo (GRU) Mumbai (BOM) London (LHR) New Delhi (DEL) Lisbon (LIS) Osaka (ITM) Madrid (MAD) Seoul (ICN) Manchester (MAN) Marseille (MRS) Singapore (QPG) Columbus (CMH) Milan (LIN) Columbus (LCK) Milan (MXP) Oslo (OSL) Dallas (DFW) Munich (MUC) Tokyo (HND) Denver (DEN) Palermo (PMO) Tokyo (NRT) Detroit (DTW) Tokyo (TYO) Gainesville (GNV) Paris (CDG) Honolulu (HNL) Paris (PAR) Rome (FCO) Houston (IAH) Sofia (SOF) Stockholm (BMA) Kansas City (MCI) Vienna (VIE) Los Angeles (BUR) Los Angeles (LAX) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) New York (NYC) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
05 September 2024, 19:48 UTC

We are investigating elevated errors to our Platform delivery services.

 
05 September 2024, 21:44 UTC

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

 
05 September 2024, 22:01 UTC

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

 
05 September 2024, 23:00 UTC

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

 
05 September 2024, 23:34 UTC

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.

 
06 September 2024, 00:48 UTC

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

Fastly Platform Asia Third Party Service Provider Chennai (MAA) Hyderabad (HYD) Kolkata (CCU) Mumbai (BOM) New Delhi (DEL)
 
23 April 2024, 11:30 UTC

On Tuesday, the 23rd of April 2024 from 11:30 UTC to the 24th of April 01:36 UTC, our engineers observed an unplanned event that contained impact across the Chennai (MAA), Mumbai (BOM), Kolkata (CCU), Delhi (DEL), and Hyderabad (HYD) Points of Presence (POPs) with a common transit provider.

This event is resolved, and there is no remaining impact.

18 March 2024, 08:03 UTC
Platform Asia Mumbai (BOM)
 
18 March 2024, 08:03 UTC

Traffic in Mumbai (BOM) has been temporarily rerouted.

All other locations and services are unaffected.

 
18 March 2024, 08:52 UTC

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