RIPEstat integration
RIPEstat data, in your warehouse.
A built-in ingestr connector: add credentials, pick tables, schedule it.
name: raw.table
type: ingestr
parameters:
source_connection: ripestat
source_table: '<table>'
destination: snowflake
incremental_strategy: merge$ bruin run assets/raw/ripestat.asset.yml
- extract · RIPEstat dataincremental
- load · snowflake raw.datamerged
- checks · not_null, unique
Loaded and checked. Downstream models can run.
How it connects
Connected in three steps.
RIPEstat provides Internet routing, registration, geography, DNS, and RPKI data from the RIPE NCC. Its Data API is public and does not require authentication.
- 01
Add a RIPEstat connection with its credentials.
- 02
Pick the tables to load and how: replace, append or merge.
- 03
Bruin runs it on your schedule and checks every load.
The platform
Part of the Bruin platform.
Data in, ready for everything downstream: the models, the checks, the lineage and the AI layer.
01 · Move
02 · Model & govern
03 · Use
Security & identity
More tools, same category.
Frequently asked
Questions about RIPEstat.
Does Bruin have a built-in RIPEstat integration?
Yes. Built-in ingestr source.
Where can RIPEstat data go?
Snowflake, BigQuery, Databricks, Redshift, ClickHouse, Postgres, DuckDB, MotherDuck, Microsoft Fabric and more, plus files on S3 and GCS.
How fresh is the data?
As fresh as your schedule. Incremental loads append, merge or replace a time window, every few minutes if you like.
Do we need Bruin Cloud?
No. The Bruin CLI and ingestr run locally, in CI or in your own orchestrator. Bruin Cloud adds scheduling, lineage, alerts and the AI data analyst on top.
Ready to connect RIPEstat?
$100 in credits and 50 AI tasks. No credit card.
A demo walks through your own data.