Xero incident

Philippines - Some customers may be experiencing errors in Xero due to an internet service connection issue

Major Resolved View vendor source →

Xero experienced a major incident on September 23, 2025 affecting Xero Platform and Settings, lasting 8h 13m. The incident has been resolved; the full update timeline is below.

Started
Sep 23, 2025, 11:11 PM UTC
Resolved
Sep 24, 2025, 07:24 AM UTC
Duration
8h 13m
Detected by Pingoru
Sep 23, 2025, 11:11 PM UTC

Affected components

Xero Platform and Settings

Update timeline

  1. investigating Sep 23, 2025, 11:11 PM UTC

    We are aware some Asia customers are experiencing errors trying to login to Xero. Our team is investigating this with urgency. Status Last Reviewed: 11.10 pm UTC

  2. investigating Sep 23, 2025, 11:11 PM UTC

    We are continuing to investigate this issue.

  3. investigating Sep 23, 2025, 11:24 PM UTC

    We are continuing to investigate this issue.

  4. investigating Sep 23, 2025, 11:46 PM UTC

    Our product team is looking into this, and we’ll provide an update as soon as possible

  5. identified Sep 24, 2025, 12:38 AM UTC

    We’ve identified some Xero customers in the Philippines may be experiencing errors in Xero due to an internet service connection issue. We are investigating with the internet service provider and will update customers as soon as possible. Status Last Reviewed:

  6. identified Sep 24, 2025, 04:34 AM UTC

    We’ve identified some Xero customers in the Philippines may be experiencing errors in Xero due to an internet service connection issue. We are investigating with the internet service provider and will update customers as soon as possible. Status Last Reviewed:

  7. identified Sep 24, 2025, 07:22 AM UTC

    We've contacted the internet service provider for more information. Customers can access Xero via mobile data or another internet service provider as normal. Status Last Reviewed:

  8. identified Sep 24, 2025, 07:23 AM UTC

    We are continuing to work on a fix for this issue.

  9. resolved Sep 24, 2025, 07:24 AM UTC

    This incident has been resolved.