User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is RIPE NCC 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 → ripe.net—
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 2 hr ago. Last stored result reached it in 550 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 568 ms | 0 |
| Mon 17 | 0 | 0.0 | 633 ms | 0 |
| Mon 19 | 0 | 0.0 | 541 ms | 0 |
| Mon 21 | 0 | 0.0 | 586 ms | 0 |
| Mon 23 | 0 | 0.0 | 354 ms | 0 |
| Tue 01 | 0 | 0.0 | 655 ms | 0 |
| Tue 04 | 0 | 0.0 | 595 ms | 0 |
| Tue 06 | 0 | 0.0 | 602 ms | 0 |
| Tue 08 | 0 | 0.0 | 694 ms | 0 |
| Tue 11 | 0 | 0.0 | 671 ms | 0 |
| Tue 13 | 0 | 0.0 | 574 ms | 0 |
| Tue 15 | 0 | 0.0 | 656 ms | 0 |
| Tue 17 | 0 | 0.0 | 444 ms | 0 |
| Tue 20 | 0 | 0.0 | 790 ms | 0 |
| Tue 22 | 0 | 0.0 | 580 ms | 0 |
| Wed 00 | 0 | 0.0 | 623 ms | 0 |
| Wed 02 | 0 | 0.0 | 784 ms | 0 |
| Wed 04 | 0 | 0.0 | 694 ms | 0 |
| Wed 07 | 0 | 0.0 | 794 ms | 0 |
| Wed 09 | 0 | 0.0 | 578 ms | 0 |
| Wed 11 | 0 | 0.0 | 486 ms | 0 |
| Wed 13 | 0 | 0.0 | 790 ms | 0 |
| Wed 15 | 0 | 0.0 | 366 ms | 0 |
| Wed 17 | 0 | 0.0 | 696 ms | 0 |
| Wed 20 | 0 | 0.0 | 1094 ms | 0 |
| Wed 22 | 0 | 0.0 | 376 ms | 0 |
| Thu 00 | 0 | 0.0 | 783 ms | 0 |
| Thu 02 | 0 | 0.0 | 1141 ms | 0 |
| Thu 04 | 0 | 0.0 | 506 ms | 0 |
| Thu 06 | 0 | 0.0 | 352 ms | 0 |
| Thu 08 | 0 | 0.0 | 1006 ms | 0 |
| Thu 10 | 0 | 0.0 | 626 ms | 0 |
| Thu 13 | 0 | 0.0 | 591 ms | 0 |
| Thu 15 | 0 | 0.0 | 728 ms | 0 |
| Thu 17 | 0 | 0.0 | 818 ms | 0 |
| Thu 19 | 0 | 0.0 | 668 ms | 0 |
| Thu 21 | 0 | 0.0 | 645 ms | 0 |
| Fri 00 | 0 | 0.0 | 973 ms | 0 |
| Fri 02 | 0 | 0.0 | 1003 ms | 0 |
| Fri 04 | 0 | 0.0 | 826 ms | 0 |
| Fri 06 | 0 | 0.0 | 449 ms | 0 |
| Fri 08 | 0 | 0.0 | 619 ms | 0 |
| Fri 10 | 0 | 0.0 | 530 ms | 0 |
| Fri 12 | 0 | 0.0 | 609 ms | 0 |
| Fri 14 | 0 | 0.0 | 358 ms | 0 |
| Fri 16 | 0 | 0.0 | 540 ms | 0 |
| Fri 18 | 0 | 0.0 | 410 ms | 0 |
| Fri 20 | 0 | 0.0 | 654 ms | 0 |
Reliability
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 RIPE NCC 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 RIPE NCC yet. Outages of 10 minutes or more get their own page here.
Having trouble with RIPE NCC?
One report per service every 10 minutes from this network. No account.
Follow RIPE NCC
Get an email when RIPE NCC goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send RIPE NCC alerts to Slack, Discord or a webhook — free.
About RIPE NCC
RIPE NCC is listed in our Cloud & developer category and checked at ripe.net. The RIPE NCC is one of five Regional Internet Registries (RIRs) providing Internet resource allocation and registration, and coordination activities.
RIPE NCC publishes an official status page at status.ripe.net; when we can read it, its incident level is folded into the status shown here.
Typical issues with 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: 618 ms average, 358–1003 ms range across 13 successful checks.
Questions
Is RIPE NCC down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was RIPE NCC last down?
We have not recorded a public RIPE NCC incident since monitoring began 8 days ago.
What is RIPE NCC's uptime?
From our own checks: 100% over 8 days of checks.
How fast does RIPE NCC respond?
618 ms on average over the last 24 hours (358–1003 ms).
Does RIPE NCC have an official status page?
Yes, at https://status.ripe.net.
RIPE NCC 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 RIPE NCC here at once, the problem is on RIPE NCC'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 RIPE NCC. 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.