Los Angeles (BUR)

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

Platform North America Europe Amsterdam (AMS) Brussels (BRU) Ashburn (IAD) Copenhagen (CPH) Dublin (DUB) Frankfurt (FRA) Frankfurt (HHN) Atlanta (PDK) Helsinki (HEL) Boston (BOS) London (LCY) Calgary (YYC) London (LON) Chicago (CHI) London (LHR) Lisbon (LIS) Madrid (MAD) Manchester (MAN) Marseille (MRS) Milan (LIN) Milan (MXP) Columbus (CMH) Oslo (OSL) Columbus (LCK) Munich (MUC) Palermo (PMO) Dallas (DFW) Denver (DEN) Paris (CDG) Detroit (DTW) Paris (PAR) Rome (FCO) 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)
 
23 July 2024, 12:48 UTC

At approximately 08:00 UTC our engineers began to investigate a large traffic event impacting performance within our Europe and North America regions. 

Standard traffic engineering practices have been deployed in response to this event, in an effort to reduce the potential impact to our customers within the regions. Customer may continue to see elevated errors and latency as mitigation efforts continue to be deployed.

All other products and services are unaffected by this incident.

 
23 July 2024, 14:29 UTC

Our engineers are implementing adjusted mitigation strategies in our North America and Europe regions to continue to balance traffic and manage performance.

Error rates and latency have improved, although customers may still experience intermittent periods of performance impact as traffic engineering continues to be deployed.

 
23 July 2024, 16:37 UTC

Engineering has implemented mitigation strategies and has confirmed a gradual recovery in our North America and Europe regions. 

We are closely monitoring performance in these regions as a top priority as this event continues and will provide a final update once customer and end user experience has been fully restored.

 
23 July 2024, 23:52 UTC

Engineering has confirmed that Europe and North America regions have been fully restored. Customers may have experienced elevated errors and latency from 08:00 to 16:37 UTC.

This incident is resolved.

Affected customers would 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

Platform North America Los Angeles (BUR)
 
25 June 2024, 07:13 UTC

Fastly Engineers detected a performance impacting event affecting the Los Angeles (BUR) data center.

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

Platform North America Los Angeles (BUR) Palo Alto (PAO)
 
04 June 2024, 02:00 UTC

We are investigating elevated errors to our Palo Alto (PAO), Los Angeles (BUR) Point of Presence (POP).

 
04 June 2024, 03:01 UTC

Our engineers have identified the contributing factor and are applying a fix to our Los Angeles (BUR), Palo Alto (PAO) Point of Presence (POP).

All other locations and services are unaffected.

 
04 June 2024, 03:10 UTC

Engineering has confirmed the impact to Los Angeles (BUR), Palo Alto (PAO) Point of Presence (POP) has been mitigated.

 
04 June 2024, 03:19 UTC

Engineering has confirmed that Los Angeles (BUR), Palo Alto (PAO) Point of Presence (POP) has been fully restored. Customers may have experienced increased latency and timeouts from 02:00 to 02:50 UTC.

This incident is resolved.

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

Platform North America Asia Oceania Melbourne (MEL) Seoul (ICN) Tokyo (TYO) Los Angeles (BUR)
 
22 May 2024, 17:38 UTC

We are investigating elevated errors to our Melbourne (MEL), Seoul (ICN), Tokyo (TYO), Los Angeles (BUR) Points of Presence (POPs).

 
22 May 2024, 18:23 UTC

Our engineers have identified the contributing factor and are applying a fix to our Melbourne (MEL), Seoul (ICN), Tokyo (TYO), Los Angeles (BUR) POPs.


 
22 May 2024, 18:32 UTC

Engineering has confirmed the impact to Melbourne (MEL), Seoul (ICN), Tokyo (TYO), Los Angeles (BUR) POPs has been mitigated.

 
22 May 2024, 18:36 UTC

Engineering has confirmed that Melbourne (MEL), Seoul (ICN), Tokyo (TYO), Los Angeles (BUR) POPs have been fully restored. Customers may have experienced elevated errors and latency from 17:38 to 18:13 UTC.

This incident is resolved.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

11 December 2023, 23:39 UTC
Platform North America Los Angeles (BUR)
 
11 December 2023, 23:39 UTC

We are investigating elevated errors to our Los Angeles (BUR) Point of Presence (POP). 

 
11 December 2023, 23:42 UTC

Our engineers have identified the contributing factor and are applying a fix to Los Angeles (BUR) POP.


 
12 December 2023, 00:21 UTC

Engineering has confirmed the impact to Los Angeles (BUR) POP has been mitigated.

 
12 December 2023, 00:45 UTC

Engineering has confirmed that Los Angeles (BUR) POP has been fully restored. Customers may have experienced increased latency and 5xx errors from 22:57 to 23:30 UTC.

This incident is resolved.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

31 October 2023, 15:22 UTC
Platform North America Los Angeles (BUR)
 
31 October 2023, 15:22 UTC

We're investigating possible performance impact affecting the Los Angeles (BUR) data center. Traffic is currently being rerouted from the impacted data center. 

All other locations and services are unaffected.

 
31 October 2023, 15:58 UTC

This issue has been identified and a fix is being implemented. 

 
31 October 2023, 16:38 UTC

Fastly has deployed traffic engineering to restore network service performance for our customers.

We are continuing to deploy mitigations to fully restore our BUR POP. Traffic remains rerouted to other nearby POPs.

We will update our status page once BUR has been fully restored. 

 
31 October 2023, 20:31 UTC

Customers who experienced impact at the start of this incident would have experienced elevated error rates and latency in our BUR POP from 15:12 to 15:15 UTC.

Our BUR POP has been restored and customer traffic is being gradually returned to their pre-incident routes.

 
31 October 2023, 21:17 UTC

Our BUR POP experienced a power outage, caused by third party service provider maintenance. We temporarily rerouted customer traffic to nearby POPs to prevent further impact to our customers and their end users while mitigations were deployed on-site.

This incident is resolved, and network availability in our BUR POP has been fully restored.

29 June 2023, 18:46 UTC
Platform North America Europe Amsterdam (AMS) Brussels (BRU) Ashburn (IAD) Copenhagen (CPH) Dublin (DUB) Frankfurt (FRA) Frankfurt (HHN) Atlanta (PDK) Helsinki (HEL) Boston (BOS) London (LCY) Calgary (YYC) London (LON) Chicago (CHI) London (LHR) Lisbon (LIS) Madrid (MAD) Manchester (MAN) Marseille (MRS) Milan (LIN) Milan (MXP) Columbus (CMH) Oslo (OSL) Columbus (LCK) Munich (MUC) Palermo (PMO) Dallas (DFW) Denver (DEN) Paris (CDG) Detroit (DTW) Paris (PAR) Rome (FCO) 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)
 
29 June 2023, 18:46 UTC

We're currently investigating performance impacts in Europe, North America.

All other locations and services are unaffected.

 
29 June 2023, 19:56 UTC

This issue has been identified and a fix is being implemented. 

 
29 June 2023, 21:54 UTC

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

 
29 June 2023, 23:54 UTC

This incident has been resolved.

Platform North America Los Angeles (BUR)
 
06 March 2023, 18:13 UTC

Fastly Engineers detected a performance impacting event affecting the Los Angeles (BUR),Los Angeles (LGB) data center.

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

 
06 March 2023, 20:41 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.