User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
dilar.tube · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 1 hr ago. Last stored result reached it in 305 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 208 ms | 0 |
| Mon 23 | 0 | 0.0 | 341 ms | 0 |
| Tue 01 | 0 | 0.0 | 411 ms | 0 |
| Tue 03 | 0 | 0.0 | 566 ms | 0 |
| Tue 05 | 0 | 0.0 | 529 ms | 0 |
| Tue 07 | 0 | 0.0 | 510 ms | 0 |
| Tue 09 | 0 | 0.0 | 381 ms | 0 |
| Tue 11 | 0 | 0.0 | 503 ms | 0 |
| Tue 13 | 0 | 0.0 | 562 ms | 0 |
| Tue 16 | 0 | 0.0 | 469 ms | 0 |
| Tue 18 | 0 | 0.0 | 592 ms | 0 |
| Tue 20 | 0 | 0.0 | 286 ms | 0 |
| Tue 22 | 0 | 0.0 | 367 ms | 0 |
| Wed 01 | 0 | 0.0 | 553 ms | 0 |
| Wed 03 | 0 | 0.0 | 610 ms | 0 |
| Wed 05 | 0 | 0.0 | 521 ms | 0 |
| Wed 07 | 0 | 0.0 | 538 ms | 0 |
| Wed 10 | 0 | 0.0 | 393 ms | 0 |
| Wed 12 | 0 | 0.0 | 484 ms | 0 |
| Wed 14 | 0 | 0.0 | 484 ms | 0 |
| Wed 16 | 0 | 0.0 | 542 ms | 0 |
| Wed 18 | 0 | 0.0 | 456 ms | 0 |
| Wed 20 | 0 | 0.0 | 406 ms | 0 |
| Wed 23 | 0 | 0.0 | 372 ms | 0 |
| Thu 01 | 0 | 0.0 | 369 ms | 0 |
| Thu 03 | 0 | 0.0 | 806 ms | 0 |
| Thu 05 | 0 | 0.0 | 372 ms | 0 |
| Thu 07 | 0 | 0.0 | 387 ms | 0 |
| Thu 09 | 0 | 0.0 | 258 ms | 0 |
| Thu 11 | 0 | 0.0 | — | 0 |
| Thu 13 | 0 | 0.0 | 241 ms | 0 |
| Thu 15 | 0 | 0.0 | 427 ms | 0 |
| Thu 17 | 0 | 0.0 | 391 ms | 0 |
| Thu 19 | 0 | 0.0 | 426 ms | 0 |
| Thu 21 | 0 | 0.0 | 500 ms | 0 |
| Thu 23 | 0 | 0.0 | 416 ms | 0 |
| Fri 01 | 0 | 0.0 | 340 ms | 0 |
| Fri 04 | 0 | 0.0 | 500 ms | 0 |
| Fri 06 | 0 | 0.0 | 751 ms | 0 |
| Fri 08 | 0 | 0.0 | 665 ms | 0 |
| Fri 10 | 0 | 0.0 | 301 ms | 0 |
| Fri 11 | 0 | 0.0 | 325 ms | 0 |
| Fri 13 | 0 | 0.0 | 461 ms | 0 |
| Fri 15 | 0 | 0.0 | 636 ms | 0 |
| Fri 17 | 0 | 0.0 | 560 ms | 0 |
| Fri 18 | 0 | 0.0 | 382 ms | 0 |
| Fri 19 | 0 | 0.0 | 509 ms | 0 |
| Fri 21 | 0 | 0.0 | 305 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Dilar yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Dilar goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Dilar alerts to Slack, Discord or a webhook — free.
Dilar is listed in our Cloud & developer category and checked at dilar.tube. موقع Dilar هو موقع تفاعلي يهدف لتوفير خيارات أكثر لعرض الترجمات العربية لفصول المانجا، ويوفّر كذلك روابط مباشرة لتحميل الفصول وأيضًا قراءتها بعدة طرق. جميع فصول الأعمال سواء كانت مانجا، مانها او مانهوا المشهورة مثل ون بيس ، كونان ، ناروتو ، بليتش ، فيري تيل، سولو ليفلنج.
Dilar publishes an official status page at status.dilar.tube; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 470 ms average, 191–751 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Dilar incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
470 ms on average over the last 24 hours (191–751 ms).
Yes, at https://status.dilar.tube.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Dilar here at once, the problem is on Dilar's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Dilar. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.