User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
opensanctions.org · Cloud & developer
Is OpenSanctions down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → opensanctions.org—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 20 min ago. Last stored result reached it in 567 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 523 ms | 0 |
| Mon 17 | 0 | 0.0 | 545 ms | 0 |
| Mon 19 | 0 | 0.0 | 501 ms | 0 |
| Mon 21 | 0 | 0.0 | 451 ms | 0 |
| Mon 23 | 0 | 0.0 | 382 ms | 0 |
| Tue 01 | 0 | 0.0 | 612 ms | 0 |
| Tue 03 | 0 | 0.0 | 452 ms | 0 |
| Tue 05 | 0 | 0.0 | 339 ms | 0 |
| Tue 08 | 0 | 0.0 | 468 ms | 0 |
| Tue 10 | 0 | 0.0 | 332 ms | 0 |
| Tue 12 | 0 | 0.0 | 403 ms | 0 |
| Tue 14 | 0 | 0.0 | 472 ms | 0 |
| Tue 16 | 0 | 0.0 | 700 ms | 0 |
| Tue 19 | 0 | 0.0 | 461 ms | 0 |
| Tue 21 | 0 | 0.0 | 474 ms | 0 |
| Tue 23 | 0 | 0.0 | 430 ms | 0 |
| Wed 01 | 0 | 0.0 | 1187 ms | 0 |
| Wed 04 | 0 | 0.0 | 254 ms | 0 |
| Wed 06 | 0 | 0.0 | 377 ms | 0 |
| Wed 08 | 0 | 0.0 | 522 ms | 0 |
| Wed 10 | 0 | 0.0 | 695 ms | 0 |
| Wed 12 | 0 | 0.0 | 1198 ms | 0 |
| Wed 14 | 0 | 0.0 | 413 ms | 0 |
| Wed 16 | 0 | 0.0 | 577 ms | 0 |
| Wed 18 | 0 | 0.0 | 535 ms | 0 |
| Wed 20 | 0 | 0.0 | 450 ms | 0 |
| Wed 22 | 0 | 0.0 | 358 ms | 0 |
| Thu 00 | 0 | 0.0 | 585 ms | 0 |
| Thu 02 | 0 | 0.0 | 339 ms | 0 |
| Thu 05 | 0 | 0.0 | 487 ms | 0 |
| Thu 07 | 0 | 0.0 | 289 ms | 0 |
| Thu 09 | 0 | 0.0 | 345 ms | 0 |
| Thu 11 | 0 | 0.0 | 499 ms | 0 |
| Thu 13 | 0 | 0.0 | 536 ms | 0 |
| Thu 15 | 0 | 0.0 | 291 ms | 0 |
| Thu 17 | 0 | 0.0 | 288 ms | 0 |
| Thu 19 | 0 | 0.0 | 417 ms | 0 |
| Thu 21 | 0 | 0.0 | 423 ms | 0 |
| Thu 23 | 0 | 0.0 | 705 ms | 0 |
| Fri 01 | 0 | 0.0 | 419 ms | 0 |
| Fri 03 | 0 | 0.0 | 297 ms | 0 |
| Fri 05 | 0 | 0.0 | 336 ms | 0 |
| Fri 07 | 0 | 0.0 | 830 ms | 0 |
| Fri 09 | 0 | 0.0 | 629 ms | 0 |
| Fri 11 | 0 | 0.0 | 317 ms | 0 |
| Fri 14 | 0 | 0.0 | 389 ms | 0 |
| Fri 16 | 0 | 0.0 | 509 ms | 0 |
| Fri 17 | 0 | 0.0 | 400 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live OpenSanctions badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for OpenSanctions yet. Outages of 10 minutes or more get their own page here.
Having trouble with OpenSanctions?
One report per service every 10 minutes from this network. No account.
Follow OpenSanctions
Get an email when OpenSanctions goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send OpenSanctions alerts to Slack, Discord or a webhook — free.
About OpenSanctions
We track OpenSanctions (opensanctions.org) as part of the Cloud & developer group. The open-source database of sanctions, watchlists, and politically exposed persons — aggregating hundreds of sources and relied on by compliance teams, investigators, and journalists.
OpenSanctions publishes an official status page at status.opensanctions.org; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 475 ms average, 297–830 ms range across 13 successful checks.
Questions
Is OpenSanctions down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was OpenSanctions last down?
We have not recorded a public OpenSanctions incident since monitoring began 8 days ago.
What is OpenSanctions's uptime?
From our own checks: 100% over 8 days of checks.
How fast does OpenSanctions respond?
475 ms on average over the last 24 hours (297–830 ms).
Does OpenSanctions have an official status page?
Yes, at https://status.opensanctions.org.
OpenSanctions not working for me but the status is fine. What now?
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 OpenSanctions here at once, the problem is on OpenSanctions'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 OpenSanctions. 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.