Fastly Outage History
Fastly is up right nowPingoru has recorded 173 incidents for Fastly: 173 in the last 12 months and 50 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 81 | 372 of 720 (52%) |
| May 2026 | 12 | 30 of 744 (4%) |
| June 2026 | 18 | 86 of 720 (12%) |
| July 2026 | 13 | 360 of 744 (48%) |
| August 2026 | 18 | 433 of 744 (58%) |
| September 2026 | 17 | 353 of 720 (49%) |
| October 2026 | 13 | 433 of 584 (74%) |
Incidents, newest first
Notice July 2, 2026 Resolved - Elevated errors and latency at LCY and LHR POPs 1m Europe, London (LCY), London (LHR), Platform and 4 more
Started Jul 02, 2026, 04:46 PM UTC· resolved Jul 02, 2026, 04:47 PM UTC
- investigating Jul 02, 2026, 04:46 PM UTC
Between 13:00 UTC and 19:12 UTC on June 25, 2026, customers routing traffic through our London City (LCY) and London Heathrow (LHR) Points of Presence (POPs) may have experienced elevated Time to First Byte (TTFB), request timeouts, and HTTP 503 errors. Customers using LHR as a shield origin — including those routing through LCY — were most affected. The highest concentration of errors occurred between approximately 16:00 and 16:40 UTC. Service degradation began to improve at approximately 16:40 UTC and was fully resolved by 19:12 UTC. Customer impact: Customers in the affected traffic paths may have observed increased latency, elevated error rates, and in some cases failed requests during this window. Current status: This incident is fully resolved. All services at LCY and LHR are operating normally. If you have questions about how this incident affected your services, please contact our support team by emailing us at [email protected].
- resolved Jul 02, 2026, 04:47 PM UTC
This event has been resolved.
Notice July 2, 2026 Retrospective: Impacted Performance for API Services 17m Fastly Control Panel, API & Configuration Management, API Services, Fastly and 3 more
Started Jul 02, 2026, 06:50 AM UTC· resolved Jul 02, 2026, 07:07 AM UTC
- investigating Jul 02, 2026, 06:50 AM UTC
Fastly Engineers detected a performance impacting event affecting our API Services. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
- resolved Jul 02, 2026, 07:07 AM UTC
Engineering has confirmed that API Services has been fully restored. Customers may have experienced errors when using our API from 06:50 to 07:07 UTC. This incident is resolved. Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above. 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. Status Post, Created Date/Time: 2026-07-02 07:32:38 UTC
Notice June 30, 2026 Mumbai (QAI) Rerouted Traffic 8d 18h Mumbai (QAI), Platform, Platform, India and 8 more
Started Jun 30, 2026, 07:16 AM UTC· resolved Jul 09, 2026, 01:58 AM UTC
- investigating Jun 30, 2026, 07:16 AM UTC
Traffic in Mumbai (QAI) has been temporarily rerouted. All other locations and services are unaffected.
- resolved Jul 09, 2026, 01:58 AM UTC
This event was resolved and POP fully restored at 01:58 AM earlier today.
Major June 30, 2026 Buenos Aires (EZE) with Possible Impact 22m South America, Buenos Aires (EZE), Platform, South America and 7 more
Started Jun 30, 2026, 02:31 AM UTC· resolved Jun 30, 2026, 02:53 AM UTC
- investigating Jun 30, 2026, 02:31 AM UTC
We're investigating possible performance impact affecting the Buenos Aires (EZE) data center. All other locations and services are unaffected.
- investigating Jun 30, 2026, 02:43 AM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Buenos Aires (EZE) 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.
- monitoring Jun 30, 2026, 02:50 AM UTC
Engineering has deployed a fix and have confirmed a gradual recovery to Buenos Aires (EZE) POP. We will continue to monitor until we’ve confirmed that customer experience has been fully restored. All other networks and services were unaffected by this incident.
- resolved Jun 30, 2026, 02:53 AM UTC
Engineering has confirmed that Buenos Aires (EZE) POP has been fully restored. Customers may have experienced elevated errors from 02:31 to 02:53 UTC. This incident is resolved. 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. Status Post, Created Date/Time: 2026-06-30 02:43:11 UTC
Notice June 30, 2026 Retrospective: Impacted Performance in Santiago (SCL) 13m South America, Santiago (SCL), Platform, South America and 7 more
Started Jun 30, 2026, 01:42 AM UTC· resolved Jun 30, 2026, 01:55 AM UTC
- investigating Jun 30, 2026, 01:42 AM UTC
Fastly Engineers detected a performance impacting event affecting the Santiago (SCL) data center. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
- resolved Jun 30, 2026, 01:55 AM UTC
Customers may have experienced elevated errors from 01:42 to 01:55 UTC. For more information about this retrospective status post, please reach out to Support through https://support.fastly.com.
Major June 30, 2026 Impact to NGWAF@edge Services 31m Next-Gen WAF (NGWAF), Security, Security
Started Jun 30, 2026, 01:23 AM UTC· resolved Jun 30, 2026, 01:54 AM UTC
- investigating Jun 30, 2026, 01:23 AM UTC
We're currently investigating an issue with our Next-Gen WAF (NGWAF) service that is causing audit log events to not appear in the logs. This does not affect functionality of NGWAF services. All other services are unaffected.
- investigating Jun 30, 2026, 01:50 AM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Next-Gen WAF (NGWAF) 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.
- resolved Jun 30, 2026, 01:54 AM UTC
During this incident, customers may have experienced audit log events not appearing in the logs between June 27th 21:23 UTC to June 30th 01:54 UTC. This incident is resolved. For more information about this retrospective status post, please reach out to Support through https://support.fastly.com.
Notice June 29, 2026 Retrospective: Impacted Performance in Lima (LIM) 9m South America, Lima (LIM), Platform, South America and 7 more
Started Jun 29, 2026, 05:43 PM UTC· resolved Jun 29, 2026, 05:52 PM UTC
- investigating Jun 29, 2026, 05:43 PM UTC
Fastly Engineers detected a performance impacting event affecting the Lima (LIM) data center. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
- resolved Jun 29, 2026, 05:52 PM UTC
During this incident, customers may have experienced elevated errors from 17:43 to 17:52 UTC. This incident is resolved. For more information about this retrospective status post, please reach out to Support through https://support.fastly.com.
Notice June 26, 2026 Retrospective: Fastly Control Panel and API Performance Issues 1h 14m Fastly Control Panel, API & Configuration Management, API Services, Configuration Management Services and 8 more
Started Jun 26, 2026, 06:05 AM UTC· resolved Jun 26, 2026, 07:19 AM UTC
- investigating Jun 26, 2026, 06:05 AM UTC
Fastly Engineers detected a performance impacting event affecting the availability of manage.fastly.com and API. CDN delivery, stats aggregation, and all other data plane services were unaffected. The issue has been resolved and we are monitoring performance closely.
- resolved Jun 26, 2026, 07:19 AM UTC
This event has been resolved.
Major June 25, 2026 Elevated Errors for Fastly Application 1h 34m Fastly Control Panel, API & Configuration Management, API Services, Configuration Management Services and 15 more
Started Jun 25, 2026, 05:25 PM UTC· resolved Jun 25, 2026, 06:59 PM UTC
- investigating Jun 25, 2026, 06:13 PM UTC
We are investigating elevated errors with product enablements in our Fastly Application. All other products and services are unaffected by this incident.
- investigating Jun 25, 2026, 06:27 PM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Fastly Application 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.
- monitoring Jun 25, 2026, 06:28 PM UTC
Engineering has confirmed the impact to Fastly Application service has been mitigated.
- resolved Jun 25, 2026, 06:59 PM UTC
Engineering has confirmed that Fastly Application service has been fully restored. Customers may have experienced failures with enablement, disablement, and configuration operations, as well as enablement checks from 17:25 to 18:22 UTC. This incident is resolved. 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. Status Post, Created Date/Time: 2026-06-25 18:15:32 UTC
Notice June 24, 2026 London (QQP) Rerouted Traffic 2d 5h Europe, London (QQP), Platform, Europe and 8 more
Started Jun 24, 2026, 02:53 PM UTC· resolved Jun 26, 2026, 08:45 PM UTC
- investigating Jun 24, 2026, 02:53 PM UTC
Traffic in London (QQP) has been temporarily rerouted. All other locations and services are unaffected.
- resolved Jun 26, 2026, 08:45 PM UTC
This event has been resolved.
Notice June 18, 2026 Third party service provider incident resulting possible delays for our support services 3h 5m Customer Services, Support Systems, Support Ticketing System, Fastly and 7 more
Started Jun 18, 2026, 04:48 PM UTC· resolved Jun 18, 2026, 07:53 PM UTC
- investigating Jun 18, 2026, 04:48 PM UTC
Our engineers have been informed that our Customer Relationship Management (CRM) provider is currently experiencing an incident. As a result, you may experience slightly delayed responses from our Support team while we implement an internal workaround and monitor this provider's incident updates. All other Fastly services remain fully operational. Our network and security products continue to deliver without disruption. We will provide an update if the situation changes.
- investigating Jun 18, 2026, 06:49 PM UTC
We have an update regarding the ongoing Informational affecting Support Ticketing System. Our provider has reported that a contributing factor has been identified and they are working on a fix. As a reminder, Fastly's core edge network and security services remain unaffected. Please continue to email [email protected] for any assistance while our standard support and CRM channels remain impacted. Updated on 18 June 2026 at 18:49 UTC
- resolved Jun 18, 2026, 07:53 PM UTC
The third party provider issue affecting Support Ticketing System services has been fully resolved. All Fastly Customer Support services and CRM systems have been restored and are operating normally. Ticket processing and standard communication channels are fully functional. We apologize for the inconvenience and appreciate your patience during this interruption to our support channels. Resolved on 18 June 2026 at 19:53 UTC
Major June 17, 2026 Elevated Errors for Bogota (BOG) 2h 5m South America, Bogota (BOG), Platform, South America and 6 more
Started Jun 17, 2026, 05:05 PM UTC· resolved Jun 17, 2026, 07:10 PM UTC
- investigating Jun 17, 2026, 05:05 PM UTC
We are investigating elevated errors to our Bogota (BOG) Point of Presence (POP). All other products and services are unaffected by this incident.
- investigating Jun 17, 2026, 06:13 PM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Bogota (BOG) 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.
- monitoring Jun 17, 2026, 06:33 PM UTC
Engineering has confirmed the impact to our Bogota (BOG) POP has been mitigated.
- resolved Jun 17, 2026, 07:10 PM UTC
Engineering has confirmed that our Bogota (BOG) POP has been fully restored. Customers may have experienced elevated errors and increased latency from 17:05 to 17:51 UTC. This incident is resolved. 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. Status Post, Created Date/Time: 2026-06-17 17:30:29 UTC
Major June 17, 2026 Elevated Errors for Lima (LIM) 2h 38m South America, Lima (LIM), Platform, South America and 5 more
Started Jun 17, 2026, 05:05 PM UTC· resolved Jun 17, 2026, 07:43 PM UTC
- investigating Jun 17, 2026, 05:05 PM UTC
We are investigating elevated errors to our Lima (LIM) Point of Presence (POP). All other products and services are unaffected by this incident.
- investigating Jun 17, 2026, 06:12 PM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Lima (LIM) 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.
- monitoring Jun 17, 2026, 06:33 PM UTC
Engineering has confirmed the impact to our Lima (LIM) POP has been mitigated.
- resolved Jun 17, 2026, 07:43 PM UTC
Engineering has confirmed that our Lima (LIM) POP has been fully restored. Customers may have experienced elevated errors and increased latency from 17:05 to 17:51 UTC. This incident is resolved. 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. Status Post, Created Date/Time: 2026-06-17 18:00:00 UTC
Notice June 11, 2026 Hong Kong (HKG) Rerouted Traffic 15m Asia, Hong Kong (HKG), Platform, Asia and 4 more
Started Jun 11, 2026, 07:25 PM UTC· resolved Jun 11, 2026, 07:40 PM UTC
- investigating Jun 11, 2026, 07:25 PM UTC
Traffic in Hong Kong (HKG) has been temporarily rerouted. All other locations and services are unaffected.
- resolved Jun 11, 2026, 07:40 PM UTC
This event has been resolved.
Notice June 11, 2026 Retrospective: Impacted Performance in Hong Kong (HKG) 1h Asia, Hong Kong (HKG), Platform, Asia and 4 more
Started Jun 11, 2026, 03:01 PM UTC· resolved Jun 11, 2026, 04:01 PM UTC
- investigating Jun 11, 2026, 03:01 PM UTC
Fastly Engineers detected a performance impacting event affecting the Hong Kong (HKG) data center. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
- resolved Jun 11, 2026, 03:20 PM UTC
This event has been resolved.
- resolved Jun 11, 2026, 04:01 PM UTC
This event has been resolved.
Notice June 6, 2026 Howrah (QAC) Rerouted Traffic 1h 56m Howrah (QAC), Platform, Platform, India and 5 more
Started Jun 06, 2026, 10:00 PM UTC· resolved Jun 06, 2026, 11:56 PM UTC
- investigating Jun 06, 2026, 10:00 PM UTC
Traffic in Howrah (QAC) has been temporarily rerouted. All other locations and services are unaffected.
- resolved Jun 06, 2026, 11:56 PM UTC
This incident has been resolved.
Major June 6, 2026 Elevated Errors for Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), Newark (EWR) 1h 35m North America, Atlanta (PDK), Dallas (DFW), Denver (DEN) and 17 more
Started Jun 06, 2026, 12:50 AM UTC· resolved Jun 06, 2026, 02:25 AM UTC
- investigating Jun 06, 2026, 01:00 AM UTC
We are investigating elevated errors to our Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), Newark (EWR) Points of Presence (POPs) All other products and services are unaffected by this incident.
- investigating Jun 06, 2026, 01:06 AM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), Newark (EWR) status page components. 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.
- investigating Jun 06, 2026, 01:53 AM UTC
The fix has been successfully deployed, and we have observed a recovery to only our DFW, DEN, MSP, and EWR POPs. Error rates and latency have returned to nominal levels and we are monitoring stability at these locations. Our engineers have identified an additional contributing factor and are developing an adjusted mitigation strategy to our MIA and PDK POPs specifically. All other locations and services are unaffected.
- monitoring Jun 06, 2026, 02:14 AM UTC
Engineering has confirmed the impact to our Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), and Newark (EWR) Points of Presence (POPs) has been mitigated.
- resolved Jun 06, 2026, 02:25 AM UTC
Engineering has confirmed that our our Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), and Newark (EWR) POPs have been fully restored. Customers may have experienced increased latency from 00:50 to 01:50 UTC at our DFW, DEN, MSP, and EWR POPs and from 00:50 to 02:13 UTC at our PDK and MIA POPs. This incident is resolved. 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. Status Post, Created Date/Time: 2026-06-06 01:01:14 UTC
Notice June 5, 2026 Retrospective: Impacted Performance in Singapore (SIN) 52m Asia, Singapore (SIN), Platform, Asia and 4 more
Started Jun 05, 2026, 12:00 PM UTC· resolved Jun 05, 2026, 12:52 PM UTC
- investigating Jun 05, 2026, 12:00 PM UTC
Fastly Engineers detected a performance impacting event affecting the Singapore (SIN) data center. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
- resolved Jun 05, 2026, 12:52 PM UTC
This incident has been resolved.
Notice June 4, 2026 Houston (IAH) Rerouted Traffic 1h 25m North America, Houston (IAH), Platform, North America and 7 more
Started Jun 04, 2026, 08:00 AM UTC· resolved Jun 04, 2026, 09:25 AM UTC
- investigating Jun 04, 2026, 08:00 AM UTC
Traffic in Houston (IAH) has been temporarily rerouted. All other locations and services are unaffected.
- resolved Jun 04, 2026, 09:25 AM UTC
This event has been resolved.
Notice June 2, 2026 Fortaleza (FOR) Rerouted Traffic 1h 33m South America, Fortaleza (FOR), Platform, South America and 5 more
Started Jun 02, 2026, 03:03 PM UTC· resolved Jun 02, 2026, 04:36 PM UTC
- investigating Jun 02, 2026, 03:03 PM UTC
Traffic in Fortaleza (FOR) has been temporarily rerouted. All other locations and services are unaffected.
- resolved Jun 02, 2026, 04:36 PM UTC
This event has been resolved.
Major May 28, 2026 Elevated Errors for Fortaleza (FOR) 51m South America, Fortaleza (FOR), Platform, South America and 5 more
Started May 28, 2026, 01:38 AM UTC· resolved May 28, 2026, 02:29 AM UTC
- investigating May 28, 2026, 01:38 AM UTC
We are investigating elevated errors to our Fortaleza (FOR) Point of Presence (POP). All other products and services are unaffected by this incident.
- resolved May 28, 2026, 02:29 AM UTC
This event has been resolved.
Notice May 21, 2026 Retrospective: Impacted Performance in Ashburn (IAD) 6m North America, Ashburn (IAD), Platform, North America and 6 more
Started May 21, 2026, 09:29 PM UTC· resolved May 21, 2026, 09:35 PM UTC
- investigating May 21, 2026, 09:29 PM UTC
Fastly Engineers detected a performance impacting event affecting the Ashburn (IAD) data center.
- resolved May 21, 2026, 09:35 PM UTC
The issue causing temporary unhealthy cache nodes was resolved, and services were fully restored. Our engineers confirmed that all cache nodes returned to a healthy state. Customers may have experienced impact between 21:29 UTC and 21:35 UTC (approximately 6 minutes). All other services and locations were unaffected by this event.
Major May 20, 2026 Elevated Errors for API Services 1h 44m Fastly Control Panel, API & Configuration Management, API Services, Fastly and 3 more
Started May 20, 2026, 06:35 PM UTC· resolved May 20, 2026, 08:19 PM UTC
- investigating May 20, 2026, 07:28 PM UTC
We are investigating an issue causing errors and timeouts for customers using the Fastly API (api.fastly.com). Our engineers are actively working to diagnose the contributing factor. We will provide another update as more information becomes available or within the next hour. All other products and services are unaffected by this incident.
- investigating May 20, 2026, 08:02 PM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the API Services 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.
- monitoring May 20, 2026, 08:18 PM UTC
Engineering has confirmed the impact to API Services has been mitigated.
- resolved May 20, 2026, 08:19 PM UTC
Our engineers have confirmed that the Fastly API (api.fastly.com) has been fully restored. Customers may have experienced elevated 503 errors, increased timeouts, or failures on API calls and Terraform builds from approximately 18:35 to 19:37 UTC. As a side effect of the API degradation, the following areas were also impacted during this period: Next-Gen WAF (NGWAF) rule and configuration updates may have been delayed in taking effect Fastly account sign-up may have experienced disruptions Fastly Support Portal functionality may have been affected Service has been fully restored. Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above. This incident is resolved. 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. Status Post, Created Date/Time: 2026-05-20 19:31:03 UTC
Major May 13, 2026 Elevated Errors for TLS Provisioning 1h 9m Domain Management, TLS Provisioning, Network Services, Domain Management and 1 more
Started May 13, 2026, 06:06 AM UTC· resolved May 13, 2026, 07:15 AM UTC
- investigating May 13, 2026, 06:54 AM UTC
We are investigating elevated errors to our TLS Provisioning feature.
- investigating May 13, 2026, 07:01 AM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the TLS Provisioning 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.
- monitoring May 13, 2026, 07:12 AM UTC
Engineering has confirmed the impact to TLS Provisioning service has been mitigated.
- resolved May 13, 2026, 07:15 AM UTC
Engineering has confirmed that our TLS Provisioning service has been fully restored. Customers may have experienced errors and timeouts when using the TLS provisioning API from 06:06 to 07:12 UTC. This incident is resolved. Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above. 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. Status Post, Created Date/Time: 2026-05-13 06:55:15 UTC
Notice May 12, 2026 Retrospective: Impacted Performance in TLS Provisioning 10m Domain Management, TLS Provisioning, Network Services, Domain Management and 1 more
Started May 12, 2026, 01:49 PM UTC· resolved May 12, 2026, 01:59 PM UTC
- investigating May 12, 2026, 01:49 PM UTC
Fastly Engineers detected a performance impacting event affecting the TLS Provisioning service. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
- resolved May 12, 2026, 01:59 PM UTC
This event has been resolved.