User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
cloudsign.jp · Cloud & developer
Is CloudSign Series down?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
Source: the vendor's status page · We are not affiliated with CloudSign Series.
What to try while CloudSign Series is having problems
Estimated fix: Not enough CloudSign Series history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–13 h; 77 outages).
- Hold off on deploys and config changes; check which regions or products are affected and retry with backoff.
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 → cloudsign.jp—
Your browser → us—
Our checksReaching it
Official · ReportsMinor incident · 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 44 min ago. Last stored result reached it in 228 ms.
Official status
Minor incident
Some components degraded (no active incident posted) Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 05:15 | 0 | 0.0 | 67 ms | 0 |
| 07:15 | 0 | 0.0 | 155 ms | 0 |
| 09:30 | 0 | 0.0 | 54 ms | 0 |
| 11:30 | 0 | 0.0 | 54 ms | 0 |
| 13:30 | 0 | 0.0 | 59 ms | 0 |
| 15:30 | 0 | 0.0 | 64 ms | 0 |
| 17:45 | 0 | 0.0 | 79 ms | 0 |
| 19:45 | 0 | 0.0 | 150 ms | 0 |
| 21:45 | 0 | 0.0 | 52 ms | 0 |
| 23:45 | 0 | 0.0 | 35 ms | 0 |
| 01:45 | 0 | 0.0 | 146 ms | 0 |
| 04:00 | 0 | 0.0 | 228 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 CloudSign Series badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
This week
Planned maintenance
署名機能メンテナンスのお知らせ：サービス停止なし（2026年11月14日）
下記のとおり、クラウドサインにおける署名機能のメンテナンスを実施いたします。サービスの停止はありません。 ■メンテナンス日時 ・2026年11月14日（土）23:00 〜 11月15日（日）05:00 ※メンテナンス終了時間は都合により変更する場合がございます。 ■ 影響範囲 ・メンテナンス中もクラウドサインをご利用いただけます。 ・該当時間帯において、最大 30 秒程度の署名処理停止が発生する可能性があります。署名処理を伴う操作（書類送信や同意など）でエラーが発生した場合は、大変恐れ入りますが、再度操作のやり直しをお願いします。 ■ メンテナンスの目的 ・署名機能の安定稼働を目的とするものです。
Announced by CloudSign Series · source検索機能の臨時メンテナンスのお知らせ：サービス停止なし（2026年11月17日）
検索機能の臨時メンテナンスを以下の通り実施いたします。 ■メンテナンス期間 2026年11月17日（火） 19:00 〜 22:00 ※メンテナンス終了時間は都合により変更する場合がございます ■ 影響範囲 メンテナンス期間中においては、書類の検索結果の表示に時間がかかる、または表示されない場合があります。その場合は、メンテナンス終了後での再操作をお願いいたします。 なお、本影響はメンテナンス期間中のみのため、メンテナンス終了後には通常通り検索機能をご利用いただけます。 ※ メンテナンス期間中でもクラウドサインはご利用いただけます ■ メンテナンスの目的 検索機能のパフォーマンス維持向上を目的とするものです。
Announced by CloudSign Series · source
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
Past outages
No outages on record for CloudSign Series yet. Outages of 10 minutes or more get their own page here.
Having trouble with CloudSign Series?
One report per service every 10 minutes from this network. No account.
Follow CloudSign Series
Get an email when CloudSign Series goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send CloudSign Series alerts to Slack, Discord or a webhook — free.
About CloudSign Series
We track CloudSign Series (cloudsign.jp) as part of the Cloud & developer group. クラウドサインは導入250万社超・ 累計送信件数4000万件超の国内シェアNo.1電子契約。締結から契約書管理（保管・検索）まで一元化。法務省基準・高セキュリティ。資料ダウンロード無料・料金なども相談可能。
CloudSign Series publishes an official status page at status.cloudsign.jp; 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: 100 ms average, 35–228 ms range across 13 successful checks.
Questions
Is CloudSign Series down right now?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
When was CloudSign Series last down?
We have not recorded a public CloudSign Series incident since monitoring began 8 days ago.
What is CloudSign Series's uptime?
From our own checks: 100% over 8 days of checks.
How fast does CloudSign Series respond?
100 ms on average over the last 24 hours (35–228 ms).
Does CloudSign Series have an official status page?
Yes, at https://status.cloudsign.jp.
CloudSign Series 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 CloudSign Series here at once, the problem is on CloudSign Series'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 CloudSign Series. 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.