User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
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 27 min ago. Last stored result reached it in 777 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Wed 00 | 0 | 0.0 | — | 0 |
| Wed 02 | 0 | 0.0 | 1024 ms | 0 |
| Wed 04 | 0 | 0.0 | 1030 ms | 0 |
| Wed 07 | 0 | 0.0 | 936 ms | 0 |
| Wed 09 | 0 | 0.0 | 984 ms | 0 |
| Wed 11 | 0 | 0.0 | 1024 ms | 0 |
| Wed 13 | 0 | 0.0 | 1406 ms | 0 |
| Wed 15 | 0 | 0.0 | 804 ms | 0 |
| Wed 17 | 0 | 0.0 | 1080 ms | 0 |
| Wed 20 | 0 | 0.0 | 1000 ms | 0 |
| Wed 22 | 0 | 0.0 | 996 ms | 0 |
| Thu 00 | 0 | 0.0 | 587 ms | 0 |
| Thu 02 | 0 | 0.0 | 948 ms | 0 |
| Thu 04 | 0 | 0.0 | 1122 ms | 0 |
| Thu 06 | 0 | 0.0 | 1213 ms | 0 |
| Thu 08 | 0 | 0.0 | 991 ms | 0 |
| Thu 10 | 0 | 0.0 | 1042 ms | 0 |
| Thu 12 | 0 | 0.0 | 1228 ms | 0 |
| Thu 14 | 0 | 0.0 | 1210 ms | 0 |
| Thu 17 | 0 | 0.0 | 1188 ms | 0 |
| Thu 19 | 0 | 0.0 | — | 1 |
| Thu 21 | 0 | 0.0 | 1224 ms | 0 |
| Thu 23 | 0 | 0.0 | 923 ms | 0 |
| Fri 01 | 0 | 0.0 | 980 ms | 0 |
| Fri 03 | 0 | 0.0 | 1021 ms | 0 |
| Fri 05 | 0 | 0.0 | 985 ms | 0 |
| Fri 07 | 0 | 0.0 | 969 ms | 0 |
| Fri 09 | 0 | 0.0 | 478 ms | 0 |
| Fri 10 | 0 | 0.0 | 406 ms | 0 |
| Fri 11 | 0 | 0.0 | 1038 ms | 0 |
| Fri 13 | 0 | 0.0 | 956 ms | 0 |
| Fri 15 | 0 | 0.0 | 1282 ms | 0 |
| Fri 17 | 0 | 0.0 | 982 ms | 0 |
| Fri 19 | 0 | 0.0 | 941 ms | 0 |
| Fri 21 | 0 | 0.0 | 1082 ms | 0 |
| Fri 23 | 0 | 0.0 | 885 ms | 0 |
| Sat 01 | 0 | 0.0 | 918 ms | 0 |
| Sat 03 | 0 | 0.0 | 1150 ms | 0 |
| Sat 05 | 0 | 0.0 | 935 ms | 0 |
| Sat 07 | 0 | 0.0 | 975 ms | 0 |
| Sat 09 | 0 | 0.0 | 1131 ms | 0 |
| Sat 12 | 0 | 0.0 | 932 ms | 0 |
| Sat 14 | 0 | 0.0 | 961 ms | 0 |
| Sat 16 | 0 | 0.0 | 1232 ms | 0 |
| Sat 18 | 0 | 0.0 | 1019 ms | 0 |
| Sat 19 | 0 | 0.0 | 999 ms | 0 |
| Sat 21 | 0 | 0.0 | 631 ms | 0 |
| Sat 23 | 0 | 0.0 | 891 ms | 0 |
98.89% 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 iMotorbike 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 iMotorbike goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
We track iMotorbike (imotorbike.com) as part of the Money group. Buy & sell used motorbikes online in Malaysia fast, easy & safe. Fast Payment, 6 Days Return & 6 Months Warranty.
iMotorbike publishes an official status page at status.imotorbike.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with money services: login and two-factor problems, payments or transfers failing, and app errors.
Measured uptime from our checks: 98.89% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 950 ms average, 315–1232 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public iMotorbike incident since monitoring began 8 days ago.
From our own checks: 98.89% over 8 days of checks.
950 ms on average over the last 24 hours (315–1232 ms).
Yes, at https://status.imotorbike.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For money services, watch for login and two-factor problems, payments or transfers failing, and app errors. If many people report iMotorbike here at once, the problem is on iMotorbike'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 iMotorbike. 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.