User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
scribe-mail.com · Cloud & developer
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 48 min ago. Last stored result reached it in 1972 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 | 1530 ms | 0 |
| Mon 13 | 0 | 0.0 | 1846 ms | 0 |
| Mon 15 | 0 | 0.0 | 851 ms | 0 |
| Mon 18 | 0 | 0.0 | 2156 ms | 0 |
| Mon 20 | 0 | 0.0 | 1244 ms | 0 |
| Mon 22 | 0 | 0.0 | 129 ms | 0 |
| Tue 00 | 0 | 0.0 | 986 ms | 0 |
| Tue 02 | 0 | 0.0 | 1551 ms | 0 |
| Tue 04 | 0 | 0.0 | 1779 ms | 0 |
| Tue 06 | 0 | 0.0 | 977 ms | 0 |
| Tue 08 | 0 | 0.0 | 815 ms | 0 |
| Tue 11 | 0 | 0.0 | 1400 ms | 0 |
| Tue 13 | 0 | 0.0 | 149 ms | 0 |
| Tue 15 | 0 | 0.0 | 2017 ms | 0 |
| Tue 17 | 0 | 0.0 | 132 ms | 0 |
| Tue 20 | 0 | 0.0 | 968 ms | 0 |
| Tue 22 | 0 | 0.0 | 1992 ms | 0 |
| Wed 00 | 0 | 0.0 | 796 ms | 0 |
| Wed 02 | 0 | 0.0 | 1158 ms | 0 |
| Wed 05 | 0 | 0.0 | 79 ms | 0 |
| Wed 07 | 0 | 0.0 | 713 ms | 0 |
| Wed 09 | 0 | 0.0 | 1077 ms | 0 |
| Wed 11 | 0 | 0.0 | 1060 ms | 0 |
| Wed 13 | 0 | 0.0 | 1039 ms | 0 |
| Wed 15 | 0 | 0.0 | 1031 ms | 0 |
| Wed 18 | 0 | 0.0 | 474 ms | 0 |
| Wed 20 | 0 | 0.0 | 1368 ms | 0 |
| Wed 22 | 0 | 0.0 | 854 ms | 0 |
| Thu 00 | 0 | 0.0 | 808 ms | 0 |
| Thu 02 | 0 | 0.0 | 1137 ms | 0 |
| Thu 04 | 0 | 0.0 | 99 ms | 0 |
| Thu 06 | 0 | 0.0 | 143 ms | 0 |
| Thu 09 | 0 | 0.0 | 750 ms | 0 |
| Thu 11 | 0 | 0.0 | 1274 ms | 0 |
| Thu 13 | 0 | 0.0 | 676 ms | 0 |
| Thu 15 | 0 | 0.0 | 1112 ms | 0 |
| Thu 17 | 0 | 0.0 | 2117 ms | 0 |
| Thu 19 | 0 | 0.0 | 1112 ms | 0 |
| Thu 21 | 0 | 0.0 | 1870 ms | 0 |
| Thu 23 | 0 | 0.0 | 1526 ms | 0 |
| Fri 01 | 0 | 0.0 | 935 ms | 0 |
| Fri 03 | 0 | 0.0 | 83 ms | 0 |
| Fri 05 | 0 | 0.0 | 96 ms | 0 |
| Fri 07 | 0 | 0.0 | 116 ms | 0 |
| Fri 09 | 0 | 0.0 | 72 ms | 0 |
| Fri 11 | 0 | 0.0 | 507 ms | 0 |
| Fri 14 | 0 | 0.0 | 1859 ms | 0 |
| Fri 16 | 0 | 0.0 | 1972 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 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Scribe 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 Scribe goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Scribe alerts to Slack, Discord or a webhook — free.
Scribe, at scribe-mail.com, is one of the Cloud & developer services we monitor. Install consistent signatures company-wide in under a day. No employee installation. 12% average CTR on banners, conversion tracking from click to revenue.
Scribe publishes an official status page at status.scribe-mail.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 982 ms average, 72–2117 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Scribe incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
982 ms on average over the last 24 hours (72–2117 ms).
Yes, at https://status.scribe-mail.com.
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 Scribe here at once, the problem is on Scribe'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 Scribe. 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.