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 min ago. Last stored result reached it in 59 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Wed 00 | 0 | 0.0 | 100 ms | 0 |
| Wed 02 | 0 | 0.0 | 87 ms | 0 |
| Wed 05 | 0 | 0.0 | 70 ms | 0 |
| Wed 07 | 0 | 0.0 | 72 ms | 0 |
| Wed 09 | 0 | 0.0 | 70 ms | 0 |
| Wed 11 | 0 | 0.0 | 33 ms | 0 |
| Wed 13 | 0 | 0.0 | 40 ms | 0 |
| Wed 15 | 0 | 0.0 | 68 ms | 0 |
| Wed 18 | 0 | 0.0 | 52 ms | 0 |
| Wed 20 | 0 | 0.0 | 78 ms | 0 |
| Wed 22 | 0 | 0.0 | 55 ms | 0 |
| Thu 00 | 0 | 0.0 | 73 ms | 0 |
| Thu 02 | 0 | 0.0 | 58 ms | 0 |
| Thu 04 | 0 | 0.0 | 51 ms | 0 |
| Thu 06 | 0 | 0.0 | 40 ms | 0 |
| Thu 08 | 0 | 0.0 | 37 ms | 0 |
| Thu 11 | 0 | 0.0 | 65 ms | 0 |
| Thu 13 | 0 | 0.0 | 99 ms | 0 |
| Thu 15 | 0 | 0.0 | 86 ms | 0 |
| Thu 17 | 0 | 0.0 | 88 ms | 0 |
| Thu 19 | 0 | 0.0 | 92 ms | 0 |
| Thu 21 | 0 | 0.0 | 76 ms | 0 |
| Thu 23 | 0 | 0.0 | 73 ms | 0 |
| Fri 01 | 0 | 0.0 | 44 ms | 0 |
| Fri 02 | 0 | 0.0 | 66 ms | 0 |
| Fri 04 | 0 | 0.0 | 96 ms | 0 |
| Fri 06 | 0 | 0.0 | 25 ms | 0 |
| Fri 08 | 0 | 0.0 | 58 ms | 0 |
| Fri 10 | 0 | 0.0 | 24 ms | 0 |
| Fri 12 | 0 | 0.0 | 36 ms | 0 |
| Fri 14 | 0 | 0.0 | 49 ms | 0 |
| Fri 16 | 0 | 0.0 | 121 ms | 0 |
| Fri 18 | 0 | 0.0 | 85 ms | 0 |
| Fri 20 | 0 | 0.0 | 86 ms | 0 |
| Fri 22 | 0 | 0.0 | 22 ms | 0 |
| Fri 23 | 0 | 0.0 | 58 ms | 0 |
| Sat 01 | 0 | 0.0 | 45 ms | 0 |
| Sat 03 | 0 | 0.0 | 49 ms | 0 |
| Sat 05 | 0 | 0.0 | 52 ms | 0 |
| Sat 07 | 0 | 0.0 | 74 ms | 0 |
| Sat 09 | 0 | 0.0 | 38 ms | 0 |
| Sat 10 | 0 | 0.0 | 46 ms | 0 |
| Sat 11 | 0 | 0.0 | 42 ms | 0 |
| Sat 14 | 0 | 0.0 | 33 ms | 0 |
| Sat 15 | 0 | 0.0 | 119 ms | 0 |
| Sat 18 | 0 | 0.0 | 43 ms | 0 |
| Sat 20 | 0 | 0.0 | 56 ms | 0 |
| Sat 23 | 0 | 0.0 | 59 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 9 days of data so far, so the 90-day numbers fill in over time.
[Partner] Bangkok Bank (BBL) Mobile banking will be maintenance on Sat, 21 Nov 2026 during 02:00 - 07:00 (GMT+7)
Bangkok Bank (BBL) Mobile banking will be maintenance on Sat, 21 Nov 2026 during 02:00 - 07:00 (GMT+7)
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for Omise 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 Omise 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 Omise (omise.co) as part of the Money group. Omise is a financial technology platform designed to empower global businesses and financial institutions to accept and make secure payments, increasing revenue easily, seamlessly, and without borders.
Omise publishes an official status page at status.omise.co; 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 54 ms average, 26–119 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 Omise incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
54 ms on average over the last 24 hours (26–119 ms).
Yes, at https://status.omise.co.
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 Omise here at once, the problem is on Omise'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 Omise. 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.