Home ASN LookupAS219347

AS219347 Andi Anderson Vulczak

🇧🇷

Org handle: ORG-AA3460-RIPE

OCITOKEN::219347:39c54b387f7812babc1ed9bfe2a4d8182ae631280a63e528db14b80db1c0359f

RIPE NCCallocated

Announced Prefixes (BGP)

2total

1 IPv41 IPv6

IPv4 Addresses

Allocated (RIR)0

Announced (BGP)256

IPv6 Addresses

Allocated (RIR)1.2×10²⁴

Announced (BGP)1.2×10²⁴

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇧🇷 BR

RIR

RIPE NCC

Status

allocated

Allocated

2026-06-25

Routing hygiene

Score 20/100 · Low risk

RPKI ROA coverage

50%

no RPKI invalid prefixes

IRR route objects

100%

no origin mismatches

Hijack signals

0 announced against others' ROAs, 0 own announced by others

Upstreams

diversity 50/100

50% of announced prefixes (1 of 2) have no valid ROA

Based on 2 announced prefixes, updated daily (2026-10-25). How the score works · RPKI explained

Announced Prefixes

(BGP)2

Prefix	RPKI	IRR	Last Seen
44.30.224.0/24	No ROA	Other IRR	2026-10-27
2a06:9801:7d0::/48	Valid	RIPE	2026-10-27

Allocated Prefixes

(RIR)1

Prefix	Country	RIR	Status
2a06:9801:7d0::/48	🇧🇷 BR	RIPE	assigned

All 2 announced prefixes of AS219347 →

BGP Neighbours

(seen in AS paths)

Upstreams (2)

Networks AS219347 hands its own prefixes to: transit providers, or peers at an exchange.

AS199829Akronic Network Akronic Network LTDA1
AS209735LAGRANGE Cloud Technologies Limited1

ASPA

No ASPA

Abuse Contact

External Links

RIPE Whois RIPEstat

Learn more

What is an ASN?Autonomous systems, ASN ranges and how they are assigned
RPKI and route origin validationWhat the RPKI badges on the prefix list mean
ASPA explainedWhy AS219347 should publish an ASPA object
IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
ASN data in AI agents and SIEMMCP server and API integrations

API

Open

GEThttps://api.ipctl.io/v1/asn/219347

Returns ASN details, announced prefixes, and BGP routing data.

curl -s "https://api.ipctl.io/v1/asn/219347" | jq