CARVIEW |
Select Language
HTTP/2 302
date: Sun, 13 Jul 2025 07:40:34 GMT
content-type: text/html; charset=utf-8
content-length: 0
location: https://status.ripe.net
x-frame-options: DENY
vary: origin, Cookie
x-content-type-options: nosniff
referrer-policy: same-origin
cross-origin-opener-policy: same-origin
strict-transport-security: max-age=31536000
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=7lAoZ5pMrllhDNDNOipYMMVrXop_8Mq9nzz8oLc2Yvw-1752392434-1.0.1.1-w_AOhZQ3WbrOPYFuNYo1gRA3i4ID48lAZZB6rnKXh.sBFEveES1Yb95JSadyh63h2A3yqRxZ8WUihcgkBoh24jgeify9vFHaNx_n9_jSdNc; path=/; expires=Sun, 13-Jul-25 08:10:34 GMT; domain=.ripe.net; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 95e7220bde382ffb-BLR
alt-svc: h3=":443"; ma=86400
HTTP/2 103
link: ; as=script; nopush; rel=preload, ; as=script; nopush; rel=preload, ; as=style; nopush; rel=preload, ; as=style; nopush; rel=preload, ; as=style; nopush; rel=preload, ; as=script; nopush; rel=preload, ; as=script; nopush; rel=preload, ; as=script; nopush; rel=preload, ; as=script; nopush; rel=preload, ; as=script; nopush; rel=preload, ; as=script; nopush; rel=preload
HTTP/2 200
date: Sun, 13 Jul 2025 07:40:35 GMT
content-type: text/html; charset=utf-8
x-download-options: noopen
x-permitted-cross-domain-policies: none
referrer-policy: strict-origin-when-cross-origin
x-statuspage-version: 24535eb0746632ffb8b6c151f2813f0d71a6db02
vary: Accept,Accept-Encoding,X-Forwarded-Host,X-Forwarded-Scheme,X-Forwarded-Proto,Fastly-SSL
x-statuspage-skip-logging: true
access-control-allow-origin: *
x-edge-cache-ttl: 3
cache-control: max-age=3, public
link: ; rel=preload; as=script; nopush,; rel=preload; as=script; nopush,; rel=preload; as=style; nopush,; rel=preload; as=style; nopush,; rel=preload; as=style; nopush,; rel=preload; as=script; nopush,; rel=preload; as=script; nopush,; rel=preload; as=script; nopush,; rel=preload; as=script; nopush,; rel=preload; as=script; nopush,; rel=preload; as=script; nopush
x-pollinator-metadata-service: status-page-web-pages
x-runtime: 0.122805
x-cache: MISS
x-content-type-options: nosniff
x-xss-protection: 1; mode=block
atl-traceid: 70d2b0d00b384f2ba79a38751a23d1b8
atl-request-id: 70d2b0d0-0b38-4f2b-a79a-38751a23d1b8
report-to: {"endpoints": [{"url": "https://dz8aopenkvv6s.cloudfront.net"}], "group": "endpoint-1", "include_subdomains": true, "max_age": 600}
nel: {"failure_fraction": 0.001, "include_subdomains": true, "max_age": 600, "report_to": "endpoint-1"}
strict-transport-security: max-age=63072000; preload
server-timing: atl-edge;dur=141,atl-edge-internal;dur=4,atl-edge-upstream;dur=139,atl-edge-pop;desc="aws-us-west-2"
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 95e7220db9b1c1ba-BLR
content-encoding: gzip
alt-svc: h3=":443"; ma=86400
RIPE NCC Status
Get email notifications whenever RIPE NCC creates, updates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you acknowledge our Privacy Policy. In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Get webhook notifications whenever RIPE NCC creates an incident, updates an incident, resolves an incident or changes a component status.
Visit our support site.
All Systems Operational
Uptime over the past 90 days. View historical uptime.
RIPE Database
Operational
90 days ago
99.94
% uptime
Today
Email to/from the RIPE NCC
Operational
90 days ago
100.0
% uptime
Today
K-root/DNS
?
Operational
90 days ago
100.0
% uptime
Today
LIR (Member) Portal
Operational
90 days ago
99.94
% uptime
Today
RIPE NCC Access
Operational
90 days ago
99.94
% uptime
Today
RPKI
Operational
90 days ago
99.91
% uptime
Today
RPKI Dashboard
Operational
90 days ago
99.89
% uptime
Today
RRDP Repository
Operational
90 days ago
100.0
% uptime
Today
rsync Repository
Operational
90 days ago
99.94
% uptime
Today
Publication as a Service (API endpoints)
?
Operational
90 days ago
99.83
% uptime
Today
www.ripe.net
Operational
90 days ago
100.0
% uptime
Today
Reverse DNS
Operational
90 days ago
100.0
% uptime
Today
Non-Critical Services
Operational
90 days ago
99.95
% uptime
Today
Billing & Payments
Operational
RIPEstat
Operational
DNSMON
Operational
Mailing Lists
Operational
RIPE NCC Academy
Operational
RIPE NCC Certified Professionals
Operational
RIPE Atlas
Operational
RIPE Labs
Operational
RIS (Routing Information Service)
Operational
Meeting Software
Operational
Pilot (RPKI)
?
Operational
90 days ago
99.95
% uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
Past Incidents
Jul 13, 2025
No incidents reported today.
Jul 12, 2025
No incidents reported.
Jul 11, 2025
No incidents reported.
Jul 10, 2025
No incidents reported.
Jul 9, 2025
Completed -
The maintenance window is closed.
Jul 9, 18:37 CEST
Jul 9, 18:37 CEST
Update -
The maintenance cannot be completed due to an issue with the virtual environment where the RIS collector will be hosted.
No downtime affected the RIS service.
The same task will be rescheduled on a new date.
Jul 9, 15:45 CEST
No downtime affected the RIS service.
The same task will be rescheduled on a new date.
Jul 9, 15:45 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 9, 10:00 CEST
Jul 9, 10:00 CEST
Scheduled -
We will be reinstalling rrc18.ripe.net, currently hosted on a metal server at CATNIX, Barcelona.
The server will be installed in a Virtual Machine provided by CATNIX.
During the maintenance window:
BGP sessions will be down
MRT file will not be produced.
Jul 7, 12:49 CEST
The server will be installed in a Virtual Machine provided by CATNIX.
During the maintenance window:
BGP sessions will be down
MRT file will not be produced.
Jul 7, 12:49 CEST
Completed -
The scheduled maintenance has been completed.
Jul 9, 08:14 CEST
Jul 9, 08:14 CEST
Verifying -
Verification is currently underway for the maintenance items.
Jul 9, 08:11 CEST
Jul 9, 08:11 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 9, 08:00 CEST
Jul 9, 08:00 CEST
Scheduled -
We plan to perform a switchover of the RIPE database primary instance, so we can perform patching on the server. We don't expect any downtime for Whois queries or updates.
Jul 2, 11:08 CEST
Jul 2, 11:08 CEST
Jul 8, 2025
Completed -
The scheduled maintenance has been completed.
Jul 8, 12:00 CEST
Jul 8, 12:00 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 8, 11:00 CEST
Jul 8, 11:00 CEST
Update -
We will be undergoing scheduled maintenance during this time.
Jul 8, 10:55 CEST
Jul 8, 10:55 CEST
Scheduled -
We will carry out planned maintenance on the mailing lists. During this time, the mailing lists will be unavailable or not fully functional.
Jul 8, 10:54 CEST
Jul 8, 10:54 CEST
Completed -
The scheduled maintenance has been completed.
Jul 8, 11:15 CEST
Jul 8, 11:15 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 8, 11:01 CEST
Jul 8, 11:01 CEST
Scheduled -
We will be switching RIPE NCC Access to a new CDN provider during the maintenance window. No action is required on your part, and you should not experience any service interruption.
Jul 7, 10:34 CEST
Jul 7, 10:34 CEST
Jul 7, 2025
Completed -
The scheduled maintenance has been completed.
Jul 7, 18:54 CEST
Jul 7, 18:54 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 7, 18:00 CEST
Jul 7, 18:00 CEST
Update -
We will be undergoing scheduled maintenance during this time.
Jul 7, 11:28 CEST
Jul 7, 11:28 CEST
Scheduled -
We will do scheduled maintenance during this time.
Jun 2, 15:40 CEST
Jun 2, 15:40 CEST
Jul 6, 2025
No incidents reported.
Jul 5, 2025
No incidents reported.
Jul 4, 2025
Resolved -
We are resolving this statuspage issue, since the impact has been mitigated for now. The underlying cause has not been fully resolved.
After analysis we conclude that the python web application can get overloaded after requests to a backend system stall. RIPEstat is a python application based on Django. This means there is a limited number of worker threads available, and these get overloaded. There is no asynchronous client for the RPC system (Thrift) used by the backend API, so we can not handle multiple requests per thread..
We have:
* Added automatic rolling restarts of the thrift backend system as a stopgap measure
In the short term we will:
* Add metrics based on the nginx and python application logs
In the medium term we will:
* Scrape metrics natively from the python app (a prometheus endpoint is present but can not be scraped due to infrastructure limitations in our setup)
* Start scraping metrics from _each_ Thrift RPC server instance (instead of scraping a single instance through a webserver)
* Add standard JVM metrics, as well as statistics on thrift calls in the Thrift RPC server
Jul 4, 22:45 CEST
After analysis we conclude that the python web application can get overloaded after requests to a backend system stall. RIPEstat is a python application based on Django. This means there is a limited number of worker threads available, and these get overloaded. There is no asynchronous client for the RPC system (Thrift) used by the backend API, so we can not handle multiple requests per thread..
We have:
* Added automatic rolling restarts of the thrift backend system as a stopgap measure
In the short term we will:
* Add metrics based on the nginx and python application logs
In the medium term we will:
* Scrape metrics natively from the python app (a prometheus endpoint is present but can not be scraped due to infrastructure limitations in our setup)
* Start scraping metrics from _each_ Thrift RPC server instance (instead of scraping a single instance through a webserver)
* Add standard JVM metrics, as well as statistics on thrift calls in the Thrift RPC server
Jul 4, 22:45 CEST
Update -
We have more information, and expect to roll out additional metrics by the weekend. This will likely give us more visibility into the underlying cause.
Jul 4, 08:58 CEST
Jul 4, 08:58 CEST
Identified -
In addition, this root cause led to a near-full outage for RIPEstat between 0:38 and 1:29. We apologize for this inconvenience and are working on the monitoring gaps that are present for partial failures.
Jul 3, 11:56 CEST
Jul 3, 11:56 CEST
Investigating -
We intermittently have periods with an increased error rate affecting RIPEstat. This occurs for a fraction of requests when it happens.
Users may encounter errors when accessing RIPEstat on the web or making API calls. Data may fail to load in widgets, and API responses may return an HTTP error.
The underlying cause is intermittent issues with one of our (internal) backend APIs. This backend system degrades in performance, but not enough to raise alerts. In turn, this degrades the performance of RIPEstat. We currently have limited metrics for the performance of this system. This means there is user impact before the issue is visible in our current monitoring solution.
We are actively implementing enhanced monitoring to improve visibility into error rates for both the main RIPEstat application and the specific backend system. This will help us better identify and resolve issues in the future.
You may need to reload the page if you encounter an error, or retry failed API calls. We will update this notification as soon as we have more information.
Jul 3, 08:23 CEST
Users may encounter errors when accessing RIPEstat on the web or making API calls. Data may fail to load in widgets, and API responses may return an HTTP error.
The underlying cause is intermittent issues with one of our (internal) backend APIs. This backend system degrades in performance, but not enough to raise alerts. In turn, this degrades the performance of RIPEstat. We currently have limited metrics for the performance of this system. This means there is user impact before the issue is visible in our current monitoring solution.
We are actively implementing enhanced monitoring to improve visibility into error rates for both the main RIPEstat application and the specific backend system. This will help us better identify and resolve issues in the future.
You may need to reload the page if you encounter an error, or retry failed API calls. We will update this notification as soon as we have more information.
Jul 3, 08:23 CEST
Jul 3, 2025
Resolved -
Issue with connectivity is resolved. We will follow up later with a post-mortem.
Jul 3, 17:58 CEST
Jul 3, 17:58 CEST
Monitoring -
The situation has recovered. We will follow up later with a post-mortem.
Jul 3, 15:56 CEST
Jul 3, 15:56 CEST
Identified -
We found the issue and connectivity has recovered.
Jul 3, 15:55 CEST
Jul 3, 15:55 CEST
Update -
The engineering team is continuing their investigation.
Jul 3, 15:48 CEST
Jul 3, 15:48 CEST
Update -
We are continuing to investigate this issue.
Jul 3, 14:32 CEST
Jul 3, 14:32 CEST
Update -
We are continuing to investigate this issue.
Jul 3, 14:18 CEST
Jul 3, 14:18 CEST
Investigating -
We are currently investigating this issue.
Jul 3, 14:16 CEST
Jul 3, 14:16 CEST
Resolved -
There have been no further issues with probes connecting to the controllers. Fixes have been put in place to make the system more resilient in the future.
Jul 3, 11:38 CEST
Jul 3, 11:38 CEST
Monitoring -
Almost all probes have reconnected and the system is operating normally. We are continuing to monitor for any remaining issues.
Jun 30, 15:05 CEST
Jun 30, 15:05 CEST
Identified -
Over the weekend some RIPE Atlas probes began to disconnect from the system, causing a lot of instability. Many of the hardware probes are still unable to connect, but the issue has been identified and all remaining probes should start to connect.
Jun 30, 09:31 CEST
Jun 30, 09:31 CEST
Jul 2, 2025
No incidents reported.
Jul 1, 2025
Completed -
The scheduled maintenance has been completed.
Jul 1, 17:45 CEST
Jul 1, 17:45 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 1, 17:00 CEST
Jul 1, 17:00 CEST
Scheduled -
We will carry out planned maintenance on the ripe.net website and RIPE Labs. During this time, www.ripe.net and labs.ripe.net will be unavailable or not fully functional.
Jul 1, 11:46 CEST
Jul 1, 11:46 CEST
Jun 30, 2025
Jun 29, 2025
No incidents reported.