Is Lazada down?
Awaiting datachecked 8 minutes ago
Our checks of Lazada pass from 3 of the 4 regions we check, and have no usable reading from the rest. A missing reading is an absence of data, not an all-clear and not an outage.
As of Nov 5, 2026, 3:22 PM UTC, RealUptime's checks of Lazada passed in all 3 regions that returned a reading. RealUptime could not obtain a reading from Europe, which is a fact about our own check there and is not evidence about Lazada.
Last time our checks failed from two or more distant regions: 2h 36m on Nov 5, 2026 (API, from Europe, US-East and US-West).
Email me when our checks of Lazada fail from two or more distant regions
Lazada publishes no status feed we can read, so the only reading here is our check reading on the left.
Lazada response time, by region
Check your own site while you wait on Lazada
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Lazada. It cannot diagnose Lazada's own systems.
What we measured, function by function
Lazada answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
- APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Awaiting dataAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
What our checks show, and what people reported
- North AmericaNot monitored from this regionUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 1958msstatus code: nonechecked: Nov 5, 2026, 3:22 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Lazada normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 3742msstatus code: 200checked: Nov 5, 2026, 3:17 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Lazada normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralNot monitored from this regionLazada is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- CanadaNot monitored from this regionLazada is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- South AmericaNot monitored from this regionLazada is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- EuropeAwaiting dataEurope, UK
- EuropeAwaiting datalatency: 2004msstatus code: nonecheck reading: nonechecked: Nov 5, 2026, 3:18 PM UTC0 people in the last 5 minutesNot enough reports to sayLazada refused our Europe probe, so we have no reading from there, and a refused probe is not a confirmed outage. We also do not have enough reports from Europe to say anything on their own.
- UKNot monitored from this regionLazada is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- Asia PacificNot monitored from this regionAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 3613msstatus code: 200checked: Nov 5, 2026, 3:17 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Lazada normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaNot monitored from this regionLazada is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- AustraliaNot monitored from this regionLazada is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using Lazada, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Lazada yet, which is not evidence that nothing is wrong.
Recent probe events
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Lazada since November 2, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for Lazada covering any window you pick, with our check readings and Lazada's own claim at the time, side by side.
Full check history for Lazada: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.
Put this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/lazada)<a href="https://realuptime.io/outages/lazada"><img src="https://realuptime.io/outages/lazada/badge.svg?days=30" alt="Lazada uptime by RealUptime's checks" height="20"></a>Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.
To cite this page: RealUptime, "Is Lazada down?", https://realuptime.io/outages/lazada. The readings change with every check, so give the date you read them.
How our checks compare with Lazada's stated SLA
Below your target
Our checks of Lazada failed for 22h 36m over the 73h 15m since we started checking it on 2026-11-02, which is 69.1466% uptime by our checks. A 99.9% target allows 4 minutes over that period.
That is 22h 31m more than the target allows. The figure above is the pro-rata share of one month's fee for the time our checks failed, an estimate from our checks. Lazadadecides what counts. Your contract probably uses a tiered credit schedule instead, and we have not read it, so treat this as one common way to reason about a credit rather than the amount they owe.
These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from Lazada's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.
What we check
What our check can and cannot see
A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.
Host checked: api.lazada.com