User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Education
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 9 min ago. Last stored result reached it in 63 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 22 | 0 | 0.0 | 250 ms | 0 |
| Wed 00 | 0 | 0.0 | 130 ms | 0 |
| Wed 02 | 0 | 0.0 | 190 ms | 0 |
| Wed 04 | 0 | 0.0 | 124 ms | 0 |
| Wed 06 | 0 | 0.0 | 126 ms | 0 |
| Wed 09 | 0 | 0.0 | 305 ms | 0 |
| Wed 11 | 0 | 0.0 | 97 ms | 0 |
| Wed 13 | 0 | 0.0 | 120 ms | 0 |
| Wed 15 | 0 | 0.0 | 96 ms | 0 |
| Wed 17 | 0 | 0.0 | 99 ms | 0 |
| Wed 20 | 0 | 0.0 | 218 ms | 0 |
| Wed 22 | 0 | 0.0 | 279 ms | 0 |
| Thu 00 | 0 | 0.0 | 290 ms | 0 |
| Thu 02 | 0 | 0.0 | 329 ms | 0 |
| Thu 04 | 0 | 0.0 | 230 ms | 0 |
| Thu 06 | 0 | 0.0 | 168 ms | 0 |
| Thu 08 | 0 | 0.0 | 69 ms | 0 |
| Thu 10 | 0 | 0.0 | 275 ms | 0 |
| Thu 12 | 0 | 0.0 | 152 ms | 0 |
| Thu 14 | 0 | 0.0 | 125 ms | 0 |
| Thu 17 | 0 | 0.0 | 106 ms | 0 |
| Thu 19 | 0 | 0.0 | 215 ms | 0 |
| Thu 21 | 0 | 0.0 | 385 ms | 0 |
| Thu 23 | 0 | 0.0 | 54 ms | 0 |
| Fri 01 | 0 | 0.0 | 148 ms | 0 |
| Fri 03 | 0 | 0.0 | 110 ms | 0 |
| Fri 05 | 0 | 0.0 | 116 ms | 0 |
| Fri 06 | 0 | 0.0 | 32 ms | 0 |
| Fri 09 | 0 | 0.0 | 237 ms | 0 |
| Fri 11 | 0 | 0.0 | 127 ms | 0 |
| Fri 12 | 0 | 0.0 | 91 ms | 0 |
| Fri 14 | 0 | 0.0 | 53 ms | 0 |
| Fri 16 | 0 | 0.0 | 262 ms | 0 |
| Fri 18 | 0 | 0.0 | 107 ms | 0 |
| Fri 19 | 0 | 0.0 | 241 ms | 0 |
| Fri 21 | 0 | 0.0 | 114 ms | 0 |
| Fri 23 | 0 | 0.0 | 127 ms | 0 |
| Sat 02 | 0 | 0.0 | 440 ms | 0 |
| Sat 04 | 0 | 0.0 | 121 ms | 0 |
| Sat 06 | 0 | 0.0 | 97 ms | 0 |
| Sat 07 | 0 | 0.0 | 67 ms | 0 |
| Sat 09 | 0 | 0.0 | 282 ms | 0 |
| Sat 11 | 0 | 0.0 | 95 ms | 0 |
| Sat 13 | 0 | 0.0 | 35 ms | 0 |
| Sat 16 | 0 | 0.0 | 124 ms | 0 |
| Sat 18 | 0 | 0.0 | 126 ms | 0 |
| Sat 20 | 0 | 0.0 | 63 ms | 0 |
| Sat 22 | 0 | 0.0 | 305 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Center for Open Science 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 Center for Open Science goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
Center for Open Science, at cos.io, is one of the Education services we monitor. At the Center for Open Science, our mission is to increase openness, integrity, and reproducibility of scholarly research. Promoting these practices within the research funding and publishing communities accelerates scientific progress
Center for Open Science publishes an official status page at status.cos.io; when we can read it, its incident level is folded into the status shown here.
Typical issues with education services: learning management systems and student portals slowing down around assignment deadlines, exams and registration.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 150 ms average, 35–440 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 Center for Open Science incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
150 ms on average over the last 24 hours (35–440 ms).
Yes, at https://status.cos.io.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For education services, watch for learning management systems and student portals slowing down around assignment deadlines, exams and registration. If many people report Center for Open Science here at once, the problem is on Center for Open Science'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 Center for Open Science. 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.