RealUptime

Lazada: SLA evidence report

2026-11-02 to 2026-11-06 · read by RealUptime from our regions · generated Nov 6, 2026, 6:58 PM UTC

Lazada: SLA evidence report

We only started checking Lazada on 2026-11-02, so the window starts there.

Time our checks failed
31h 37m
Across 13 probe events in this window.
Window
2026-11-02 to 2026-11-06
UTC, 4 days.

  • Nov 6, 2026, 7:07 AM UTC to Nov 6, 2026, 10:27 AM UTC

    Multiple regions: Europe, US-East, US-West

    3h 20mchecks failing in this window

    Lazada's status page at the time: No claim history exists for this period

  • Nov 6, 2026, 2:23 AM UTC to Nov 6, 2026, 5:35 AM UTC

    Multiple regions: Europe, US-East, US-West

    3h 12mchecks failing in this window

    Lazada's status page at the time: No claim history exists for this period

  • Nov 5, 2026, 7:40 PM UTC to Nov 5, 2026, 8:47 PM UTC

    Multiple regions: Europe, US-East, US-West

    1h 7mchecks failing in this window

    Lazada's status page at the time: No claim history exists for this period

  • Nov 5, 2026, 4:01 PM UTC to Nov 5, 2026, 5:23 PM UTC

    Multiple regions: Europe, US-East, US-West

    1h 22mchecks failing in this window

    Lazada's status page at the time: No claim history exists for this period

  • Nov 5, 2026, 12:00 PM UTC to Nov 5, 2026, 2:35 PM UTC

    Multiple regions: Europe, US-East, US-West

    2h 36mchecks failing in this window

    Lazada's status page at the time: No claim history exists for this period

  • Nov 5, 2026, 5:34 AM UTC to Nov 5, 2026, 7:42 AM UTC

    Multiple regions: Europe, US-East, US-West

    2h 8mchecks failing in this window

    Lazada's status page at the time: No claim history exists for this period

  • Nov 5, 2026, 12:49 AM UTC to Nov 5, 2026, 2:08 AM UTC

    Multiple regions: Europe, US-East, US-West

    1h 19mchecks failing in this window

    Lazada's status page at the time: No claim history exists for this period

  • Nov 4, 2026, 9:10 PM UTC to Nov 5, 2026, 12:28 AM UTC

    Multiple regions: Europe, US-East, US-West

    3h 18mchecks failing in this window

    Lazada's status page at the time: No claim history exists for this period

  • Nov 4, 2026, 9:15 AM UTC to Nov 4, 2026, 2:52 PM UTC

    Multiple regions: Europe, US-East, Asia-Pacific, US-West

    5h 38mchecks failing in this window

    Lazada's status page at the time: No claim history exists for this period

  • Nov 4, 2026, 5:20 AM UTC to Nov 4, 2026, 5:46 AM UTC

    Multiple regions: US-East, Asia-Pacific

    26.3mchecks failing in this window

    Lazada's status page at the time: No claim history exists for this period

  • Nov 4, 2026, 12:29 AM UTC to Nov 4, 2026, 4:55 AM UTC

    Multiple regions: Europe, US-East, US-West

    4h 26mchecks failing in this window

    Lazada's status page at the time: No claim history exists for this period

  • Nov 3, 2026, 8:41 PM UTC to Nov 3, 2026, 9:14 PM UTC

    Multiple regions: Europe, US-East

    33.0mchecks failing in this window

    Lazada's status page at the time: No claim history exists for this period

  • Nov 3, 2026, 5:56 PM UTC to Nov 3, 2026, 8:09 PM UTC

    Multiple regions: Europe, US-East, US-West

    2h 13mchecks failing in this window

    Lazada's status page at the time: No claim history exists for this period

13 earlier probe events in this window happened before we began keeping a record of Lazada's own status-page claims, so no claim comparison exists for them.

What we check

primary
https://api.lazada.com/rest
secondary
https://www.lazada.com/

Estimate an SLA credit from our check readings

Enter what you pay Lazada for this period and their own stated SLA target. This estimates a credit from the time our checks failed, shown above. The figure is an estimate from our checks andLazada decides what counts. It is one common way to reason about an SLA credit, notLazada's own contract terms, and it is not a legal determination. RealUptime is not counsel.

Based on 1,896.7 minutes with our checks failing across this report's window.

Methodology

Every event above is a period in which our checks of Lazada failed from two or more distant regions, meaning regions on different continents (see how we tell the difference). One that nothing else backs stops counting as an outage after 6 hours, and an event that fails these rules is retracted, kept, and listed on the corrections page. The time our checks failed is the wall-clock time inside the window an event's regions were failing; regions failing together still count as one event, not one per region. It is not proof of downtime for your account.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime.

Lazada's claim at the time comes from their own public status feed, polled on our own schedule, and is shown separately from our check readings. We never change our own reading based on what a vendor claims, and their claim never becomes our reading.

This is one external reading from RealUptime's own regions, not Lazada's own SLA measurement, which is usually defined against their own instrumentation and may cover a different scope than what we check. The credit estimate above is an estimate from our checks, and Lazada decides what counts. It is a starting point for a conversation with Lazada, not a legal determination, and RealUptime is not counsel.