RIPE NCC logo

Is RIPE NCC Down?

SaaSLive status, outages, and incident history

No. RIPE NCC is up right now.

Every monitored RIPE NCC system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 2m agoLive · 60s while moving

Know the moment RIPE NCC breaks

RIPE NCC is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official RIPE NCC status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

RIPE NCC Component Status

The main RIPE NCC systems on this page. All 25 are operational right now.

25operational
Email to/from the RIPE NCC
Operational
K-root/DNS
Operational
LIR (Member) Portal
Operational

22 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Non-Critical Services » Billing & Payments, Non-Critical Services » DNSMON, Non-Critical Services » ftp.ripe.net, Non-Critical Services » Mailing Lists, Non-Critical Services » Meeting Registration Software, Non-Critical Services » Meeting Sites Platform, Non-Critical Services » Meeting Software, Non-Critical Services » Pilot, Non-Critical Services » RIPE Atlas, Non-Critical Services » RIPE Labs, Non-Critical Services » RIPE NCC Academy, Non-Critical Services » RIPE NCC Certified Professionals, and 10 more.

See all of them free

Component statuses may change independently during partial outages.

Recent RIPE NCC Outages & Incidents

Incident history from the official RIPE NCC status page, including resolution updates.

Planned Maintenance: RIPE NCC Access Account (SSO), LIR Portal, RIPE Database and RPKI DashboardScheduled for Oct 1, 2026 · 30 minScheduled

We will be undergoing scheduled maintenance this time.

Planned Maintenance: RIPE AtlasScheduled for Sep 23, 2026 · 30 minScheduled

The scheduled maintenance has been completed. --- [2026-09-23T09:23:21.720+02:00] (in_progress) Scheduled maintenance is still in progress. We will provide updates as necessary. --- [2026-09-23T09:00:22.794+02:00] (in_progress) Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-09-23T08:47:48.301+02:00] (scheduled) We will carry out planned maintenance on RIPE Atlas. During this time, RIPE Atlas will be unavailable or not fully functional.

RPKI Test Environment: external APIs are not workingResolved Sep 17, 2026 · 37 minResolved

This incident has been resolved. --- [2026-09-17T14:45:05.486+02:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-09-17T14:43:28.803+02:00] (identified) The issue has been identified and a fix is being implemented. --- [2026-09-17T14:22:15.370+02:00] (investigating) We are currently investigating this issue.

RIPE NCC Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a RIPE NCC incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 16 days with incidentsSep 25

Live RIPE NCC Outage Reports

Problems reported by engineers using RIPE NCC. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No RIPE NCC problems reported yet.

Something wrong with RIPE NCC on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About RIPE NCC

RIPE NCC exposes 27 monitored components on its status page at status.ripe.net — RIPE Database, Billing & Payments and RPKI Dashboard among them. Follow RIPE NCC downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

Over the past 30 days, PulsAPI has measured RIPE NCC uptime at 99.88%. Response times, incident history, and SLA tracking for RIPE NCC are available on the PulsAPI dashboard.

RIPE NCC Status FAQ

Is RIPE NCC down right now?

The verdict at the top of this page comes from the latest poll of the official RIPE NCC status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if RIPE NCC is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until RIPE NCC recovers.

How do I check RIPE NCC uptime history?

PulsAPI tracks RIPE NCC uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.88%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever RIPE NCC changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect RIPE NCC outages?

PulsAPI reads the official RIPE NCC status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual RIPE NCC components?

Yes. PulsAPI monitors 25 individual RIPE NCC components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when RIPE NCC goes down?

Yes. Create a free account and subscribe to RIPE NCC: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with RIPE NCC to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot RIPE NCC problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor RIPE NCC?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so RIPE NCC plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track RIPE NCC with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services