Mumbai (BOM)

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) Brussels (BRU) Auckland (AKL) Buenos Aires (EZE) Ghana (ACC) Ashburn (IAD) Copenhagen (CPH) Brisbane (BNE) Curitiba (CWB) Johannesburg (JNB) Dubai (FJR) Dublin (DUB) Christchurch (CHC) Dubai (DXB) Fortaleza (FOR) Frankfurt (FRA) Fujairah (FJR) Melbourne (MEL) Lima (LIM) Hyderabad (HYD) Frankfurt (HHN) Perth (PER) Rio de Janeiro (GIG) Atlanta (PDK) Helsinki (HEL) Hong Kong (HKG) Santiago (SCL) Boston (BOS) Kolkata (CCU) London (LCY) Sydney (SYD) Sāo Paulo (CGH) Calgary (YYC) London (LON) Kuala Lumpur (KUL) Wellington (WLG) Chicago (CHI) Sao Paulo (GRU) London (LHR) Manila (MNL) Mumbai (BOM) Lisbon (LIS) New Delhi (DEL) Madrid (MAD) Manchester (MAN) Osaka (ITM) Marseille (MRS) Seoul (ICN) Milan (LIN) Milan (MXP) Singapore (QPG) Columbus (CMH) Oslo (OSL) Columbus (LCK) Munich (MUC) Palermo (PMO) Dallas (DFW) Tokyo (HND) Denver (DEN) Paris (CDG) Tokyo (NRT) Detroit (DTW) Paris (PAR) Rome (FCO) Tokyo (TYO) Gainesville (GNV) Sofia (SOF) Honolulu (HNL) Stockholm (BMA) Houston (IAH) Vienna (VIE) Kansas City (MCI) 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.

Platform Asia Mumbai (BOM)
 
11 August 2023, 14:30 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.

 
11 August 2023, 14:32 UTC

This incident has been resolved.

Platform Asia Mumbai (BOM) New Delhi (DEL)
 
11 April 2023, 15:00 UTC

We're investigating elevated errors in our  (DEL) and New Delhi (BOM) Mumbai Points of Presence (POPs).

All other POP locations and services are unaffected.

 
11 April 2023, 16:46 UTC

This incident has been resolved.

Platform Asia Chennai (MAA) Mumbai (BOM)
 
10 April 2023, 14:56 UTC

We're investigating elevated errors in our Chennai (MAA) and Mumbai (BOM) Points of Presence (POPs).

All other POP locations and services are unaffected.

 
10 April 2023, 16:00 UTC

This incident has been resolved.

16 February 2023, 14:36 UTC
Platform Asia Mumbai (BOM)
 
16 February 2023, 14:36 UTC

Traffic in Mumbai (BOM) has been temporarily rerouted.

All other locations and services are unaffected.

 
17 February 2023, 12:18 UTC

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

 
17 February 2023, 18:57 UTC

This incident has been resolved.

19 January 2023, 23:05 UTC
Platform North America Europe Asia South America Oceania Africa Amsterdam (AMS) Adelaide (ADL) Bangkok (BKK) Bogota (BOG) Cape Town (CPT) Chennai (MAA) Brussels (BRU) Auckland (AKL) Buenos Aires (EZE) Ghana (ACC) Ashburn (IAD) Copenhagen (CPH) Brisbane (BNE) Curitiba (CWB) Johannesburg (JNB) Dubai (FJR) Dublin (DUB) Christchurch (CHC) Dubai (DXB) Fortaleza (FOR) Frankfurt (FRA) Fujairah (FJR) Melbourne (MEL) Lima (LIM) Hyderabad (HYD) Frankfurt (HHN) Perth (PER) Rio de Janeiro (GIG) Atlanta (PDK) Helsinki (HEL) Hong Kong (HKG) Santiago (SCL) Boston (BOS) Kolkata (CCU) London (LCY) Sydney (SYD) Sāo Paulo (CGH) Calgary (YYC) London (LON) Kuala Lumpur (KUL) Wellington (WLG) Chicago (CHI) Sao Paulo (GRU) London (LHR) Manila (MNL) Mumbai (BOM) Lisbon (LIS) New Delhi (DEL) Madrid (MAD) Manchester (MAN) Osaka (ITM) Marseille (MRS) Seoul (ICN) Milan (LIN) Milan (MXP) Singapore (QPG) Columbus (CMH) Oslo (OSL) Columbus (LCK) Munich (MUC) Palermo (PMO) Dallas (DFW) Tokyo (HND) Denver (DEN) Paris (CDG) Tokyo (NRT) Detroit (DTW) Paris (PAR) Rome (FCO) Tokyo (TYO) Gainesville (GNV) Sofia (SOF) Honolulu (HNL) Stockholm (BMA) Houston (IAH) Vienna (VIE) Kansas City (MCI) 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)
 
19 January 2023, 23:05 UTC

We're currently investigating potential impact to performance with our CDN services.

 
19 January 2023, 23:06 UTC

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

 
19 January 2023, 23:48 UTC
On the 19th of January at 23:00 UTC a configuration change was deployed which impacted performance to global CDN delivery. Fastly Engineering reverted the change resulting in immediate recovery at 23:06 UTC. Fastly's Customer Incident Response team is currently preparing a Fastly Service Advisory of today's incident, and will be made available to Fastly Customers.
 
20 January 2023, 00:48 UTC

This incident has been resolved.