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 November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 3m agoLive · every 60s

Know the moment RIPE NCC breaks

RIPE NCC is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

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

Official RIPE NCC status page
How we know: the official RIPE NCC status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

RIPE NCC Status Summary

As of 23:46 UTC on 9 November 2026, RIPE NCC is operational. PulsAPI checked RIPE NCC's official status page and found 25 of 25 components operational, with no active incidents. Over the last 30 days PulsAPI measured 99.78% uptime for RIPE NCC, counting degraded performance as up. The latest incident, "RIPEstat APIs unavailable", was on Nov 8, 2026 and lasted 17h 55m.

Cite as: PulsAPI, “RIPE NCC status”, checked 9 November 2026, 23:46 UTC. https://www.pulsapi.com/services/ripe-ncc

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.

RIPEstat APIs unavailableResolved Nov 8, 2026 · 17h 55mResolved

The last data (kafka partition) recovered at 04:46. This incident has been resolved. As a follow-up we will make changes to our alerts for this service. When a single node fails, the alert only pages during office-hours. A composite alert, based on the count of the single node alert, fires when multiple nodes are failing. This alert inherited labels that also routed it as office-hours only. --- [2026-11-08T21:06:56.532+01:00] (monitoring) The looking-glass is still recovering the data for the final peers. Around 1/10th of the peers on RRC25 are still delayed due to a high volume of messages for this part of the data. The current estimate is that this will recover around 05:00 UTC. We will update this message tomorrow. --- [2026-11-08T14:39:37.097+01:00] (monitoring) The database system has recovered. In turn this caused the API used by RIPEstat to recover. The RIPEstat API latency is recovering and API throughput is close to normal. The looking-glass database is now replaying BGP messages from the last hours and will be behind until this recovers. --- [2026-11-08T14:20:28.417+01:00] (identified) The database system used for the RIS looking glass ran out of file descriptors due to a low limit in our configuration (32k). This caused an internal API to consume all available processing slots while handling looking glass requests. We are recovering the database system. --- [2026-11-08T13:51:30.941+01:00] (investigating) Multiple RIPEstat APIs (looking-glass, ris-peers, many others) are unavailable. We received the first report in a ticket at 0:58 UTC and the issue is ongoing. We are currently investigating the issue.

RPKI Publication as a Service rejecting publicationsResolved Nov 4, 2026Resolved

On 3 November between 20.07 and 22:50 UTC the RFC8181 endpoint that provides Publication as a Service failed to validate publishers. As a result, CAs could not publish objects during that time. After restarting the system during regular maintenance the RFC8181 service (krill) came back before its configuration was made available, due to a slowdown of our storage system. This caused Krill to not recognise registered Delegated CA publishers and returned “Unknown publisher” error to every publication request. After the problem was reported by one of our members, our 24/7 engineer resolved the problem by making the correct configuration available to Krill. The content of the RPKI repository was not affected. Delegated CAs that failed to publish during the outage, automatically resumed publication after the issue was resolved. We will improve our configuration to ensure that the configuration is always available before we attempt to start krill. Also we are looking into how we can get more monitoring coverage on the RFC8181 part of Publication as a Service.

Intermitted issues accessing Resource information in LIR PortalResolved Nov 3, 2026 · 55 minResolved

The applications using the database were impacted by failover of the load-balancer. We mitigated this short-term by clearing up the stale connections. We will work on the long-term mitigations: review of the connection pooling configuration and improve the connection usage monitoring. --- [2026-11-03T16:50:45.437+01:00] (resolved) This incident has been resolved. --- [2026-11-03T15:55:39.649+01: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 history90 days observed
Aug 12100.00% average · 37 days with incidentsNov 9

Going further back: RIPE NCC uptime by month and every recorded RIPE NCC outage.

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.78%. 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 it every 60 seconds.

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.78%. 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 it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

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

2660+ 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