asn.dev

Routing security

AS275626 BOLHANET telecomunicacoes

Unclassified LACNIC

RPKI valid 0% 0 of 7 announcements
RPKI invalid 0 none
No ROA 7 not covered by any ROA
IRR registered 0% 7 missing · 0 other origin
ROAs 0 authorising this AS

Announcements

What this network originates

7 observed

Every prefix observed with AS275626 as its origin, checked against RPKI and the IRR. Problems sort first.

PrefixRPKIIRRVantage points
2804:977c::/32No ROANo IRR31
2804:977c::/33No ROANo IRR31
2804:977c::/34No ROANo IRR31
2804:977c:4000::/34No ROANo IRR31
2804:977c:8000::/33No ROANo IRR31
2804:977c:8000::/34No ROANo IRR31
2804:977c:c000::/34No ROANo IRR31

RPKI · ROAs

Route origin authorisations

0 ROAs

Signed statements by address holders that AS275626 may originate these prefixes, up to the maximum length shown.

No ROA names this AS as an authorised origin.

ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.

RPKI · ASPA

Declared transit providers

No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.

IRR

Registered route objects

0 objects · 0 not announced

Route objects naming AS275626 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.

No route objects name this AS as origin.

IRR

AS-sets

The as-set is what upstreams expand to build this network's customer filter. Sets that list AS275626 directly show who expects to carry it.

AS-setWhereRelationship
AS-ALTAREDERADBLists AS275626 as a direct member
AS-CTBC-TOOLS-11RADBLists AS275626 as a direct member
AS-DURAND1-CUSTOMERRADBLists AS275626 as a direct member
AS-FORTEL-CUSTOMERSRADBLists AS275626 as a direct member
AS264409:AS-CONERADBLists AS275626 as a direct member

RPKI from rpki-client, validated 2026-10-21 12:00 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-21. Cross-check on bgp.he.net.