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 59 min ago. Last stored result reached it in 953 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 11 | 0 | 0.0 | 894 ms | 0 |
| Tue 13 | 0 | 0.0 | 921 ms | 0 |
| Tue 14 | 0 | 0.0 | 765 ms | 0 |
| Tue 16 | 0 | 0.0 | 847 ms | 0 |
| Tue 18 | 0 | 0.0 | 622 ms | 0 |
| Tue 20 | 0 | 0.0 | 787 ms | 0 |
| Tue 23 | 0 | 0.0 | 892 ms | 0 |
| Wed 01 | 0 | 0.0 | 784 ms | 0 |
| Wed 03 | 0 | 0.0 | 868 ms | 0 |
| Wed 05 | 0 | 0.0 | 895 ms | 0 |
| Wed 08 | 0 | 0.0 | 1007 ms | 0 |
| Wed 10 | 0 | 0.0 | 1040 ms | 0 |
| Wed 12 | 0 | 0.0 | 948 ms | 0 |
| Wed 14 | 0 | 0.0 | 892 ms | 0 |
| Wed 16 | 0 | 0.0 | 752 ms | 0 |
| Wed 18 | 0 | 0.0 | 792 ms | 0 |
| Wed 21 | 0 | 0.0 | 912 ms | 0 |
| Wed 22 | 0 | 0.0 | 927 ms | 0 |
| Thu 00 | 0 | 0.0 | 913 ms | 0 |
| Thu 02 | 0 | 0.0 | 949 ms | 0 |
| Thu 04 | 0 | 0.0 | 894 ms | 0 |
| Thu 06 | 0 | 0.0 | 916 ms | 0 |
| Thu 08 | 0 | 0.0 | 755 ms | 0 |
| Thu 10 | 0 | 0.0 | 889 ms | 0 |
| Thu 12 | 0 | 0.0 | 916 ms | 0 |
| Thu 15 | 0 | 0.0 | 744 ms | 0 |
| Thu 17 | 0 | 0.0 | 782 ms | 0 |
| Thu 19 | 0 | 0.0 | 769 ms | 0 |
| Thu 21 | 0 | 0.0 | 894 ms | 0 |
| Thu 23 | 0 | 0.0 | 862 ms | 0 |
| Fri 00 | 0 | 0.0 | 769 ms | 0 |
| Fri 02 | 0 | 0.0 | 873 ms | 0 |
| Fri 04 | 0 | 0.0 | 759 ms | 0 |
| Fri 06 | 0 | 0.0 | 782 ms | 0 |
| Fri 08 | 0 | 0.0 | 906 ms | 0 |
| Fri 10 | 0 | 0.0 | 651 ms | 0 |
| Fri 11 | 0 | 0.0 | 873 ms | 0 |
| Fri 12 | 0 | 0.0 | 878 ms | 0 |
| Fri 14 | 0 | 0.0 | 885 ms | 0 |
| Fri 17 | 0 | 0.0 | 829 ms | 0 |
| Fri 19 | 0 | 0.0 | 837 ms | 0 |
| Fri 20 | 0 | 0.0 | 869 ms | 0 |
| Fri 22 | 0 | 0.0 | 944 ms | 0 |
| Sat 00 | 0 | 0.0 | 874 ms | 0 |
| Sat 02 | 0 | 0.0 | 914 ms | 0 |
| Sat 04 | 0 | 0.0 | 914 ms | 0 |
| Sat 06 | 0 | 0.0 | 937 ms | 0 |
| Sat 08 | 0 | 0.0 | 953 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 OECD.AI 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 OECD.AI goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send OECD.AI alerts to Slack, Discord or a webhook — free.
OECD.AI is listed in our AI category and checked at oecd.ai. OECD.AI helps countries and shape trustworthy AI with the OECD AI Principles. It gives access to 900+ national AI policies and initiatives, live data about AI and a blog about AI policy.
OECD.AI publishes an official status page at status.oecd.ai; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 855 ms average, 381–953 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public OECD.AI incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
855 ms on average over the last 24 hours (381–953 ms).
Yes, at https://status.oecd.ai.
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 OECD.AI here at once, the problem is on OECD.AI'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 OECD.AI. 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.