Cronologia delle interruzioni di Xero Developer

We are aware our API customers trying to integrate or use the Xero API are experiencing issues. Our team is investigating this with urgency.

We're seeing recovery of our systems, and are continuing to investigate this issue.

Our team has resolved the issue impacting customers. Xero is now stable and customers should be able to use the platform normally. Our engineering teams will continue to monitor closely to ensure everything remains on track. We apologise for any inconvenience this has caused and appreciate your patience during this time.

Our team has resolved a recent outage our customers experienced from 11:02pm-11:07pm UTC. Xero is now stable and customers should be able to use the platform normally. Our engineering teams will continue to monitor closely to ensure everything remains on track. We apologise for any inconvenience this has caused and appreciate your patience during this time.

We're aware of an outage affecting customers between 12:21 and 12:24 AM UTC. Xero is now stable and operating normally. We're sorry for the disruption, particularly given the recent outages. Our engineering team is monitoring closely and will update this page if anything changes.

Xero is now stable and all customers should be able to use the platform normally. We have not observed any further disruption since our last update and are confident the platform is operating as expected. We sincerely apologise for the series of incidents over the past week and the impact this has had on your business. We know how much you rely on Xero, and we did not meet the standard you deserve.

Some customers continue to experience slowness and issues when accessing the API with Xero due to an global issue with Amazon Web Services (AWS). AWS is a Xero third-party provider, and are working to rectify with urgency. Some customers can successfully login to Xero and we are monitoring. We thank customers for their patience.

We are continuing to work on resolving the impacts of the AWS issue, and some customers are successfully connecting with Xero APIs. We are monitoring the results. Customers may still experience general slowness and errors. We appreciate your ongoing patience during this time. Status Last Reviewed: 2:44 UTC

Our technical teams have observed a return of normal services and we're monitoring for any remaining impact. We'll continue to monitor this issue for our customers, and want to thank you for your patience during this time. Status Last Reviewed: 5:09 UTC

Status Last Reviewed: 8:48 UTC

We’re aware of an issue preventing some connections to Xero’s Public APIs. This is related to an issue with our third-party provider, Amazon Web Services (AWS), who are investigating with urgency. Status Last Reviewed: 9.38am UTC

Some customers are now successfully connecting to Xero’s Public APIs. AWS has reported recovery across most of their impacted services. We thank customers for their patience. Status Last Reviewed: 11.36am UTC

Our team has resolved the issue impacting customers connecting to Xero’s Public APIs. This related to an issue affecting our third party supplier, Amazon Web Services (AWS). This issue has now been resolved. We thank customers for their patience during this time.

We are aware API users may not be receiving webhooks as expected. Our team is investigating this with urgency. Status Last Reviewed: 12:37am UTC.

We are continuing to investigate this issue.

We have identified what is impacting API users may from receiving webhooks as expected. This is our top priority and we will update you as soon as we can. Status Last Reviewed: 1:40am UTC

Our team has implemented a fix and we are currently monitoring the results. Status Last Reviewed: 1:46am UTC

Our team has resolved the issue impacting some customers trying to received webhooks via the Xero API. We apologise for any inconvenience this has caused. This was due to a certificate issue, and we've restored service.

We are currently investigating an issue with the AuthEventId that is returned when using the Connections endpoint. Apps may encounter issues when a user attempts to authorise an app connection.

Our team has resolved the issue impacting a user attempts to authorise an app connection. This was caused by a recent release and has now been rolled back by our product team. Any users that were unable to connect prior to the resolution should now be able to connect. If they are still experiencing issues we would ask you to advise them to: Navigate to the Settings > Connected apps screen within Xero Locate your app Click the disconnect button They should then re-attempt the connection process from within your interface. We apologise for any inconvenience caused.

We have identified what is preventing global API users trying to receive webhooks. We understand that as a result you will not receive notifications of updates. This is our top priority and we will update you as soon as we can. Status Last Reviewed: 11:32pm UTC

Our team has implemented a fix and we are currently monitoring the results. Status Last Reviewed: 11:38pm UTC

Our team has resolved the issue impacting global API users trying to retrieve webhooks. We apologise for any inconvenience this has caused. This was caused by network instability and we've since restored service

We are aware that some customers might be getting delayed or doubled Webhook deliveries. We are investigating this with urgency.

Our team has resolved the issue causing some customers to have delayed or doubled Webhook deliveries. We apologise for any inconvenience caused.

Our team has resolved the issue impacting some API customers who experienced a delay in trying to push transactions in Xero. We apologise for any inconvenience this has caused. This related to poor network connectivity and our team has restored service.

We are aware that Webhooks are currently not being delivered. We are investigating this with urgency.

Our team has implemented a fix and Webhook delivery has resumed. We are continuing to monitor the results. Status Last Reviewed: 7:33pm UTC.

Our team has resolved the issue impacting Webhooks from being delivered. A previous issue triggered a limit error, resulting in a full outage. We apologise for any inconvenience.

We are adding support for a new form of Leave Type(LeaveType) in UK Payroll called Statutory Neonatal Care Pay (StatutoryNeonatalCarePay). This was released earlier this week but not within the public SDKs which may have caused some customers to encounter SDK errors. We have temporarily rolled back the release whilst we work to update the SDKs as a matter of urgency. Status Last Reviewed: 16:50 UTC

The SDKs have now been updated, we would advise any apps that use the UK Payroll API to update to the latest version as soon as possible. https://developer.xero.com/documentation/sdks-and-tools/libraries/overview/. Status Last Reviewed: 15:51 UTC

Our team has resolved the issue where UK customers experienced errors attempting to add the Leave Type of Statutory Neonatal Care Pay. This was caused by a release which caused customers to experience SDK errors. We apologise for any inconvenience.

We are aware that some customers trying to use Xero Files are experiencing errors or poor performance. This relates to Xero features that uses files including (but not limited to) expenses, Workpapers, emailing invoices and downloading bills. Our team is investigating this with urgency.

Our team has implemented a fix and we are currently monitoring the results. Status Last Reviewed: 12:04 UTC.

This was caused by a product release, which has been rolled back to resolve customer impact. We apologise for any inconvenience caused.

We have identified what is preventing API customers trying to pull or push information into Quotes in Xero. This is our top priority and we will update you as soon as we can. Status Last Reviewed: 12:38am UTC

Our team has resolved the issue impacting customers trying to update quotes in Xero via the API. We apologise for any inconvenience this has caused.

We are aware customers are experiencing errors when calling Xero's public API. Our team is investigating this with urgency. Status Last Reviewed: 10:10pm UTC

Our team has resolved the issue impacting customers trying to call Xero's public API. We apologise for any inconvenience this has caused. This was caused by a product release, and the team implemented a fix to resolve impact.

We are aware customers trying to operate third-party apps may be experiencing errors. Our team is investigating this with urgency. Status Last Reviewed: 12:05am UTC

Our team has resolved the issue impacting customers trying to operate third-party apps. We apologise for any inconvenience this has caused. This was caused by a product release which has been rolled back to resolve the issue. We apologise for the inconvenience caused.

We have identified what is impacting global customers trying to utilise the Xero Practice Manager APIs. This is our top priority and we will update you as soon as we can. Status Last Reviewed: 3:45am UTC

Our team has implemented a fix and we are currently monitoring the results. Status Last Reviewed: 3:55am UTC

Our team has resolved the issue impacting global customers trying utilise the Xero Practice Manager APIs. We apologise for any inconvenience this has caused. A product release caused this feature to become unavailable. We've rolled back the release and services are back to normal.

We are aware global third party developers trying to edit configurations via Xero's Public API are experiencing an error. Our team is investigating this with urgency. Status Last Reviewed: 10:47pm UTC

We have identified what is preventing global third party developers trying to edit configurations via Xero's Public API. This is our top priority and we will update you as soon as we can. Status Last Reviewed: 1:28am UTC

Our team has implemented a fix and we are currently monitoring the results. Status Last Reviewed: 1:56am UTC

We are continuing to monitor for any further issues. Please note that any changes made between 10pm UTC 31st July and today may not have been reflected in cache.

Our team has resolved the issue impacting global third party developers trying to edit configurations via Xero's Public API. We apologise for any inconvenience this has caused.

We have identified what is impacting some customers trying to log in and navigate Xero. This is related to an issue with AWS (a Xero third-party provider) and the AWS team are investigating with urgency. This is our top priority and we will update you as soon as we can. Status Last Reviewed: 1:38am UTC.

We are aware some customers are now able to login to Xero. Our teams are continuing to investigate this issue with urgency and we’re closely working with our third-party provider, AWS. We thank customers for their patience and apologise for any inconvenience. Status Last Reviewed: 3:23am UTC.

We are now seeing recovery across our systems. Customers should be able to log in and navigate through Xero as expected. We thank customers for their patience during this time. Status Last Reviewed: 4:35am UTC

We are now seeing recovery across our systems. Customers should be able to log in and navigate through Xero as expected. We thank customers for their patience during this time. This was caused by an issue relating to AWS, one of Xero's third-party providers. We apologise for the inconvenience.

We are aware that App Partners are currently unable to update their App listings. Our team is in the process of putting in place a fix for this issue. We apologise for the inconvenience this causes.

Our team has resolved this issue which related to a prior release which has been reverted. We apologise for any inconvenience this has caused.

Our Product team were aware of an issue with the Payment Services API endpoint on Monday 13 February 2024 where errors were sent for call that should have been successful. This issue was found to be due to a recent release and was resolved Tuesday 14 February AM.

We're aware some customers are experiencing an elevated level of API errors and latency. Our technical team are investigating this as a matter of urgency.

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

This incident has been resolved. We apologise for any inconvenience caused.