User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
tosspayments.com · Cloud & developer
Is tosspayments down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → tosspayments.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 29 min ago. Last stored result reached it in 709 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 14:45 | 0 | 0.0 | 631 ms | 0 |
| 16:45 | 0 | 0.0 | 881 ms | 0 |
| 18:15 | 0 | 0.0 | 675 ms | 0 |
| 20:15 | 0 | 0.0 | 764 ms | 0 |
| 20:30 | 0 | 0.0 | 914 ms | 0 |
| 22:30 | 0 | 0.0 | 699 ms | 0 |
| 00:30 | 0 | 0.0 | 799 ms | 0 |
| 02:30 | 0 | 0.0 | 679 ms | 0 |
| 04:45 | 0 | 0.0 | 704 ms | 0 |
| 06:45 | 0 | 0.0 | 698 ms | 0 |
| 09:00 | 0 | 0.0 | 843 ms | 0 |
| 11:00 | 0 | 0.0 | 709 ms | 0 |
| 12:15 | 0 | 0.0 | 711 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live tosspayments badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for tosspayments yet. Outages of 10 minutes or more get their own page here.
Having trouble with tosspayments?
One report per service every 10 minutes from this network. No account.
Follow tosspayments
Get an email when tosspayments goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send tosspayments alerts to Slack, Discord or a webhook — free.
About tosspayments
We track tosspayments (tosspayments.com) as part of the Cloud & developer group. PG 도입 고민하고 있다면? 쉽고 빠르게 연동할 수 있는 토스페이먼츠를 선택하세요. 카드, 계좌이체, 빌링, 간편결제 등 온라인 사업에 필요한 모든 전자결제수단을 바로 이용할 수 있습니다.
tosspayments publishes an official status page at status.tosspayments.com; 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: 742 ms average, 631–914 ms range across 14 successful checks.
Questions
Is tosspayments down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was tosspayments last down?
We have not recorded a public tosspayments incident since monitoring began 8 days ago.
What is tosspayments's uptime?
From our own checks: 100% over 8 days of checks.
How fast does tosspayments respond?
742 ms on average over the last 24 hours (631–914 ms).
Does tosspayments have an official status page?
Yes, at https://status.tosspayments.com.
tosspayments not working for me but the status is fine. What now?
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 tosspayments here at once, the problem is on tosspayments'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 tosspayments. 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.