Skip to content
thenetworkery

Network report

Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.

IP address, prefix or AS number

AS264943 · 

curl -s "https://thenetworkery.com/api/v1/network-report?query=AS264943"
JSON Docs

Warning: AS264943 (AS264943) announces 4 IPv4 and 1 IPv6 prefixes. 2 warnings

AS pageAS264943
HolderAS264943 - VIARAPIDA TELECOMUNICACOES LTDA - ME
AllocationLACNIC, Brazil (BR), allocated 2016-04-25
Prefixes (IPv4 / IPv6)4 / 1
RPKI valid0% (0 / 5)
Upstreams and peers11
Peering policyOpen

What to fix

  1. Warning

    5 of 5 announced prefixes have no ROA (RPKI not found): 167.250.60.0/22, 168.232.136.0/22, 170.231.200.0/22, 170.244.248.0/22, 2804:3050::/32.

    Without a ROA, networks cannot tell your routes from a hijack.

    Fix: Create a ROA for each at your RIR portal, with origin AS264943 and a max length equal to the prefix length:

    167.250.60.0/22 AS264943 max-length /22
168.232.136.0/22 AS264943 max-length /22
170.231.200.0/22 AS264943 max-length /22
170.244.248.0/22 AS264943 max-length /22
2804:3050::/32 AS264943 max-length /32

    Open in RPKI / ROA validator Guide

  2. Warning

    No public NOC, policy or technical contact.

    Other networks use these addresses to set up peering and to reach you during an incident.

    Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.

    Open in PeeringDB lookup

Checks

Routing and RPKI 5 of 5 announced prefixes have no ROA (RPKI not found): 167.250.60.0/22, 168.232.136.0/22, 170.231.200.0/22, 170.244.248.0/22, 2804:3050::/32.
  • Pass: AS264943 announces 4 IPv4 and 1 IPv6 prefixes.
  • Warning: 5 of 5 announced prefixes have no ROA (RPKI not found): 167.250.60.0/22, 168.232.136.0/22, 170.231.200.0/22, 170.244.248.0/22, 2804:3050::/32.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 11 upstreams and peers, 17 downstream networks seen.
HolderAS264943 - VIARAPIDA TELECOMUNICACOES LTDA - ME
IPv4 prefixes4
IPv6 prefixes1
RPKI5 not found
Downstream networks17
Routes to fix
PrefixRPKI
167.250.60.0/22 No ROA
168.232.136.0/22 No ROA
170.231.200.0/22 No ROA
170.244.248.0/22 No ROA
2804:3050::/32 No ROA

Upstreams and peers seen to the left 11

AS7195 EdgeUno AS3356 Lumen AS3356 AS6939 Hurricane Electric AS264409 Huge Networks / Grupo YAX AS1031 PEER-1 AS262847 Hoinaski & Sklasky AS53062 Brasil TecPar AS61599 EAÍ TELECOMUNICAÇÕES LTDA AS33891 Core-Backbone AS6057 ANTEL AS137409 Global Secure Layer

Announced prefixes 5

167.250.60.0/22 168.232.136.0/22 170.231.200.0/22 170.244.248.0/22 2804:3050::/32

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration Found at rdap.lacnic.net.
  • Pass: Found at rdap.lacnic.net.
NameASN264943
Handle264943
RangeAS264943
CountryBR
Registered2016-04-25T12:15:53Z
Last changed2016-04-25T12:15:53Z
Abuse contactnoc@viarapidanet.com.br
Allocation
Registry (RIR)LACNIC
CountryBrazil (BR)
Delegated on2016-04-25
StatusAllocated
Delegated rangeAS264943

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts
RoleNameEmail
registrant VIARAPIDA TELECOMUNICAÇÕES LTDA - ME
administrative, abuse Viarapida Telecomunicações - NOC noc@viarapidanet.com.br

Source: https://rdap.lacnic.net/rdap/autnum/264943. Registration data from rdap.lacnic.net, shown under its terms of use (terms): not for marketing or bulk collection.

Open in WHOIS / RDAP lookup
PeeringDB No public NOC, policy or technical contact.
  • Pass: AS264943 is in PeeringDB as VIARAPIDA TELECOMUNICAÇÕES.
  • Info: Peering policy: Open.
  • Info: Present at 3 internet exchanges with 3 ports (220G in total).
  • Warning: No public NOC, policy or technical contact.
NetworkVIARAPIDA TELECOMUNICAÇÕES (VIARAPIDA TELECOM)
AS numberAS264943
TypeNSP, Regional
Websitehttp://www.viarapidanet.com.br
IRR as-setAS264943:AS-GLOBAL
Prefixes (IPv4 / IPv6)160 / 20
Traffic100-200Gbps, Mostly Inbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2026-05-11

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup