New York (NYC)

Platform North America New York (NYC) New York (LGA) Ashburn (IAD)
 
31 March 2026, 22:24 UTC

We are investigating elevated errors to our Ashburn (IAD), New York (LGA), New York (NYC) (service/Point of Presence (POP)).

All other products and services are unaffected by this incident.

 
31 March 2026, 22:28 UTC

Our engineers have identified  (an/a)   (additional or different)  contributing factor and are developing an adjusted mitigation strategy to Ashburn (IAD), New York (LGA), New York (NYC)  (service/POP)  .

(All other locations and services are unaffected.)

 
31 March 2026, 22:31 UTC

Our engineers believe they have identified contributing factor causing the issue impacting the   Ashburn (IAD), New York (LGA), New York (NYC) status page component  .

We are now developing a fix, and will post a new update once it has been fully implemented and we see signs of recovery.

All other products and services are unaffected by this incident.

 
31 March 2026, 22:32 UTC

Engineering has confirmed the impact to Ashburn (IAD), New York (LGA), New York (NYC) (service/POP) has been mitigated.

 
31 March 2026, 22:39 UTC

During this incident, customers may have experienced elevated errors and timeouts from 8:55 to 10:30 UTC.

This incident is resolved.

For more information about this retrospective stat us post, please reach out to Support through https://support.fastly.com .

Platform North America New York (NYC)
 
06 February 2026, 20:08 UTC

Fastly Engineers detected a performance impacting event affecting the New York (NYC) data center.

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

06 February 2026, 19:30 UTC
Platform North America New York (NYC)
 
06 February 2026, 19:30 UTC

We're investigating possible performance impact affecting the New York (NYC) data center.

All other locations and services are unaffected

Status Post, Created Date/Time:   2026-02-06 19:45:31 UTC    2026-02-06 19:45:31 UTC



Note:  Our Customer Escalation Management team will update the start date and time of this 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.

 
06 February 2026, 19:47 UTC

Our engineers have identified the contributing factor and are applying a fix to our New York (NYC) POP.

All other locations and services are unaffected.

 
06 February 2026, 19:50 UTC

Engineering has confirmed the impact to New York (NYC) POP has been mitigated.

 
06 February 2026, 19:55 UTC

Engineering has confirmed that New York (NYC) POP has been fully restored. Customers may have experienced elevated errors and latency from 19:30 to 19:55 UTC.

This incident is resolved.

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

03 February 2026, 19:32 UTC
Platform North America New York (NYC)
 
03 February 2026, 19:32 UTC

We're investigating possible performance impact affecting the New York (NYC) data center.

All other locations and services are unaffected

Status Post, Created Date/Time: 2026-02-03 19:41:24 UTC  2026-02-03 19:41:24 UTC



Note: Our Customer Escalation Management team will update the start date and time of this 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.

 
03 February 2026, 20:06 UTC

This event has been resolved.

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

21 January 2026, 22:38 UTC
Platform North America New York (NYC)
 
21 January 2026, 22:38 UTC

We're investigating possible performance impact affecting the New York (NYC) data center.

All other locations and services are unaffected

Status Post, Created Date/Time: 2026-01-21 22:42:21 UTC  2026-01-21 22:42:21 UTC



Note: Our Customer Escalation Management team will update the start date and time of this 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.

 
06 February 2026, 19:26 UTC

Test completed. This event has been resolved.

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

13 August 2025, 00:30 UTC
Platform North America New York (NYC)
 
13 August 2025, 00:30 UTC

We're investigating possible performance impact affecting the New York (NYC) data center.

All other locations and services are unaffected.

Status Post, Created Date/Time: 0001-01-01 00:00:00 UTC 0001-01-01 00:00:00 UTC



Note:  Our Customer Escalation Management team will update the start date and time of this 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.

 
13 August 2025, 01:03 UTC

Our engineers have identified the contributing factor and are applying a fix to our New York (NYC) POP.

All other locations and services are unaffected.

 
13 August 2025, 01:08 UTC

Engineering has confirmed the impact to New York (NYC) POP has been mitigated.

 
13 August 2025, 01:10 UTC

Engineering has confirmed that New York (NYC) POP has been fully restored. Customers may have experienced elevated errors and latency from 00:30 to 01:09 UTC.

This incident is resolved.

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

Platform North America New York (NYC)
 
12 August 2025, 23:36 UTC

Fastly Engineers detected a performance impacting event affecting the New York (NYC) data center.

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

16 July 2025, 17:00 UTC
Platform North America New York (NYC)
 
16 July 2025, 17:00 UTC

Fastly will be performing scheduled maintenance on our New York (NYC) data center from 16 July 2025, 17:00 UTC - 16 July 2025, 17:10  UTC.

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

 
16 July 2025, 17:01 UTC

The maintenance is currently in progress. 

 
16 July 2025, 17:10 UTC

The scheduled maintenance has been completed.

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

Platform North America New York (NYC) Vancouver (YVR)
 
05 June 2025, 08:34 UTC

We're investigating possible performance impact affecting the Vancouver (YVR), New York (NYC) data center.

All other locations and services are unaffected

Status Post, Created Date/Time: 0001-01-01 00:00:00 UTC  0001-01-01 00:00:00 UTC



Note: Our Customer Escalation Management team will update the start date and time of this 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 June 2025, 08:35 UTC

TEST completed. This event has been resolved.

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

Platform North America New York (NYC) Vancouver (YVR)
 
14 April 2025, 14:10 UTC

We're investigating possible performance impact affecting the New York (NYC) Vancouver (YVR) data center.

All other locations and services are unaffected

Status Post, Created Date/Time: 0001-01-01 00:00:00 UTC  0001-01-01 00:00:00 UTC



Note: Our Customer Escalation Management team will update the start date and time of this 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.

 
14 April 2025, 14:21 UTC

TEST Completed - This event has been resolved.

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