User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 1 min ago. Last stored result reached it in 1194 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 1207 ms | 0 |
| Mon 22 | 0 | 0.0 | 1313 ms | 0 |
| Tue 00 | 0 | 0.0 | 2523 ms | 0 |
| Tue 02 | 0 | 0.0 | 1070 ms | 0 |
| Tue 04 | 0 | 0.0 | 156 ms | 0 |
| Tue 06 | 0 | 0.0 | 1030 ms | 0 |
| Tue 08 | 0 | 0.0 | 98 ms | 0 |
| Tue 10 | 0 | 0.0 | 1046 ms | 0 |
| Tue 12 | 0 | 0.0 | 1202 ms | 0 |
| Tue 15 | 0 | 0.0 | 1345 ms | 0 |
| Tue 17 | 0 | 0.0 | 1035 ms | 0 |
| Tue 19 | 0 | 0.0 | 1371 ms | 0 |
| Tue 22 | 0 | 0.0 | 1118 ms | 0 |
| Wed 00 | 0 | 0.0 | 1173 ms | 0 |
| Wed 02 | 0 | 0.0 | 1142 ms | 0 |
| Wed 04 | 0 | 0.0 | 1662 ms | 0 |
| Wed 06 | 0 | 0.0 | 251 ms | 0 |
| Wed 09 | 0 | 0.0 | 1021 ms | 0 |
| Wed 10 | 0 | 0.0 | 1011 ms | 0 |
| Wed 13 | 0 | 0.0 | 847 ms | 0 |
| Wed 15 | 0 | 0.0 | 1372 ms | 0 |
| Wed 17 | 0 | 0.0 | 567 ms | 0 |
| Wed 19 | 0 | 0.0 | 627 ms | 0 |
| Wed 21 | 0 | 0.0 | 1233 ms | 0 |
| Wed 23 | 0 | 0.0 | 989 ms | 0 |
| Thu 01 | 0 | 0.0 | 428 ms | 0 |
| Thu 04 | 0 | 0.0 | 538 ms | 0 |
| Thu 06 | 0 | 0.0 | 1135 ms | 0 |
| Thu 08 | 0 | 0.0 | 1288 ms | 0 |
| Thu 10 | 0 | 0.0 | 1164 ms | 0 |
| Thu 12 | 0 | 0.0 | 1399 ms | 0 |
| Thu 14 | 0 | 0.0 | 840 ms | 0 |
| Thu 16 | 0 | 0.0 | 1110 ms | 0 |
| Thu 18 | 0 | 0.0 | 903 ms | 0 |
| Thu 20 | 0 | 0.0 | 598 ms | 0 |
| Thu 22 | 0 | 0.0 | 1376 ms | 0 |
| Fri 00 | 0 | 0.0 | 1583 ms | 0 |
| Fri 02 | 0 | 0.0 | 964 ms | 0 |
| Fri 04 | 0 | 0.0 | 1310 ms | 0 |
| Fri 06 | 0 | 0.0 | 979 ms | 0 |
| Fri 08 | 0 | 0.0 | 1262 ms | 0 |
| Fri 10 | 0 | 0.0 | 1196 ms | 0 |
| Fri 11 | 0 | 0.0 | 925 ms | 0 |
| Fri 12 | 0 | 0.0 | 1196 ms | 0 |
| Fri 14 | 0 | 0.0 | 1444 ms | 0 |
| Fri 16 | 0 | 0.0 | 345 ms | 0 |
| Fri 17 | 0 | 0.0 | 1194 ms | 0 |
| Fri 18 | 0 | 0.0 | 1421 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Monotype 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 Monotype goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Monotype alerts to Slack, Discord or a webhook — free.
Monotype, at monotype.com, is one of the AI services we monitor. Search 400,000+ fonts, manage licensing, and deploy typography globally. Monotype brings font tools, services, and workflows together.
Monotype publishes an official status page at status.monotype.com; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 1128 ms average, 345–1583 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 Monotype incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
1128 ms on average over the last 24 hours (345–1583 ms).
Yes, at https://status.monotype.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Monotype here at once, the problem is on Monotype'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 Monotype. 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.