Live checks, official provider updates, and incident history for Daraz.
See the latest checks and provider updates, with separate results for Pakistan and other countries.
A recent public access check succeeded. The Pakistan result uses that check; access on Pakistani networks has not been independently tested.
Updates every 5 minutesChecks cover the measured service access; individual app features or accounts can behave differently.
The latest website check reached the service at 03-Oct-2026, 4:50 am PKT. This is one signal from the monitoring location.
A working result can use one successful public access check at the monitoring location. This does not verify every Pakistani or international network. Percentages, when shown, refer only to networks actually measured.
A responsive public website does not guarantee that every part of Daraz is working. Login, notifications, payments, media, APIs, or regional routes can fail independently. We describe the evidence we have rather than turning a single successful check into a broad claim. When the latest stored status grows stale, the page shows that the status is not verified until new measurements arrive.
A status label is only a starting point. The exact symptom and the networks involved help explain what may be happening.
Shopping and mobility apps depend on search, booking, checkout, payment, and location services. A problem in one step can look like a full outage.
Record whether browsing works and exactly where the flow stops. A payment may be pending even if the confirmation screen does not load.
Check connectivity and app updates, then use official support before retrying a charge or booking. Avoid sharing payment details in public reports.
If the service fails on only one device, browser, or account, the cause may be local. If it fails across different connections and other people report the same symptom at the same time, a wider problem becomes more plausible. Keep troubleshooting steps reversible, particularly when a payment, booking, upload, or form submission could already be in progress.
Public site checks and independent network measurements supply different kinds of evidence. A broad classification requires several corroborating signals.
Our worker tests safe public endpoints for DNS resolution, TCP connectivity, TLS negotiation, HTTPS response, and latency. RIPE Atlas can add Pakistani and international probe observations when configured; OONI may provide access context. Official status feeds are considered where the provider publishes one. These signals are weighted conservatively, and an unavailable provider contributes no positive evidence.
Availability data cannot confirm whether a particular order, booking, or refund was processed.
For Daraz, if checkout, booking, or payment seems to hang, inspect the provider's order or trip history before retrying. A second tap may create a duplicate order even when the first confirmation screen did not load. Distinguish search, map, inventory, payment, and tracking symptoms. A lack of nearby drivers or stock is not itself a technical outage. Public checks cannot view a private cart or booking; use official support for a disputed transaction or missing receipt.
Independent checks and official updates help confirm wider disruptions. For a problem with your own account, use the service’s official support channel.
Historical charts use stored checks. They start empty and grow as monitoring runs; no incidents or availability figures are fabricated.
Switch between 24-hour, 7-day, 30-day, and 90-day views.
Average public endpoint availability in this view: 99.4%. This measures configured endpoints, not every feature of the service.
No confirmed incidents have been recorded for Daraz yet.
A public endpoint availability percentage measures only configured endpoints. It does not promise that every feature, region, account, or app function was available for the same percentage of time. Older raw checks are rolled into hourly aggregates and removed under the retention policy, while incident records remain available for context.
