Xero Error 502 Bad Gateway

Let’s Dive in…

How to Fix Xero Error=502 Bad Gateway

 

Schedule a call to fix XERO Errors

* All trademarks and logos are the property of their respective owners. Images for visual reference only.

Xero Error · HTTP 5xx Series

How to Fix Xero Error 502 Bad Gateway

Xero displays: "502 Bad Gateway" — the browser shows a blank or error page instead of loading Xero.

A 502 is almost always a server-side problem on Xero's end — a gateway server received an invalid response from Xero's backend. At QuickFix Bookkeeping, the first step is always to check status.xero.com to confirm whether Xero is experiencing a known outage. If it's a Xero outage — wait. If status.xero.com shows all green — the issue may be local and fixable on your side.

The QuickFix Bookkeeping Distinction — 502 vs 503 vs 500 in Xero

Xero's 5xx error codes all show as server errors but mean different things — identifying which gives you the right action.

502 — this page

Bad Gateway: a Xero proxy server received an invalid response from the Xero backend. Often transient — a brief backend spike, a deployment in progress, or a routing issue. Usually resolves in minutes to an hour.

503

Service Unavailable: Xero is intentionally down for maintenance or at capacity. Status.xero.com will show an incident. Nothing to do but wait for Xero to restore service.

500

Internal Server Error: a Xero backend server encountered an unexpected error. Also server-side. Often caused by a specific action (submitting a form, running a report) that triggers a code error.

When Xero 502 occurs at specific times:

502 in Xero often appears during peak usage periods — payroll processing runs (especially pay day mornings), month-end reconciliation, and tax filing dates — when Xero's backend load is highest. 502 also appears during partial outages affecting specific features (e.g., payroll working but reports 502-ing). If you're getting 502 only on one Xero feature but others work — it's a partial backend issue. Check status.xero.com for any partial outage notices and contact Xero support to report the specific feature affected.

What Causes Xero Error 502?

Xero Backend Temporarily Overloaded

Most common cause — Xero's application or database servers are temporarily overwhelmed (typically during peak periods like payroll runs or month-end). The gateway proxy gets no valid response before its timeout and returns 502. These resolve on their own within minutes to an hour. Refreshing every few minutes is the appropriate response.

Xero Deployment or Maintenance (Unannounced)

Xero regularly deploys updates to its platform, sometimes causing brief 502 periods during the deployment itself. These are typically not pre-announced on the status page and resolve within minutes. A deployment-related 502 usually affects all users simultaneously and clears quickly.

Your Browser Cache Serving a Stale 502 Response

Browsers can cache error responses. If Xero returned a 502 during a brief outage, some browsers save this cached error and continue serving it even after Xero recovers. A hard refresh (Ctrl+F5 / Cmd+Shift+R) or clearing the browser cache forces your browser to fetch a fresh response from Xero's servers.

Local DNS Resolution Issue

Your local DNS cache may have a stale or incorrect entry for Xero's servers. If your ISP's DNS is returning an incorrect IP for xero.com, your browser connects to the wrong server — which returns 502. Flushing the DNS cache or temporarily switching to Google DNS (8.8.8.8) confirms whether DNS is the issue.

Browser Extension Interfering

Ad blockers, VPN extensions, proxy extensions, or security plugins can intercept Xero's network requests and return a 502-like response to the browser. Opening Xero in an incognito window (which disables extensions by default) immediately confirms this — if Xero loads in incognito, an extension is the cause.

Corporate Firewall or Proxy Misconfiguration

Corporate firewalls or outbound proxies in office environments can intercept HTTPS traffic to Xero and return a 502 when their own SSL inspection fails. If Xero works on mobile data but not on office WiFi — the corporate network/firewall is the issue. Your IT team needs to whitelist Xero's domains.

How to Fix Xero Error 502

Check status.xero.com first. If Xero shows an active incident — wait. If the status page shows all green — work through these steps.

METHOD 1 Check Status Page + Hard Refresh + Wait Do this first — takes 60 seconds
1

Go to status.xero.com in a new browser tab. Check if there is an active incident for your region. If Xero shows a degraded or down status — this is a Xero-side issue. Check back periodically and wait for Xero to resolve it. Posting to Xero's Twitter/X (@XeroSupport) or their support chat with the status page reference speeds up a response if the status page hasn't been updated yet.

2

Hard refresh (if status page shows all clear): Press Ctrl+F5 (Windows) or Cmd+Shift+R (Mac) on the Xero page. This bypasses the cache and forces a fresh request. If Xero loads — a cached 502 response was the cause. If it doesn't — try Method 2.

METHOD 2 Try Incognito Mode + Different Browser + Different Device Browser extension or local cache issue
1

Incognito test: Press Ctrl+Shift+N (Chrome) or Ctrl+Shift+P (Firefox) → open Xero in the incognito window. Incognito disables extensions and ignores the regular cache. If Xero loads in incognito — a browser extension is causing the 502. Disable extensions one by one to find the culprit.

2

Different browser/device test: Try accessing Xero in a completely different browser (if you use Chrome, try Firefox). Try on a mobile device using mobile data (not office WiFi). If Xero loads on mobile data but not office WiFi — the corporate network or proxy is filtering Xero traffic.

METHOD 3 Clear Browser Cache + Flush DNS Stale cached response or corrupted DNS entry
1

Clear browser cache: Chrome → Settings → Privacy and Security → Delete browsing data → check Cached images and files + Cookies → All time → Delete data. Reopen Chrome and try Xero.

2

Flush DNS (Windows): press Windows → type cmd → Run as administrator → type ipconfig /flushdns → Enter. Mac: Terminal → sudo dscacheutil -flushcache. Retry Xero. Also restart your router (unplug 30 seconds) to clear router-level DNS cache.

METHOD 4 Change DNS Servers + Contact Xero Support Persistent 502 — ISP DNS or ongoing Xero issue
1

Switch to Google DNS temporarily: Windows → Settings → Network & Internet → Change adapter options → right-click your connection → Properties → IPv4 → Use the following DNS server addresses: 8.8.8.8 (preferred) and 8.8.4.4 (alternate) → OK. Retry Xero. If Xero loads — your ISP's DNS has a bad entry for Xero. Revert DNS after the issue resolves or keep Google DNS.

2

Contact Xero support (if 502 persists for more than an hour and all above pass): go to help.xero.com → contact support. Provide: your Xero organisation name, the specific URL showing 502, the time the error started, your region, and whether other users in your organisation are affected. Xero support can check if there's a backend issue specific to your organisation or data centre region not yet showing on the status page.

Quick Reference

Your situation Likely cause Action
502 just appeared — haven't checked status Possibly Xero-side outage Method 1 — check status.xero.com first
Status.xero.com shows all green Local cache or extension Method 2 — incognito test
Works on mobile data, not office WiFi Corporate proxy/firewall Ask IT to whitelist Xero domains
502 for >1 hour, all local checks pass Xero regional or account-level issue Method 4 — contact Xero support

Frequently Asked Questions

Is Error 502 my fault or Xero's fault?
Almost always Xero's. A 502 is specifically a server-to-server communication error — Xero's own gateway servers are failing to get a response from Xero's backend. As a user you have no access to Xero's server infrastructure. The rare local causes are a browser extension hijacking the request, a stale cached error response in your browser, or a corporate proxy intercepting HTTPS traffic. The incognito window test quickly confirms whether it's one of these local causes — if Xero loads in incognito, it's local; if it doesn't, it's Xero's servers.
How long do Xero 502 errors typically last?
Most Xero 502 errors caused by backend spikes or brief deployments resolve within a few minutes to 30 minutes. Peak-period 502s (during payroll runs or month-end processing) can last up to a few hours as Xero's backend manages the load. Full outages shown on status.xero.com typically resolve within 1–4 hours based on Xero's historical incident resolution times. If you're seeing 502 for more than 2 hours with no incident on the status page, contact Xero support — you may be experiencing an undiscovered regional or account-specific issue.
What's the difference between Xero 502 and Xero 503?
Both are server-side errors but with different meanings. A 503 (Service Unavailable) is Xero saying "I know you're trying to reach me and I'm intentionally not accepting requests right now" — caused by planned maintenance, deliberate capacity throttling, or an overload protection mechanism. A 502 (Bad Gateway) is Xero's proxy/gateway server saying "I tried to reach Xero's backend to fulfill your request, but the backend gave me garbage back or didn't respond" — it's an unexpected failure rather than an intentional refusal. In practice for users, both mean "Xero isn't loading right now" and both appear on the status page when widespread. The distinction matters for Xero's engineering team diagnosing the issue, not for users trying to get back into Xero.

Related Xero Errors

Xero 502 blocking your payroll run or month-end close?

Let QuickFix Bookkeeping Keep Your Books Moving.

Certified Xero & Intuit ProAdvisors

When Xero outages block your payroll deadline or month-end close, we can help you navigate workarounds, liaise with Xero support, and ensure your books stay accurate until service is restored.

Book a Free 30-Minute Consultation

No obligation. Same-day response.