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 1 hr ago. Last stored result reached it in 757 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 |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 2431 ms | 0 |
| Nov 7 | 0 | 0.0 | 3541 ms | 0 |
| Nov 7 | 0 | 0.0 | 1742 ms | 0 |
| Nov 7 | 0 | 0.0 | 3834 ms | 0 |
| Nov 7 | 0 | 0.0 | 3579 ms | 0 |
| Nov 8 | 0 | 0.0 | 3728 ms | 0 |
| Nov 8 | 0 | 0.0 | 367 ms | 0 |
| Nov 8 | 0 | 0.0 | 697 ms | 0 |
| Nov 8 | 0 | 0.0 | 629 ms | 0 |
| Nov 9 | 0 | 0.0 | 569 ms | 0 |
| Nov 9 | 0 | 0.0 | 616 ms | 0 |
| Nov 9 | 0 | 0.0 | 633 ms | 0 |
| Nov 9 | 0 | 0.0 | 541 ms | 0 |
| Nov 10 | 0 | 0.0 | 595 ms | 0 |
| Nov 10 | 0 | 0.0 | 671 ms | 0 |
| Nov 10 | 0 | 0.0 | 574 ms | 0 |
| Nov 10 | 0 | 0.0 | 685 ms | 0 |
| Nov 11 | 0 | 0.0 | 694 ms | 0 |
| Nov 11 | 0 | 0.0 | 578 ms | 0 |
| Nov 11 | 0 | 0.0 | 696 ms | 0 |
| Nov 11 | 0 | 0.0 | 735 ms | 0 |
| Nov 12 | 0 | 0.0 | 783 ms | 0 |
| Nov 12 | 0 | 0.0 | 626 ms | 0 |
| Nov 12 | 0 | 0.0 | 728 ms | 0 |
| Nov 12 | 0 | 0.0 | 645 ms | 0 |
| Nov 13 | 0 | 0.0 | 973 ms | 0 |
| Nov 13 | 0 | 0.0 | 530 ms | 0 |
| Nov 13 | 0 | 0.0 | 540 ms | 0 |
| Nov 13 | 0 | 0.0 | 550 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: 628 ms average, 358–1003 ms range across 14 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?
628 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.