Skip to content

Autonomous System

AS28271 — AS28271 - DataCorpore Servicos e Representacoes(BR)

Last fetched

AS28271 is an Autonomous System operated by AS28271 - DataCorpore Servicos e Representacoes and registered in BR. As of Thu, 06 Aug 2026 10:21:25 GMT, it announces 7 routed IP prefixes and peers with 12 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS28271Routing diversity4.5/10Peering density4.4/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/28271

Routing footprint

AS28271 announces 7 distinct routed prefixes. The 7-prefix sample below links to per-prefix pages with full conflict and reverse-DNS detail.

Peering ecosystem

12 distinct peers via BGP. The first 12 are listed below.

Peer ASNOperatorCountry
AS262403AS262403 - Net Way Telecom LTDA MEBR
AS262714AS262714 - Empresa Municipal de Informatica s/aBR
AS263009AS263009 - FORTE TELECOM LTDA.BR
AS268014AS268014 - Tribunal de Justica do Estado do Rio de JaneiroBR
AS271212AS271212 - RL Connect Telecomunicacao LTDABR
AS273729AS273729 - Net Gates TelecomBR
AS274670AS274670 - Tribunal de Contas do Estado do Rio de JaneiroBR
AS3356LEVEL3 - Level 3 Parent, LLCUS
AS52550AS52550 - Etaf Telecom EireliBR
AS53225AS53225 - IPGLOBE INTERNET LTDABR
AS54253ORCL-CHICAGO-PP - Oracle CorporationUS
AS6939HURRICANE - Hurricane Electric LLCUS

Blast radius

Count of dependent hostnames if AS28271 disappeared from the routing table.

832 hostnames depend on this network.Exact count across all 8 announced prefixes. Snapshot Sat, 25 Jul 2026 11:00:39 GMT.

MOAS / hijack watch

Prefixes routed by AS28271 that another Autonomous System also announces. A non-empty list is one of the strongest BGP-hijack signals available without active probes.

No active MOAS conflicts. Every prefix announced by AS28271 is unique to AS28271 in the current routing snapshot.

Threat posture

Related pages

Pivot deeper into the graph from AS28271.

Cypher and MCP

Reproduce the headline metric directly against graph.whisper.security:

MATCH (a:ASN {name: "AS28271"})-[:HAS_NAME]->(n:ASN_NAME)
OPTIONAL MATCH (a)-[:HAS_COUNTRY]->(c:COUNTRY)
RETURN a.name AS asn, n.name AS operator, c.name AS country

Or query Whisper from your own LLM workflow via the Whisper MCP server.