User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
scrive.com · Cloud & developer
Is Scrive 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 → scrive.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 44 min ago. Last stored result reached it in 110 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 |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 90 ms | 0 |
| Mon 17 | 0 | 0.0 | 103 ms | 0 |
| Mon 19 | 0 | 0.0 | 324 ms | 0 |
| Mon 21 | 0 | 0.0 | 192 ms | 0 |
| Mon 23 | 0 | 0.0 | 156 ms | 0 |
| Tue 01 | 0 | 0.0 | 202 ms | 0 |
| Tue 04 | 0 | 0.0 | 223 ms | 0 |
| Tue 06 | 0 | 0.0 | 95 ms | 0 |
| Tue 08 | 0 | 0.0 | 111 ms | 0 |
| Tue 10 | 0 | 0.0 | 93 ms | 0 |
| Tue 12 | 0 | 0.0 | 265 ms | 0 |
| Tue 14 | 0 | 0.0 | 264 ms | 0 |
| Tue 17 | 0 | 0.0 | 273 ms | 0 |
| Tue 19 | 0 | 0.0 | 133 ms | 0 |
| Tue 21 | 0 | 0.0 | 97 ms | 0 |
| Tue 23 | 0 | 0.0 | 93 ms | 0 |
| Wed 01 | 0 | 0.0 | 117 ms | 0 |
| Wed 03 | 0 | 0.0 | 234 ms | 0 |
| Wed 06 | 0 | 0.0 | 85 ms | 0 |
| Wed 08 | 0 | 0.0 | 75 ms | 0 |
| Wed 10 | 0 | 0.0 | 218 ms | 0 |
| Wed 12 | 0 | 0.0 | 631 ms | 0 |
| Wed 14 | 0 | 0.0 | 155 ms | 0 |
| Wed 16 | 0 | 0.0 | 107 ms | 0 |
| Wed 19 | 0 | 0.0 | 185 ms | 0 |
| Wed 21 | 0 | 0.0 | 112 ms | 0 |
| Wed 23 | 0 | 0.0 | 146 ms | 0 |
| Thu 01 | 0 | 0.0 | 297 ms | 0 |
| Thu 03 | 0 | 0.0 | 356 ms | 0 |
| Thu 05 | 0 | 0.0 | 337 ms | 0 |
| Thu 07 | 0 | 0.0 | 251 ms | 0 |
| Thu 10 | 0 | 0.0 | 115 ms | 0 |
| Thu 12 | 0 | 0.0 | 159 ms | 0 |
| Thu 14 | 0 | 0.0 | 207 ms | 0 |
| Thu 16 | 0 | 0.0 | 393 ms | 0 |
| Thu 18 | 0 | 0.0 | 260 ms | 0 |
| Thu 20 | 0 | 0.0 | 148 ms | 0 |
| Thu 21 | 0 | 0.0 | 145 ms | 0 |
| Thu 23 | 0 | 0.0 | 153 ms | 0 |
| Fri 00 | 0 | 0.0 | 169 ms | 0 |
| Fri 02 | 0 | 0.0 | 166 ms | 0 |
| Fri 04 | 0 | 0.0 | 189 ms | 0 |
| Fri 06 | 0 | 0.0 | 200 ms | 0 |
| Fri 08 | 0 | 0.0 | 91 ms | 0 |
| Fri 10 | 0 | 0.0 | 280 ms | 0 |
| Fri 12 | 0 | 0.0 | 94 ms | 0 |
| Fri 14 | 0 | 0.0 | 236 ms | 0 |
| Fri 17 | 0 | 0.0 | 110 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 Scrive 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
Critical Security Maintenance: November 14
On Saturday, November 14, between 07:00 and 09:00 CET, we will apply critical security updates to our database servers. During this period, you will not be able to access the Scrive service, and any ongoing activities will be temporarily suspended. Thank you for your patience and understanding. If you have any questions or concerns, please feel free to contact us at support@scrive.com.
Announced by Scrive · source
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
Past outages
No outages on record for Scrive yet. Outages of 10 minutes or more get their own page here.
Having trouble with Scrive?
One report per service every 10 minutes from this network. No account.
Follow Scrive
Get an email when Scrive goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Scrive alerts to Slack, Discord or a webhook — free.
About Scrive
We track Scrive (scrive.com) as part of the Cloud & developer group. Simplify contract management with a platform built for European compliance. Trusted by over 14,000 businesses. Start your free trial today.
Scrive publishes an official status page at status.scrive.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: 173 ms average, 91–280 ms range across 15 successful checks.
Questions
Is Scrive down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Scrive last down?
We have not recorded a public Scrive incident since monitoring began 8 days ago.
What is Scrive's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Scrive respond?
173 ms on average over the last 24 hours (91–280 ms).
Does Scrive have an official status page?
Yes, at https://status.scrive.com.
Scrive 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 Scrive here at once, the problem is on Scrive'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 Scrive. 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.