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 2 hr ago. Last stored result reached it in 518 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 11 | 0 | 0.0 | 239 ms | 0 |
| Mon 13 | 0 | 0.0 | 677 ms | 0 |
| Mon 15 | 0 | 0.0 | 438 ms | 0 |
| Mon 17 | 0 | 0.0 | 421 ms | 0 |
| Mon 20 | 0 | 0.0 | 637 ms | 0 |
| Mon 22 | 0 | 0.0 | 277 ms | 0 |
| Tue 00 | 0 | 0.0 | 333 ms | 0 |
| Tue 02 | 0 | 0.0 | 402 ms | 0 |
| Tue 04 | 0 | 0.0 | 271 ms | 0 |
| Tue 06 | 0 | 0.0 | 457 ms | 0 |
| Tue 08 | 0 | 0.0 | 383 ms | 0 |
| Tue 10 | 0 | 0.0 | 378 ms | 0 |
| Tue 12 | 0 | 0.0 | 294 ms | 0 |
| Tue 15 | 0 | 0.0 | 343 ms | 0 |
| Tue 17 | 0 | 0.0 | 696 ms | 0 |
| Tue 19 | 0 | 0.0 | 432 ms | 0 |
| Tue 21 | 0 | 0.0 | 460 ms | 0 |
| Wed 00 | 0 | 0.0 | 462 ms | 0 |
| Wed 02 | 0 | 0.0 | 740 ms | 0 |
| Wed 04 | 0 | 0.0 | 474 ms | 0 |
| Wed 06 | 0 | 0.0 | 375 ms | 0 |
| Wed 09 | 0 | 0.0 | 220 ms | 0 |
| Wed 11 | 0 | 0.0 | 429 ms | 0 |
| Wed 13 | 0 | 0.0 | 613 ms | 0 |
| Wed 15 | 0 | 0.0 | 503 ms | 0 |
| Wed 17 | 0 | 0.0 | 322 ms | 0 |
| Wed 19 | 0 | 0.0 | 418 ms | 0 |
| Wed 22 | 0 | 0.0 | 448 ms | 0 |
| Thu 00 | 0 | 0.0 | 641 ms | 0 |
| Thu 02 | 0 | 0.0 | 274 ms | 0 |
| Thu 04 | 0 | 0.0 | 420 ms | 0 |
| Thu 06 | 0 | 0.0 | 433 ms | 0 |
| Thu 08 | 0 | 0.0 | 762 ms | 0 |
| Thu 10 | 0 | 0.0 | 547 ms | 0 |
| Thu 12 | 0 | 0.0 | 416 ms | 0 |
| Thu 14 | 0 | 0.0 | 468 ms | 0 |
| Thu 16 | 0 | 0.0 | 321 ms | 0 |
| Thu 18 | 0 | 0.0 | 428 ms | 0 |
| Thu 20 | 0 | 0.0 | 449 ms | 0 |
| Thu 22 | 0 | 0.0 | 536 ms | 0 |
| Fri 01 | 0 | 0.0 | 536 ms | 0 |
| Fri 03 | 0 | 0.0 | 600 ms | 0 |
| Fri 05 | 0 | 0.0 | 759 ms | 0 |
| Fri 07 | 0 | 0.0 | 418 ms | 0 |
| Fri 09 | 0 | 0.0 | 390 ms | 0 |
| Fri 11 | 0 | 0.0 | 440 ms | 0 |
| Fri 12 | 0 | 0.0 | 322 ms | 0 |
| Fri 14 | 0 | 0.0 | 475 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for CHIP 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 CHIP goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send CHIP alerts to Slack, Discord or a webhook — free.
We track CHIP (chip-in.asia) as part of the Money group. CHIP is a Digital Finance Platform that helps Malaysian businesses collect payments, manage cashflow, control expenses, send payouts and access capital.
CHIP publishes an official status page at status.chip-in.asia; when we can read it, its incident level is folded into the status shown here.
Common problems for money services: login and two-factor problems, payments or transfers failing, and app errors.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 478 ms average, 321–759 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 CHIP incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
478 ms on average over the last 24 hours (321–759 ms).
Yes, at https://status.chip-in.asia.
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 CHIP here at once, the problem is on CHIP'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 CHIP. 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.