Status updated

All Systems Operational
RIPE NCC logo

RIPE NCC down?

RIPE NCC (Réseaux IP Européens Network Coordination Centre) is the Regional Internet Registry for Europe, the Middle East and parts of Central Asia, headquartered in Amsterdam. It allocates and registers IP addresses and Autonomous System numbers to its members, such as internet service providers, telecoms, governments and enterprises. RIPE NCC maintains the RIPE Database, operates the K-root DNS server, and provides tools like RIPE Atlas and RIPEstat for measuring and analysing the internet. It also supports the open RIPE community and its policy development.

RIPE NCC status preview image

I have a problem with RIPE NCC

Select the type of problem you're facing to help us and other users.

Recent User Report Trends for RIPE NCC

Aggregated reports in the last 48 hours.

No user reports about RIPE NCC in the last 48 hours.

uptimecard

View live report trends

Add your report to help, or tap to skip

What is RIPE NCC's current status?

All systems are operational

A recent issue has been resolved. Details below.

Incident history: past 7 days

times in UTC

Yesterday

No incidents reported.

Nov 7, 2026

No incidents reported.

Nov 6, 2026

No incidents reported.

Nov 5, 2026

No incidents reported.

Nov 4, 2026

No incidents reported.

User Reports for RIPE NCC

Recent issues reported by users from around the world.

No user reports for RIPE NCC in the last 30 days.

Experiencing an issue? Add your report:

Stop refreshing this page

We'll email you the moment RIPE NCC goes down — and again when it's back.

About RIPE NCC & Technical Insights

What this service does and the technologies behind it.

Loading tech map…
Read the tech stack as text▾

Overview: A privacy-conscious, standards-driven registry stack: Python/Django content management, edge-secured by Akamai, with modern React/Tailwind interfaces for a technical global audience.

What stands out

  • Wagtail and Django indicate a mature editorial workflow for policy documents, not a marketing site.
  • Piwik PRO Core plus Akamai suggests GDPR-aligned analytics and edge security are prioritized over ad-tech monetization.
  • Presence of both PHP and Python points to incremental modernization with legacy components still active.
  • Onsen UI and PWA hint at mobile tooling for network operators, aligning with RIPE's technical member services.

Technologies ripe.net uses

  • Wagtail — Wagtail, a Django CMS, powers RIPE's policy, news, and documentation with structured editorial workflows.
  • Python — Python underpins Django, automation, and network data processing central to an Internet registry.
  • Nginx — Nginx serves as reverse proxy or origin for RIPE's web applications.
  • Tailwind CSS — Utility-first CSS speeds consistent UI development across RIPE's many content and tool pages.
  • Akamai Bot Manager — Akamai Bot Manager protects public registry interfaces from scraping, abuse, and automated attacks.
  • Akamai — Akamai CDN ensures global low-latency delivery and DDoS resilience for RIPE's distributed audience.
  • React — React powers interactive frontend components.
  • Onsen UI — Mobile UI toolkit suggests RIPE builds cross-platform member or operator tools beyond static web pages.
  • Piwik PRO Core — Privacy-focused analytics chosen for GDPR compliance and data sovereignty, critical for a European registry.
  • HeroUI — React component library signals a modern design system for interactive member dashboards or data tools.
  • RSS — RSS feeds distribute policy updates and technical news to the operator community.
  • Django — Django provides the Python web framework for Wagtail and RIPE's custom registry-backed services.
  • PHP — Legacy PHP components likely support older tools or web forms.
  • HSTS — HSTS enforces HTTPS for security-sensitive registry data.
  • PWA — PWA hints at offline-capable or installable member tools for network engineers.
  • Open Graph — Open Graph optimizes link sharing for RIPE announcements.
  • HTTP/3 — HTTP/3 improves performance for global users.

How these technologies work together

  • Django runs on Wagtail — Wagtail is built as a Django application, so Django provides the models, admin, and request layer for RIPE's content site.
  • Django requires Python — Django cannot run without Python; together they handle RIPE's registry data, CMS, and backend services.
  • Akamai runs on Akamai Bot Manager — Akamai Bot Manager runs on Akamai's edge platform, protecting RIPE's public registry from automated abuse.
  • HeroUI requires React — HeroUI is a React component library, indicating RIPE's interactive tools are built on a React frontend.
  • Akamai integrates with Nginx — Akamai fronts RIPE's nginx origin, caching and filtering traffic before it reaches backend servers.
  • Nginx runs on PHP — Nginx serves PHP applications via FastCGI, supporting any legacy or auxiliary RIPE web tools.
  • RSS integrates with Wagtail — Wagtail can generate RSS feeds for RIPE's news and policy updates, reaching technical subscribers.
  • HeroUI integrates with Tailwind CSS — HeroUI uses Tailwind CSS for styling, so both work together to deliver a consistent design system.
  • Akamai integrates with HTTP/3 — Akamai supports HTTP/3 at the edge, delivering RIPE's global content faster over QUIC.
  • Django overlaps with PHP — PHP and Django coexist, suggesting legacy PHP tools alongside modern Python services—potential maintenance overhead.
  • Onsen UI works alongside PWA — Onsen UI's mobile-first components pair naturally with a PWA to create app-like experiences for members.
  • Tailwind CSS works alongside Wagtail — Tailwind CSS styles Wagtail templates, giving RIPE's content pages a modern, maintainable visual system.
  • Django integrates with Piwik PRO Core — Piwik PRO tags are embedded in Django-rendered templates to track RIPE's content without compromising privacy.
  • Open Graph integrates with Wagtail — Wagtail templates generate Open Graph metadata for RIPE's shared announcements and policy pages.
  • PWA works alongside React — React enables the interactive components used in a progressive web app for member self-service.
  • Onsen UI integrates with React — Onsen UI can integrate with React, suggesting RIPE builds cross-platform mobile interfaces for network operators.
  • Akamai integrates with HSTS — Akamai edge enforces HSTS headers for RIPE, ensuring secure connections globally.
Analytics
Piwik PRO CorePiwik PRO Core
Content
WagtailWagtail
Other
PWAPWA
HTTP/3HTTP/3
Open GraphOpen Graph
RSSRSS
Servers
AkamaiAkamai
NginxNginx
Web Development
DjangoDjango
PythonPython
Onsen UIOnsen UI
HeroUIHeroUI
HSTSHSTS
ReactReact
PHPPHP
Akamai Bot ManagerAkamai Bot Manager
Tailwind CSSTailwind CSS

Trust & Safety Checks

Public registration, DNS and certificate records UptimeCard checked independently for the domain ripe.net.

Secure, encrypted connection

Everything sent between visitors and this site travels encrypted.

Domain name active since 1992

ripe.net has been a registered domain since February 1992 — 34 years at the same web address.

Domain lock enabled

The registry blocks unauthorised transfers, so the domain cannot be hijacked.

Registered through 2027

The owner has kept this domain secured until February 2027.

Redundant DNS setup

5 nameservers answer for this domain, so it stays reachable even if one goes offline.

Hosted by Reseaux IP Europeens Network Coordination Centre (RIPE NCC)

Served from professional infrastructure located in Netherlands.

Records last verified September 2026.

How to fix RIPE NCC not working

RIPE NCC is the regional internet registry for Europe, the Middle East and parts of Central Asia. It manages internet number resources, runs a database of registrations, the WHOIS service and the RIPE Atlas network measurement platform. Network operators and researchers use its services. Find your symptom below. Most problems come from a sign-in, a database search or query, a service that is busy, or an outage. Check the status page before you rely on a result for a live decision.

Jump to what you are seeing

Website Down

The RIPE NCC website does not load for you.

  1. Open the page in a private window and on another network.
  2. Check status.ripe.net for an active incident.
  3. If only your network is affected, ask IT to check the firewall.

Database Search Failed

A database search returns an error, or it returns no results.

  1. Check the search term is typed correctly, and that you have chosen the right object type.
  2. Try a shorter search, and check the search is not limited by a filter.
  3. Check status.ripe.net, and report the search term and the time if it fails for everyone.

Login Failed

Sign-in is refused.

  1. If the password is refused, reset it through the official route and check spam.
  2. Check you are using the account that holds your organisation's registration.
  3. Try a private window to rule out an old session.

WHOIS Service Down

The WHOIS lookup does not respond, or it returns an error.

  1. Retry after a short wait, since the service can be busy.
  2. Check status.ripe.net for an incident affecting the WHOIS service.
  3. If it stays down, use another official lookup route, and report the time.

API Error

Calls to a RIPE NCC API fail or return an error.

  1. Check the status code. An access error usually means the credentials are wrong, too many calls means you should slow down, and a server error means a service-side problem.
  2. Confirm the credentials are current, and that the request follows the usage rules.
  3. Retry with a growing delay, and check status.ripe.net if several calls fail together.

RIPE Atlas Down

RIPE Atlas probes do not report, or measurements do not run.

  1. Check the probe is online and has a working internet connection.
  2. Check the measurement's settings and the probes it uses are still available.
  3. Check status.ripe.net, and report the probe ID and the time if it stays offline.

Slow Response

Pages and lookups take a long time to respond.

  1. Try again at a quieter time of day.
  2. Narrow the lookup, and avoid very large queries.
  3. If it is slow for everyone, check status.ripe.net.

Still not working?

Contact your organisation's RIPE NCC contact, or your network administrator, first, since they hold the registration. For a platform-wide problem, contact RIPE NCC support through the help route on the RIPE NCC website. Have your organisation name, the resource or probe ID, the search term or measurement ID, the exact error text, and the time with your time zone. Never send passwords or private network configuration in a support message. Live incident updates are on status.ripe.net.

Most registry-service problems come from a busy service, a search setting or a sign-in, and they usually clear after a short wait. The status page shows live incidents, so you can see whether the problem is on the registry's side.

Frequently asked questions about RIPE NCC

Is RIPE NCC down right now?

No. Based on the latest status data on this page, RIPE NCC (ripe.net) is up and running normally. The most recent incident, "RIPEstat APIs unavailable", was resolved (last update Nov 9, 2026).

What should I do if RIPE NCC is not working for me?

First rule out your side: reload the page, try another browser or device, clear the cache and cookies for ripe.net, flush your DNS cache and turn off any VPN or proxy. Then compare with this page: if the status shows an incident, or many users reported problems in the last 48 hours, the issue is on the service's end and usually clears up without any action from you. The troubleshooting steps on this page go through each check in order.

What was the most recent RIPE NCC incident?

The most recent incident on record is "RIPEstat APIs unavailable", last updated on Nov 9, 2026. It has been resolved.

How many people reported problems with RIPE NCC recently?

No user reports about RIPE NCC were submitted in the last 48 hours.

How do I report a problem with RIPE NCC?

Use the report buttons at the top of this page, or describe the problem in the user reports section. Every report is counted in the 48-hour trend chart and helps other people see whether the problem is widespread.

Where is the official RIPE NCC status page?

The official status page for RIPE NCC is status.ripe.net.

Related Services & Domains

Other websites and services in the same category as ripe.net.


Related Keywords

Common themes, topics and technologies associated with ripe.net.

RIPE NCCIP address allocationIPv4 exhaustionIPv6 deploymentWHOIS databaseAS numbersAutonomous SystemInternet RegistryRegional Internet RegistryRIRRIPE AtlasNetwork coordinationInternet governanceBGP routingLIRLocal Internet RegistryIP address lookupReverse DNSK-root serverRIPE DatabasePeering DBInternet resource managementNetwork measurementRIPE MeetingsInternet number resourcesASN lookupIP block assignmentRIPE policyInternet infrastructureRIPE NCC trainingRIPEstatRouting Information ServiceInternet routing registryIRRIPv4 transferSubnettingNetwork topologyEuropean IP networksInternet standardsRIPE NCC membership
    Is RIPE NCC down? See if Ripe.net is not working or has problems