RIPEstat

App · 20 actions

Look up any IP address, prefix or AS number with the RIPE NCC's public Internet data: who holds it and their abuse contact, WHOIS records, where it is registered and where it is used, how it is routed and how much of the Internet sees it, its RPKI status, its BGP neighbours and routes, its DNS names and whether it is on a spam blocklist. List a country's address space and networks, or search by name. Every action reads: nothing here changes anything. No account or API key required.

Actions

ActionWhat it does
Check blocklistsCheck whether an IP address is on the DNS blocklists RIPEstat asks (Spamhaus, Abusix, SpamRATS and SPFBL), for spam, malware or abuse.
Check RPKI validityCheck whether RPKI allows an AS number to announce a prefix: valid, invalid (wrong AS number or too specific) or unknown (no ROA), with the ROAs that decide it.
Check visibilityCheck how much of the Internet sees a prefix or AS number: how many of RIPE's full-table BGP peers see it, in IPv4 and IPv6, collector by collector, and which peers do not.
Count a country's ASNsCount the AS numbers registered to a country and how many of them are routed (seen announcing anything), now or at a past moment, optionally listing both groups.
Find abuse contactFind the email address to report abuse from an IP address, prefix or AS number to (spam, attacks, scanning), and the regional registry responsible for it.
Find where a resource is registeredFind the country an IP address, prefix or AS number is registered to, from the regional registries' own statistics, on any day since 2005.
GeolocateFind where an IP address or prefix is used: country, city and coordinates, from MaxMind's GeoLite2 data, with the share of a prefix at each location.
Get address space hierarchySee the RIPE Database address blocks around an address, prefix or range: the record matching it, the block directly above it (usually the provider's allocation) and the blocks directly below it (the assignments inside), each with its name, status, country and maintainers.
Get ASN overviewFind out who holds an AS number, whether it announces any prefixes, and which IANA block it comes from.
Get network for an IP addressFind the routed prefix an IP address belongs to and the AS number announcing it, from RIPE's BGP route collectors.
Get prefix overviewFind out whether a prefix is announced, which AS numbers announce it and who holds them, the prefixes related to it, and the IANA block it comes from.
Get routing statusGet how a prefix or AS number is routed: when it was first and last seen in BGP, how many of RIPE's BGP peers see it, the AS numbers originating a prefix and whether route objects back them, the prefixes around it, and for an AS number how much address space it announces.
List a country's resourcesList the AS numbers and the IPv4 and IPv6 address space registered to a country, from the regional registries' statistics, today or on a past day, with how many there are of each.
List ASN neighboursList the AS numbers seen next to an AS number in BGP paths (its upstreams, peers and customers), busiest first, with how many paths show each one.
List prefixes an ASN announcesList every IPv4 and IPv6 prefix an AS number announced in a time window (the last two weeks unless you set one), with when each was first and last seen.
List related prefixesList the routed prefixes that overlap an address, prefix or range (larger or smaller ones) or sit right next to it, with the AS number announcing each.
Look up BGP routesSee the live BGP routes RIPE's route collectors hold for a prefix (a looking glass): each peer's AS path, origin, next hop and communities, collector by collector, plus every origin AS number seen.
Look up DNSResolve a hostname to its IP addresses, following any aliases, or an IP address to its hostnames (reverse DNS), checking whether the hostname points back to the address as mail servers expect.
Look up WHOISRead the WHOIS records for an IP address, prefix or AS number from whichever regional registry holds it (RIPE NCC, ARIN, APNIC, LACNIC or AFRINIC), with the name, description, country, organisation, status and dates picked out, every line of each record, and matching route objects from routing registries.
Search RIPEstatFind AS numbers, prefixes, domains and related resources by a name or part of one, such as a company name or the start of an address.

Check blocklists

Check whether an IP address is on the DNS blocklists RIPEstat asks (Spamhaus, Abusix, SpamRATS and SPFBL), for spam, malware or abuse. The lookups take up to a minute or two; the step waits for them and says which blocklists did not answer. No API key required.

Inputs

IP addressip_addresstextRequired
An IPv4 or IPv6 address, such as 193.0.6.139.
Wait up to (seconds)wait_secondsnumber
How long to wait for every blocklist to answer. Blocklists still checking when the time is up are reported as pending.From 0 to 240. Default: 120.

Outputs

blocklist_countnumber
How many blocklists were checked.
blocklistslist
Every blocklist checked.
completetrue/false
True when every lookup finished before the step stopped waiting.
failed_countnumber
How many did not answer.
ip_addresstext
The IP address checked.
listedtrue/false
True when any blocklist lists the address.
listed_countnumber
How many list the address.
listed_onlist
The blocklists listing it, e.g. 'SPAMHAUS ZEN'.
not_listed_countnumber
How many answered that it is not listed.
noteslist
RIPEstat's own notes about the answer, such as an address it widened to its routed prefix or a time it moved to the nearest data it has.
pending_countnumber
How many were still checking.
Example output
{
  "blocklist_count": 2,
  "blocklists": [
    {
      "checked_at": "2026-10-21T05:52:38",
      "detail": null,
      "id": "abusix_black",
      "name": "Black",
      "operator": "Abusix",
      "status": "not_listed",
      "url": "https://lookup.abusix.com/"
    },
    {
      "checked_at": "2026-10-21T05:52:38",
      "detail": "The blocklist did not answer in time.",
      "id": "spamhaus_zen",
      "name": "ZEN",
      "operator": "SPAMHAUS",
      "status": "failed",
      "url": "https://www.spamhaus.org/zen/"
    }
  ],
  "complete": true,
  "failed_count": 1,
  "ip_address": "193.0.6.139",
  "listed": false,
  "listed_count": 0,
  "listed_on": [],
  "not_listed_count": 1,
  "notes": [
    "Results are complete"
  ],
  "pending_count": 0
}

Check RPKI validity

Check whether RPKI allows an AS number to announce a prefix: valid, invalid (wrong AS number or too specific) or unknown (no ROA), with the ROAs that decide it. Networks that check RPKI drop invalid announcements. No API key required.

Inputs

AS numberasntextRequired
The autonomous system number, as AS3333 or just 3333.
PrefixprefixtextRequired
The prefix announced, with its length, such as 193.0.0.0/21. The length matters: a ROA can allow 193.0.0.0/21 and not 193.0.0.0/24.

Outputs

asnnumber
The AS number checked.
meaningtext
The status in plain words.
noteslist
RIPEstat's own notes about the answer, such as an address it widened to its routed prefix or a time it moved to the nearest data it has.
prefixtext
The prefix checked.
roa_countnumber
How many ROAs cover the prefix.
roaslist
The ROAs (route origin authorisations) covering the prefix.
statustext
'valid', 'invalid_asn' (a ROA names another AS number), 'invalid_length' (the prefix is more specific than the ROA allows) or 'unknown' (no ROA covers it).
validtrue/false
True only when the status is 'valid'.
validatortext
The RPKI validator RIPEstat asked, e.g. 'routinator'.
Example output
{
  "asn": 3333,
  "meaning": "A ROA authorises this AS number to announce this prefix.",
  "notes": [],
  "prefix": "193.0.0.0/21",
  "roa_count": 1,
  "roas": [
    {
      "max_length": 21,
      "origin_asn": 3333,
      "prefix": "193.0.0.0/21",
      "validity": "valid"
    }
  ],
  "status": "valid",
  "valid": true,
  "validator": "routinator"
}

Check visibility

Check how much of the Internet sees a prefix or AS number: how many of RIPE's full-table BGP peers see it, in IPv4 and IPv6, collector by collector, and which peers do not. A drop is the first sign of an outage or a hijack. No API key required.

Inputs

Prefix, IP address or AS numberresourcetextRequired
A prefix (193.0.0.0/21), an AS number (AS3333) or an IP address, which is answered for the routed prefix it is in.
As ofas_ofdate and time
Look at the data as it was at this moment. Leave empty for the latest. Routing data is collected at 00:00, 08:00 and 16:00 UTC, so a time between those is moved to the one before.

Outputs

as_oftext
The moment the routing data describes (UTC).
collector_countnumber
How many route collectors reported.
collectorslist
Each route collector, with its peers' view.
ipv4_full_table_peersnumber
Full-table IPv4 peers in all.
ipv4_peers_seeingnumber
Full-table IPv4 peers that see it.
ipv4_percentnumber
The share of IPv4 peers that see it, in percent.
ipv6_full_table_peersnumber
Full-table IPv6 peers in all.
ipv6_peers_seeingnumber
Full-table IPv6 peers that see it.
ipv6_percentnumber
The share of IPv6 peers that see it, in percent.
noteslist
RIPEstat's own notes about the answer, such as an address it widened to its routed prefix or a time it moved to the nearest data it has.
peers_not_seeing_countnumber
How many full-table peers do not see it.
resourcetext
The prefix or AS number answered for.
Example output
{
  "as_of": "2026-10-21T00:00:00",
  "collector_count": 2,
  "collectors": [
    {
      "city": "Vienna",
      "collector": "RRC05",
      "country_code": "AT",
      "exchange": "VIX",
      "ipv4_full_table_peers": 10,
      "ipv4_peers_seeing": 10,
      "ipv6_full_table_peers": 0,
      "ipv6_peers_seeing": 0,
      "peers_not_seeing": []
    },
    {
      "city": "Montevideo",
      "collector": "RRC24",
      "country_code": "UY",
      "exchange": "LACNIC Multihop",
      "ipv4_full_table_peers": 11,
      "ipv4_peers_seeing": 10,
      "ipv6_full_table_peers": 0,
      "ipv6_peers_seeing": 0,
      "peers_not_seeing": [
        {
          "asn": 265721,
          "ip": "45.65.244.1",
          "ip_version": 4
        }
      ]
    }
  ],
  "ipv4_full_table_peers": 21,
  "ipv4_peers_seeing": 20,
  "ipv4_percent": 95.2,
  "ipv6_full_table_peers": 0,
  "ipv6_peers_seeing": 0,
  "ipv6_percent": null,
  "notes": [],
  "peers_not_seeing_count": 1,
  "resource": "1.1.1.0/24"
}

Count a country's ASNs

Count the AS numbers registered to a country and how many of them are routed (seen announcing anything), now or at a past moment, optionally listing both groups. No API key required.

Inputs

CountrycountrytextRequired
The country, by the registries' records (not by geolocation).One of: AF (Afghanistan (AF)), AX (Åland Islands (AX)), AL (Albania (AL)), DZ (Algeria (DZ)), AS (American Samoa (AS)), AD (Andorra (AD)), AO (Angola (AO)), AI (Anguilla (AI)), AQ (Antarctica (AQ)), AG (Antigua & Barbuda (AG)), and 240 more.
As ofas_ofdate and time
Look at the data as it was at this moment. Leave empty for the latest. Routing data is collected at 00:00, 08:00 and 16:00 UTC, so a time between those is moved to the one before.
List the AS numberslist_asnstrue/false
Turn on to return the routed and unrouted AS numbers as well as the counts.Default: false.

Outputs

as_oftext
The moment the data describes (UTC).
country_codetext
The country's two-letter code.
country_nametext
The country's name.
not_routed_asnslist
The AS numbers not routed, when 'List the AS numbers' is on.
not_routed_countnumber
How many are not.
noteslist
RIPEstat's own notes about the answer, such as an address it widened to its routed prefix or a time it moved to the nearest data it has.
registered_countnumber
AS numbers registered to the country.
routed_asnslist
The routed AS numbers, when 'List the AS numbers' is on.
routed_countnumber
How many of them are seen announcing routes.
Example output
{
  "as_of": "2026-10-18T00:00:00",
  "country_code": "IS",
  "country_name": "Iceland",
  "not_routed_asns": [
    21268,
    39418
  ],
  "not_routed_count": 13,
  "notes": [
    "Query time has been set to the latest time (2026-10-18 00:00 UTC) data is available for."
  ],
  "registered_count": 86,
  "routed_asns": [
    1850,
    6677
  ],
  "routed_count": 73
}

Find abuse contact

Find the email address to report abuse from an IP address, prefix or AS number to (spam, attacks, scanning), and the regional registry responsible for it. When none is on record the step still succeeds, with found set to false. No API key required.

Inputs

IP address, prefix or AS numberresourcetextRequired
What to look up: an IP address (193.0.6.139), a prefix (193.0.0.0/21) or an AS number (AS3333 or 3333).

Outputs

abuse_contacttext
The address to send abuse reports to, e.g. 'abuse@ripe.net'. Empty when none is on record.
abuse_contactslist
Every abuse address on record, usually one.
checked_attext
When RIPEstat looked the contact up (UTC).
foundtrue/false
True when an abuse contact is on record.
noteslist
RIPEstat's own notes about the answer, such as an address it widened to its routed prefix or a time it moved to the nearest data it has.
registrytext
The regional registry responsible for the resource, e.g. 'RIPE NCC' or 'ARIN'.
registry_codetext
The same registry as a short code, e.g. 'ripe'.
resourcetext
The IP address, prefix or AS number looked up.
Example output
{
  "abuse_contact": "abuse@ripe.net",
  "abuse_contacts": [
    "abuse@ripe.net"
  ],
  "checked_at": "2026-10-20T02:50:09",
  "found": true,
  "notes": [],
  "registry": "RIPE NCC",
  "registry_code": "ripe",
  "resource": "193.0.6.139"
}

Find where a resource is registered

Find the country an IP address, prefix or AS number is registered to, from the regional registries' own statistics, on any day since 2005. This is the holder's country on paper; use Geolocate for where the addresses are used. No API key required.

Inputs

IP address, prefix or AS numberresourcetextRequired
What to look up: an IP address (193.0.6.139), a prefix (193.0.0.0/21) or an AS number (AS3333 or 3333).
On datedatedate
Look at the registries' records on this day. Leave empty for the latest, usually two or three days old.

Outputs

as_oftext
The day of the statistics used.
country_codetext
The country it is registered to, e.g. 'NL'.
country_nametext
That country's name.
foundtrue/false
True when the registries' statistics name a country.
locationslist
Every matching entry, when the resource spans several.
matched_resourcetext
The registry entry that matched, which can be a larger block.
noteslist
RIPEstat's own notes about the answer, such as an address it widened to its routed prefix or a time it moved to the nearest data it has.
resourcetext
The IP address, prefix or AS number looked up.
Example output
{
  "as_of": "2026-10-18T00:00:00",
  "country_code": "NL",
  "country_name": "Netherlands",
  "found": true,
  "locations": [
    {
      "country_code": "NL",
      "country_name": "Netherlands",
      "resource": "193.0.0.0/20"
    }
  ],
  "matched_resource": "193.0.0.0/20",
  "notes": [
    "Result is based on an encompassing, larger prefix: 193.0.0.0/20"
  ],
  "resource": "193.0.6.139"
}

Geolocate

Find where an IP address or prefix is used: country, city and coordinates, from MaxMind's GeoLite2 data, with the share of a prefix at each location. Publishing the results outside your organisation falls under MaxMind's GeoLite2 licence. No API key required.

Inputs

IP address or prefixresourcetextRequired
An IP address (193.0.6.139) or a prefix (8.8.8.0/22).

Outputs

citytext
The city, when MaxMind knows it.
country_codetext
The two-letter country code, e.g. 'NL'.
country_nametext
The country's name, e.g. 'Netherlands'.
data_as_oftext
When MaxMind's data was published.
foundtrue/false
True when MaxMind knows where any of it is.
latitudenumber
Latitude of the location.
locationslist
Every location for the space, the largest share first. The fields above are the first of these.
longitudenumber
Longitude of the location.
noteslist
RIPEstat's own notes about the answer, such as an address it widened to its routed prefix or a time it moved to the nearest data it has.
resourcetext
The IP address or prefix located.
unknown_percentagenumber
How much of the space MaxMind has no location for, in percent.
Example output
{
  "city": null,
  "country_code": "NL",
  "country_name": "Netherlands",
  "data_as_of": "2026-10-16T20:30:46",
  "found": true,
  "latitude": 52.3824,
  "locations": [
    {
      "city": null,
      "country_code": "NL",
      "country_name": "Netherlands",
      "covered_percentage": 100.0,
      "latitude": 52.3824,
      "longitude": 4.8995,
      "prefixes": [
        "193.0.0.0/20"
      ]
    }
  ],
  "longitude": 4.8995,
  "notes": [],
  "resource": "193.0.6.139",
  "unknown_percentage": 0.0
}

Get address space hierarchy

See the RIPE Database address blocks around an address, prefix or range: the record matching it, the block directly above it (usually the provider's allocation) and the blocks directly below it (the assignments inside), each with its name, status, country and maintainers. Covers address space the RIPE NCC manages (Europe, the Middle East and Central Asia). No API key required.

Inputs

Prefix, IP address or rangeresourcetextRequired
A prefix (193.0.0.0/21), an IP address, or a range such as 193.0.0.0 - 193.0.7.255, the form WHOIS records use.

Outputs

as_oftext
When the lookup ran (UTC).
exactlist
The record matching it exactly.
exact_countnumber
How many exact matches came back.
less_specificlist
The block directly above it.
less_specific_countnumber
How many blocks above came back.
more_specificlist
The blocks directly below it.
more_specific_countnumber
How many blocks below came back.
noteslist
RIPEstat's own notes about the answer, such as an address it widened to its routed prefix or a time it moved to the nearest data it has.
registrytext
The registry the records come from (the RIPE NCC).
resourcetext
The address space answered for.
Example output
{
  "as_of": "2026-10-21T05:40:38",
  "exact": [
    {
      "country_code": "NL",
      "created": "2003-03-17T12:15:57Z",
      "description": "RIPE Network Coordination Centre, Amsterdam, Netherlands",
      "last_modified": "2026-03-19T09:08:35Z",
      "maintainers": [
        "RIPE-NCC-MNT"
      ],
      "name": "RIPE-NCC",
      "organisation": "ORG-RIEN1-RIPE",
      "prefixes": [
        "193.0.0.0/21"
      ],
      "range": "193.0.0.0 - 193.0.7.255",
      "source": "RIPE",
      "status": "ASSIGNED PA"
    }
  ],
  "exact_count": 1,
  "less_specific": [
    {
      "country_code": "NL",
      "created": "2012-03-09T15:03:38Z",
      "description": null,
      "last_modified": "2026-03-19T09:07:43Z",
      "maintainers": [
        "RIPE-NCC-HM-MNT",
        "RIPE-NCC-MNT"
      ],
      "name": "NL-RIPENCC-OPS-990305",
      "organisation": "ORG-RIEN1-RIPE",
      "prefixes": [
        "193.0.0.0/20",
        "193.0.16.0/21"
      ],
      "range": "193.0.0.0 - 193.0.23.255",
      "source": "RIPE",
      "status": "ALLOCATED PA"
    }
  ],
  "less_specific_count": 1,
  "more_specific": [],
  "more_specific_count": 0,
  "notes": [],
  "registry": "RIPE NCC",
  "resource": "193.0.0.0/21"
}

Get ASN overview

Find out who holds an AS number, whether it announces any prefixes, and which IANA block it comes from. An AS number nobody holds comes back with registered set to false. No API key required.

Inputs

AS numberasntextRequired
The autonomous system number, as AS3333 or just 3333.

Outputs

announcedtrue/false
True when it originates prefixes seen by at least 10 of RIPE's BGP peers. An AS number that only carries other networks' traffic reads false.
as_oftext
The moment the routing data describes (UTC).
asnnumber
The AS number looked up, e.g. 3333.
asn_labeltext
The same AS number written the usual way, e.g. 'AS3333'.
holdertext
Who holds the AS number, as its registry names them. Empty when nobody does.
iana_blockobject
The block IANA's registry files this resource under.
noteslist
RIPEstat's own notes about the answer, such as an address it widened to its routed prefix or a time it moved to the nearest data it has.
registeredtrue/false
True when a registry has assigned the AS number.
Example output
{
  "announced": true,
  "as_of": "2026-10-20T00:00:00",
  "asn": 3333,
  "asn_label": "AS3333",
  "holder": "RIPE-NCC-AS Reseaux IP Europeens Network Coordination Centre (RIPE NCC)",
  "iana_block": {
    "description": "Assigned by RIPE NCC",
    "registry": "IANA 16-bit Autonomous System (AS) Numbers Registry",
    "resource": "3154-3353"
  },
  "notes": [],
  "registered": true
}

Get network for an IP address

Find the routed prefix an IP address belongs to and the AS number announcing it, from RIPE's BGP route collectors. An address nobody routes (a private one, say) comes back with routed set to false. No API key required.

Inputs

IP addressip_addresstextRequired
An IPv4 or IPv6 address, such as 193.0.6.139.

Outputs

ip_addresstext
The IP address looked up.
noteslist
RIPEstat's own notes about the answer, such as an address it widened to its routed prefix or a time it moved to the nearest data it has.
origin_asnnumber
The AS number announcing that prefix, e.g. 3333. The first one when several announce it.
origin_asnslist
Every AS number announcing the prefix.
prefixtext
The routed prefix the address is in, e.g. '193.0.0.0/21'.
routedtrue/false
True when the address is inside a prefix announced on the Internet.
Example output
{
  "ip_address": "193.0.6.139",
  "notes": [],
  "origin_asn": 3333,
  "origin_asns": [
    3333
  ],
  "prefix": "193.0.0.0/21",
  "routed": true
}

Get prefix overview

Find out whether a prefix is announced, which AS numbers announce it and who holds them, the prefixes related to it, and the IANA block it comes from. An IP address, or a prefix not announced on its own, is answered for the announced prefix covering it. No API key required.

Inputs

Prefix or IP addressprefixtextRequired
A prefix such as 193.0.0.0/21, or an IP address to answer for the prefix covering it.
As ofas_ofdate and time
Look at the data as it was at this moment. Leave empty for the latest. Routing data is collected at 00:00, 08:00 and 16:00 UTC, so a time between those is moved to the one before.

Outputs

announcedtrue/false
True when the prefix is announced in BGP.
as_oftext
The moment the routing data describes (UTC).
holdertext
Who holds that AS number.
iana_blockobject
The block IANA's registry files this resource under.
is_less_specifictrue/false
True when the answer is for a larger prefix covering the one asked about.
low_visibility_left_outnumber
Routes left out because too few of RIPE's BGP peers see them.
noteslist
RIPEstat's own notes about the answer, such as an address it widened to its routed prefix or a time it moved to the nearest data it has.
origin_asnnumber
The AS number announcing it (the first one).
originslist
Every AS number announcing the prefix.
prefixtext
The prefix answered for. When an address, or a prefix that is not announced itself, was given, this is the announced prefix covering it.
related_prefix_countnumber
How many related prefixes there are in all, including any not listed.
related_prefixeslist
Announced prefixes inside or around this one.
requestedtext
The prefix or address that was asked about.
Example output
{
  "announced": true,
  "as_of": "2026-10-20T00:00:00",
  "holder": "RIPE-NCC-AS Reseaux IP Europeens Network Coordination Centre (RIPE NCC)",
  "iana_block": {
    "description": "RIPE NCC (Status: ALLOCATED)",
    "registry": "IANA IPv4 Address Space Registry",
    "resource": "193.0.0.0/8"
  },
  "is_less_specific": false,
  "low_visibility_left_out": 1,
  "notes": [
    "1 routes were filtered due to low visibility (min peers:10)."
  ],
  "origin_asn": 3333,
  "origins": [
    {
      "asn": 3333,
      "holder": "RIPE-NCC-AS Reseaux IP Europeens Network Coordination Centre (RIPE NCC)"
    }
  ],
  "prefix": "193.0.0.0/21",
  "related_prefix_count": 0,
  "related_prefixes": [],
  "requested": "193.0.0.0/21"
}

Get routing status

Get how a prefix or AS number is routed: when it was first and last seen in BGP, how many of RIPE's BGP peers see it, the AS numbers originating a prefix and whether route objects back them, the prefixes around it, and for an AS number how much address space it announces. No API key required.

Inputs

Prefix, IP address or AS numberresourcetextRequired
A prefix (193.0.0.0/21), an AS number (AS3333) or an IP address, which is answered for the routed prefix it is in.
As ofas_ofdate and time
Look at the data as it was at this moment. Leave empty for the latest. Routing data is collected at 00:00, 08:00 and 16:00 UTC, so a time between those is moved to the one before.
Seen by at leastmin_peers_seeingnumber
Leave out routes fewer than this many of RIPE's BGP peers see, which hides local and leaked announcements. RIPEstat uses 10 when empty; 0 keeps everything.From 0 to 1000. Default: 10.

Outputs

announced_ipv4_addressesnumber
For an AS number: how many IPv4 addresses those prefixes hold.
announced_ipv4_prefixesnumber
For an AS number: how many IPv4 prefixes it announces.
announced_ipv6_48snumber
For an AS number: its IPv6 space counted in /48 blocks.
announced_ipv6_prefixesnumber
For an AS number: how many IPv6 prefixes it announces.
as_oftext
The moment the routing data describes (UTC).
currently_seentrue/false
True when at least one RIPE BGP peer sees it now.
ever_seentrue/false
True when it has ever been seen in BGP.
first_seenobject
The first time RIPE's route collectors saw it.
ipv4_peers_seeingnumber
RIPE's full-table IPv4 BGP peers that see it.
ipv4_total_peersnumber
RIPE's full-table IPv4 BGP peers in all.
ipv6_peers_seeingnumber
RIPE's full-table IPv6 BGP peers that see it.
ipv6_total_peersnumber
RIPE's full-table IPv6 BGP peers in all.
last_seenobject
The last time they saw it.
less_specificslist
For a prefix: larger announced prefixes covering it (up to 50).
more_specificslist
For a prefix: smaller announced prefixes inside it (up to 50).
noteslist
RIPEstat's own notes about the answer, such as an address it widened to its routed prefix or a time it moved to the nearest data it has.
observed_neighboursnumber
For an AS number: how many neighbouring AS numbers are seen.
originslist
For a prefix: the AS numbers announcing exactly this prefix.
resourcetext
The prefix or AS number answered for. An address is widened to its routed prefix.
resource_typetext
'prefix' or 'asn'.
Example output
{
  "announced_ipv4_addresses": null,
  "announced_ipv4_prefixes": null,
  "announced_ipv6_48s": null,
  "announced_ipv6_prefixes": null,
  "as_of": "2026-10-19T16:00:00",
  "currently_seen": true,
  "ever_seen": true,
  "first_seen": {
    "origin_asn": 3333,
    "prefix": "193.0.0.0/21",
    "time": "2000-10-31T00:00:00"
  },
  "ipv4_peers_seeing": 326,
  "ipv4_total_peers": 326,
  "ipv6_peers_seeing": 0,
  "ipv6_total_peers": 0,
  "last_seen": {
    "origin_asn": 3333,
    "prefix": "193.0.0.0/21",
    "time": "2026-10-20T00:00:00"
  },
  "less_specifics": [],
  "more_specifics": [],
  "notes": [
    "Results exclude routes with very low visibility (less than 10 RIS full-feed peers seeing)."
  ],
  "observed_neighbours": null,
  "origins": [
    {
      "asn": 3333,
      "route_objects": [
        "RIPE"
      ]
    }
  ],
  "resource": "193.0.0.0/21",
  "resource_type": "prefix"
}

List a country's resources

List the AS numbers and the IPv4 and IPv6 address space registered to a country, from the regional registries' statistics, today or on a past day, with how many there are of each. No API key required.

Inputs

CountrycountrytextRequired
The country, by the registries' records (not by geolocation).One of: AF (Afghanistan (AF)), AX (Åland Islands (AX)), AL (Albania (AL)), DZ (Algeria (DZ)), AS (American Samoa (AS)), AD (Andorra (AD)), AO (Angola (AO)), AI (Anguilla (AI)), AQ (Antarctica (AQ)), AG (Antigua & Barbuda (AG)), and 240 more.
Resource typesresource_typeslist
Which lists to return. Leave everything unticked for all three. The counts always cover all three.One or more of: asn (AS numbers), ipv4 (IPv4 address space), ipv6 (IPv6 address space).
On datedatedate
Look at the records on this day. Leave empty for the latest.
IPv4 as prefixesipv4_as_prefixestrue/false
Turn on to write IPv4 space as prefixes (5.23.64.0/19) rather than ranges, splitting a range into prefixes where needed.Default: false.
How many of eachlimitnumber
The most entries to return in each list. A large country has tens of thousands.From 1 to 100000. Default: 1000.

Outputs

as_oftext
The day of the registries' statistics used.
asn_countnumber
How many AS numbers are registered to it.
asnslist
Its AS numbers, up to the limit.
country_codetext
The country's two-letter code.
country_nametext
The country's name.
ipv4list
Its IPv4 blocks, up to the limit, as ranges or prefixes.
ipv4_countnumber
How many IPv4 blocks are registered to it.
ipv6list
Its IPv6 blocks, up to the limit.
ipv6_countnumber
How many IPv6 blocks are registered to it.
noteslist
RIPEstat's own notes about the answer, such as an address it widened to its routed prefix or a time it moved to the nearest data it has.
truncatedtrue/false
True when a list was cut at the limit.
Example output
{
  "as_of": "2026-10-18",
  "asn_count": 86,
  "asns": [
    1850,
    6677
  ],
  "country_code": "IS",
  "country_name": "Iceland",
  "ipv4": [
    "5.23.64.0/19",
    "31.15.112.0/21"
  ],
  "ipv4_count": 174,
  "ipv6": [
    "2001:678:afc::/48",
    "2001:678:11a0::/48"
  ],
  "ipv6_count": 72,
  "notes": [],
  "truncated": true
}

List ASN neighbours

List the AS numbers seen next to an AS number in BGP paths (its upstreams, peers and customers), busiest first, with how many paths show each one. No API key required.

Inputs

AS numberasntextRequired
The autonomous system number, as AS3333 or just 3333.
Positionpositiontext
Keep only neighbours on one side of it in the paths. Leave empty for all of them.One of: left (Left: nearer the collectors, usually upstreams and peers), right (Right: further away, usually customers), uncertain (Uncertain: only seen next to a collector).
As ofas_ofdate and time
Look at the data as it was at this moment. Leave empty for the latest. Routing data is collected at 00:00, 08:00 and 16:00 UTC, so a time between those is moved to the one before.
How many to returnlimitnumber
The most neighbours to return, busiest first. A large network has thousands.From 1 to 5000. Default: 100.

Outputs

as_oftext
The moment the routing data describes (UTC).
asnnumber
The AS number looked up.
countnumber
How many neighbours came back.
left_countnumber
How many left neighbours RIPEstat counts in all.
more_availabletrue/false
True when raising the limit would return more.
neighbourslist
The neighbours, busiest first.
noteslist
RIPEstat's own notes about the answer, such as an address it widened to its routed prefix or a time it moved to the nearest data it has.
right_countnumber
How many right neighbours it counts in all.
total_matchingnumber
How many matched before the limit was applied.
uncertain_countnumber
How many uncertain neighbours it counts in all.
unique_countnumber
How many different neighbours it counts in all.
Example output
{
  "as_of": "2026-10-20T00:00:00",
  "asn": 3333,
  "count": 2,
  "left_count": 47,
  "more_available": true,
  "neighbours": [
    {
      "asn": 6939,
      "ipv4_routes": 61679,
      "ipv6_routes": 69438,
      "path_count": 26590,
      "position": "left"
    },
    {
      "asn": 3320,
      "ipv4_routes": 134910,
      "ipv6_routes": 6467,
      "path_count": 18310,
      "position": "left"
    }
  ],
  "notes": [
    "Query time has been set to the latest available time (2026-10-20 00:00 UTC)"
  ],
  "right_count": 1,
  "total_matching": 47,
  "uncertain_count": 864,
  "unique_count": 912
}

List prefixes an ASN announces

List every IPv4 and IPv6 prefix an AS number announced in a time window (the last two weeks unless you set one), with when each was first and last seen. Run on a schedule, it shows when a network starts or stops announcing address space. No API key required.

Inputs

AS numberasntextRequired
The autonomous system number, as AS3333 or just 3333.
Fromstart_timedate and time
The start of the window. Leave empty for two weeks ago.
Toend_timedate and time
The end of the window. Leave empty for now.
Seen by at leastmin_peers_seeingnumber
Leave out routes fewer than this many of RIPE's BGP peers see, which hides local and leaked announcements. RIPEstat uses 10 when empty; 0 keeps everything.From 0 to 1000. Default: 10.

Outputs

asnnumber
The AS number looked up.
countnumber
How many prefixes came back.
ipv4_countnumber
How many of them are IPv4.
ipv6_countnumber
How many of them are IPv6.
noteslist
RIPEstat's own notes about the answer, such as an address it widened to its routed prefix or a time it moved to the nearest data it has.
period_endtext
The end of the window searched (UTC).
period_starttext
The start of the window searched (UTC).
prefixeslist
Every prefix announced in the window, IPv4 first, in address order.
Example output
{
  "asn": 3333,
  "count": 2,
  "ipv4_count": 1,
  "ipv6_count": 1,
  "notes": [
    "Results exclude routes with very low visibility (less than 10 RIS full-feed peers seeing)."
  ],
  "period_end": "2026-10-10T12:00:00",
  "period_start": "2026-10-01T00:00:00",
  "prefixes": [
    {
      "first_seen": "2026-10-01T00:00:00",
      "ip_version": 4,
      "last_seen": "2026-10-10T08:00:00",
      "periods": [
        {
          "end": "2026-10-10T08:00:00",
          "start": "2026-10-01T00:00:00"
        }
      ],
      "prefix": "193.0.0.0/21"
    },
    {
      "first_seen": "2026-10-01T00:00:00",
      "ip_version": 6,
      "last_seen": "2026-10-10T08:00:00",
      "periods": [
        {
          "end": "2026-10-10T08:00:00",
          "start": "2026-10-01T00:00:00"
        }
      ],
      "prefix": "2001:67c:2e8::/48"
    }
  ]
}

List the routed prefixes that overlap an address, prefix or range (larger or smaller ones) or sit right next to it, with the AS number announcing each. No API key required.

Inputs

Prefix, IP address or rangeresourcetextRequired
A prefix (193.0.0.0/21), an IP address, or a range such as 193.0.0.0 - 193.0.7.255, the form WHOIS records use.

Outputs

as_oftext
When the lookup ran (UTC).
countnumber
How many related prefixes came back.
noteslist
RIPEstat's own notes about the answer, such as an address it widened to its routed prefix or a time it moved to the nearest data it has.
prefixeslist
The routed prefixes that overlap it or sit right next to it.
resourcetext
The prefix answered for.
Example output
{
  "as_of": "2026-10-21T05:52:00",
  "count": 2,
  "notes": [],
  "prefixes": [
    {
      "origin_asn": 54290,
      "origin_name": "HOSTWINDS - Hostwinds LLC., US",
      "prefix": "192.255.128.0/17",
      "relationship": "Adjacency - Left"
    },
    {
      "origin_asn": 197000,
      "origin_name": "RIPE-NCC-AUTHDNS-AS Reseaux IP Europeens Network Coordination Centre (RIPE NCC), NL",
      "prefix": "193.0.8.0/23",
      "relationship": "Adjacency - Right"
    }
  ],
  "resource": "193.0.0.0/21"
}

Look up BGP routes

See the live BGP routes RIPE's route collectors hold for a prefix (a looking glass): each peer's AS path, origin, next hop and communities, collector by collector, plus every origin AS number seen. Near real time. No API key required.

Inputs

Prefix or IP addressresourcetextRequired
A prefix exactly as it is announced (193.0.0.0/21), or an IP address to look up the prefix covering it.
Confirmed within (hours)max_age_hoursnumber
Only show routes confirmed in this many hours. 24 when empty.From 1 to 168. Default: 24.

Outputs

as_oftext
How recent the routing data is (UTC).
collector_countnumber
How many route collectors hold a route.
collectorslist
Each route collector and the routes its peers send it.
foundtrue/false
True when any collector holds a route.
noteslist
RIPEstat's own notes about the answer, such as an address it widened to its routed prefix or a time it moved to the nearest data it has.
origin_asnslist
Every AS number originating them.
prefixeslist
The prefixes the routes are for.
requestedtext
The prefix or address asked about.
resourcetext
The prefix answered for.
route_countnumber
How many routes there are in all.
unique_path_countnumber
How many different AS paths there are.
Example output
{
  "as_of": "2026-10-21T05:52:43",
  "collector_count": 1,
  "collectors": [
    {
      "collector": "RRC01",
      "exchange": "LINX / LONAP",
      "location": "London, GB",
      "route_count": 2,
      "routes": [
        {
          "as_path": [
            15692,
            174,
            1273,
            3333
          ],
          "as_path_text": "15692 174 1273 3333",
          "bgp_origin": "IGP",
          "communities": [
            "174:21100",
            "174:22012"
          ],
          "last_confirmed": "2026-10-21T05:52:45",
          "last_updated": "2026-10-08T22:38:44",
          "next_hop": "5.57.80.113",
          "origin_asn": 3333,
          "peer": "5.57.80.113",
          "peer_asn": 15692,
          "prefix": "193.0.0.0/21"
        },
        {
          "as_path": [
            8218,
            3333
          ],
          "as_path_text": "8218 3333",
          "bgp_origin": "IGP",
          "communities": [
            "8218:102",
            "8218:20000"
          ],
          "last_confirmed": "2026-10-21T05:52:46",
          "last_updated": "2026-09-01T20:43:50",
          "next_hop": "5.57.80.210",
          "origin_asn": 3333,
          "peer": "5.57.80.210",
          "peer_asn": 8218,
          "prefix": "193.0.0.0/21"
        }
      ]
    }
  ],
  "found": true,
  "notes": [],
  "origin_asns": [
    3333
  ],
  "prefixes": [
    "193.0.0.0/21"
  ],
  "requested": "193.0.0.0/21",
  "resource": "193.0.0.0/21",
  "route_count": 2,
  "unique_path_count": 2
}

Look up DNS

Resolve a hostname to its IP addresses, following any aliases, or an IP address to its hostnames (reverse DNS), checking whether the hostname points back to the address as mail servers expect. No API key required.

Inputs

Hostname or IP addressnametextRequired
A hostname such as www.ripe.net (a pasted link works too), or an IP address for its hostnames.

Outputs

addresseslist
For a hostname: every address it resolves to.
aliaseslist
For a hostname: the aliases (CNAMEs) followed on the way.
checked_attext
When the lookup ran (UTC).
forward_confirmedtrue/false
For an address: true when its hostname resolves back to it, which mail servers check. Empty for a hostname.
forward_recordslist
Every forward record seen (A, AAAA and CNAME).
hostnameslist
For an address: its hostnames (PTR records).
ipv4_addresseslist
The IPv4 ones among them.
ipv6_addresseslist
The IPv6 ones among them.
nameserverslist
The authoritative nameservers that answered.
noteslist
RIPEstat's own notes about the answer, such as an address it widened to its routed prefix or a time it moved to the nearest data it has.
querytext
The hostname or IP address looked up.
query_typetext
'hostname' or 'ip'.
resolvedtrue/false
For a hostname: true when it resolves to an address. For an address: true when it has a hostname.
reverse_recordslist
Every reverse record seen (PTR).
Example output
{
  "addresses": [],
  "aliases": [],
  "checked_at": "2026-10-20T03:05:00",
  "forward_confirmed": false,
  "forward_records": [
    {
      "name": "www.ripe.net",
      "points_to": [
        "www.ripe.net.edgekey.net"
      ]
    },
    {
      "name": "www.ripe.net.edgekey.net",
      "points_to": [
        "e337066.dscb.akamaiedge.net"
      ]
    },
    {
      "name": "e337066.dscb.akamaiedge.net",
      "points_to": [
        "2.19.195.59",
        "2a02:26f0:1180:35::210:6ad4"
      ]
    }
  ],
  "hostnames": [
    "www.ripe.net"
  ],
  "ipv4_addresses": [],
  "ipv6_addresses": [],
  "nameservers": [
    "manus.authdns.ripe.net",
    "ns3.afrinic.net"
  ],
  "notes": [],
  "query": "193.0.6.139",
  "query_type": "ip",
  "resolved": true,
  "reverse_records": [
    {
      "address": "193.0.6.139",
      "hostnames": [
        "www.ripe.net"
      ]
    }
  ]
}

Look up WHOIS

Read the WHOIS records for an IP address, prefix or AS number from whichever regional registry holds it (RIPE NCC, ARIN, APNIC, LACNIC or AFRINIC), with the name, description, country, organisation, status and dates picked out, every line of each record, and matching route objects from routing registries. No API key required.

Inputs

IP address, prefix or AS numberresourcetextRequired
What to look up: an IP address (193.0.6.139), a prefix (193.0.0.0/21) or an AS number (AS3333 or 3333).

Outputs

as_oftext
When the lookup ran (UTC).
noteslist
RIPEstat's own notes about the answer, such as an address it widened to its routed prefix or a time it moved to the nearest data it has.
record_countnumber
How many registry records came back.
recordslist
The registry's records for the resource.
registrieslist
The registries consulted, e.g. 'ripe' or 'arin'.
resourcetext
The IP address, prefix or AS number looked up.
routing_record_countnumber
How many routing registry objects came back.
routing_recordslist
Matching objects from routing registries (RIPE, RADB...), such as route objects.
Example output
{
  "as_of": "2026-10-20T03:00:00",
  "notes": [
    "IP address has been converted to a prefix"
  ],
  "record_count": 1,
  "records": [
    {
      "attributes": [
        {
          "key": "inetnum",
          "link": "https://stat.ripe.net/193.0.0.0/21",
          "value": "193.0.0.0/21"
        },
        {
          "key": "netname",
          "link": null,
          "value": "RIPE-NCC"
        },
        {
          "key": "country",
          "link": null,
          "value": "NL"
        }
      ],
      "country": "NL",
      "created": "2003-03-17T12:15:57Z",
      "description": "RIPE Network Coordination Centre; Amsterdam, Netherlands",
      "key": "193.0.0.0/21",
      "last_modified": "2026-03-19T09:08:35Z",
      "name": "RIPE-NCC",
      "organisation": "ORG-RIEN1-RIPE",
      "source": "RIPE",
      "status": "ASSIGNED PA",
      "type": "inetnum"
    }
  ],
  "registries": [
    "ripe"
  ],
  "resource": "193.0.6.139",
  "routing_record_count": 1,
  "routing_records": [
    {
      "attributes": [
        {
          "key": "route",
          "link": "https://stat.ripe.net/193.0.0.0/21",
          "value": "193.0.0.0/21"
        },
        {
          "key": "origin",
          "link": "https://stat.ripe.net/AS3333",
          "value": "3333"
        }
      ],
      "country": null,
      "created": "1970-01-01T00:00:00Z",
      "description": "RIPE-NCC",
      "key": "193.0.0.0/21",
      "last_modified": "2008-09-10T14:27:53Z",
      "name": null,
      "organisation": null,
      "source": "RIPE",
      "status": null,
      "type": "route"
    }
  ]
}

Search RIPEstat

Find AS numbers, prefixes, domains and related resources by a name or part of one, such as a company name or the start of an address. Each result's value can go straight into another RIPEstat step. No API key required.

Inputs

Search forquerytextRequired
A name (Cloudflare), a domain (ripe.net), an AS number or the start of an address.
How many per categorylimitnumber
The most results to return in each category.From 1 to 50. Default: 10.

Outputs

categorieslist
The categories with results.
countnumber
How many results came back.
noteslist
RIPEstat's own notes about the answer, such as an address it widened to its routed prefix or a time it moved to the nearest data it has.
querytext
The text searched for.
resultslist
What matched, grouped by category.
Example output
{
  "categories": [
    "ASNs",
    "Domains"
  ],
  "count": 2,
  "notes": [],
  "query": "cloudflare",
  "results": [
    {
      "category": "ASNs",
      "description": "CLOUDFLARENET - Cloudflare, Inc.",
      "label": "AS13335",
      "value": "AS13335"
    },
    {
      "category": "Domains",
      "description": "cloudflare.com ranks #220 on Alexa.com",
      "label": "cloudflare.com",
      "value": "cloudflare.com"
    }
  ]
}

On this page