User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Social
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: http://purl.org/dc/terms/, http://purl.org/dc/dcmitype/, and 5 other services are down | http://purl.org/dc/terms/, http://purl.org/dc/dcmitype/, and 5 other services are down |...
Source: the vendor's status page · We are not affiliated with DCMI.
Estimated fix: Not enough DCMI history yet; similar Social outages lasted 2 h (median, typically 27 min–7 h; 13 outages).
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 2 hr ago. Last stored result reached it in 177 ms.
Minor incident
http://purl.org/dc/terms/, http://purl.org/dc/dcmitype/, and 5 other services are down | http://purl.org/dc/terms/, http://purl.org/dc/dcmitype/, and 5 other services are down | http://purl.org/dc/terms/, http://purl.org/dc/dcmitype/, and 5 other services are down | http://purl.org/dc/terms/, http:/ Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 167 ms | 0 |
| Mon 22 | 0 | 0.0 | 155 ms | 0 |
| Tue 00 | 0 | 0.0 | 180 ms | 0 |
| Tue 02 | 0 | 0.0 | 168 ms | 0 |
| Tue 04 | 0 | 0.0 | 106 ms | 0 |
| Tue 07 | 0 | 0.0 | 95 ms | 0 |
| Tue 09 | 0 | 0.0 | 115 ms | 0 |
| Tue 11 | 0 | 0.0 | 65 ms | 0 |
| Tue 13 | 0 | 0.0 | 65 ms | 0 |
| Tue 15 | 0 | 0.0 | 130 ms | 0 |
| Tue 17 | 0 | 0.0 | 78 ms | 0 |
| Tue 20 | 0 | 0.0 | 163 ms | 0 |
| Tue 22 | 0 | 0.0 | 163 ms | 0 |
| Wed 00 | 0 | 0.0 | 95 ms | 0 |
| Wed 02 | 0 | 0.0 | 175 ms | 0 |
| Wed 05 | 0 | 0.0 | 218 ms | 0 |
| Wed 07 | 0 | 0.0 | 62 ms | 0 |
| Wed 09 | 0 | 0.0 | 106 ms | 0 |
| Wed 11 | 0 | 0.0 | 62 ms | 0 |
| Wed 13 | 0 | 0.0 | 113 ms | 0 |
| Wed 15 | 0 | 0.0 | 106 ms | 0 |
| Wed 18 | 0 | 0.0 | 558 ms | 0 |
| Wed 20 | 0 | 0.0 | 150 ms | 0 |
| Wed 22 | 0 | 0.0 | 160 ms | 0 |
| Thu 00 | 0 | 0.0 | 176 ms | 0 |
| Thu 02 | 0 | 0.0 | 104 ms | 0 |
| Thu 04 | 0 | 0.0 | 374 ms | 0 |
| Thu 06 | 0 | 0.0 | 85 ms | 0 |
| Thu 08 | 0 | 0.0 | 89 ms | 0 |
| Thu 10 | 0 | 0.0 | 65 ms | 0 |
| Thu 12 | 0 | 0.0 | 110 ms | 0 |
| Thu 14 | 0 | 0.0 | 157 ms | 0 |
| Thu 16 | 0 | 0.0 | 116 ms | 0 |
| Thu 18 | 0 | 0.0 | 157 ms | 0 |
| Thu 20 | 0 | 0.0 | 97 ms | 0 |
| Thu 22 | 0 | 0.0 | 142 ms | 0 |
| Fri 00 | 0 | 0.0 | 86 ms | 0 |
| Fri 01 | 0 | 0.0 | 72 ms | 0 |
| Fri 03 | 0 | 0.0 | 121 ms | 0 |
| Fri 05 | 0 | 0.0 | 63 ms | 0 |
| Fri 07 | 0 | 0.0 | 163 ms | 0 |
| Fri 09 | 0 | 0.0 | 68 ms | 0 |
| Fri 10 | 0 | 0.0 | 92 ms | 0 |
| Fri 11 | 0 | 0.0 | 64 ms | 0 |
| Fri 12 | 0 | 0.0 | 70 ms | 0 |
| Fri 14 | 0 | 0.0 | 109 ms | 0 |
| Fri 16 | 0 | 0.0 | 148 ms | 0 |
| Fri 18 | 0 | 0.0 | 177 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 DCMI 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 DCMI goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send DCMI alerts to Slack, Discord or a webhook — free.
DCMI, at dublincore.org, is one of the Social services we monitor. The Dublin Core Metadata Initiative (DCMI) is an open forum engaged in metadata innovation and support the development of interoperable online metadata standards that support a broad range of purposes and business models. DCMI's activities include
DCMI publishes an official status page at status.dublincore.org; when we can read it, its incident level is folded into the status shown here.
Common problems for social services: feeds not loading, posts or messages not sending, and login loops.
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: 105 ms average, 63–177 ms range across 14 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: http://purl.org/dc/terms/, http://purl.org/dc/dcmitype/, and 5 other services are down | http://purl.org/dc/terms/, http://purl.org/dc/dcmitype/, and 5 other services are down |...
We have not recorded a public DCMI incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
105 ms on average over the last 24 hours (63–177 ms).
Yes, at https://status.dublincore.org.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For social services, watch for feeds not loading, posts or messages not sending, and login loops. If many people report DCMI here at once, the problem is on DCMI'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 DCMI. 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.