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

AS262773 ·

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

Problem: AS262773 (AS262773) announces 353 IPv4 and 58 IPv6 prefixes. 1 problem · 2 warnings

AS pageAS262773
HolderAS262773 - PROXXIMA TELECOMUNICACOES SA
AllocationLACNIC, Brazil (BR), allocated 2010-08-30
Prefixes (IPv4 / IPv6)353 / 58
RPKI valid100% (409 / 411)
Upstreams and peers14
Peering policyOpen

What to fix

  1. Problem

    1 of 411 announced prefixes are RPKI invalid: 138.122.3.0/24.

    A ROA covers them but does not allow this origin or prefix length, so networks that filter (most large ones do) drop these routes.

    Fix: Fix the ROAs (origin AS and max length) at your RIR, or stop announcing the routes.

    Open in RPKI / ROA validator Guide

  2. Warning

    1 of 411 announced prefixes have no ROA (RPKI not found): 138.97.224.0/22.

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

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

    138.97.224.0/22 AS262773 max-length /22

    Open in RPKI / ROA validator Guide

  3. Warning

    102 of 411 announced prefixes have no IRR route object: 177.22.251.0/24, 45.167.62.0/23, 177.152.72.0/22, 2804:9f8:4026::/48, 170.82.75.0/24 (+97).

    Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.

    Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS262773 in your RIR’s IRR database (or RADB).

    route: 177.22.251.0/24
    origin: AS262773
    
    route: 45.167.62.0/23
    origin: AS262773
    
    route: 177.152.72.0/22
    origin: AS262773

    Open in ASN & BGP prefix lookup

Checks

Routing and RPKI 1 of 411 announced prefixes are RPKI invalid: 138.122.3.0/24.
  • Pass: AS262773 announces 353 IPv4 and 58 IPv6 prefixes.
  • Problem: 1 of 411 announced prefixes are RPKI invalid: 138.122.3.0/24.
  • Warning: 1 of 411 announced prefixes have no ROA (RPKI not found): 138.97.224.0/22.
  • Info: 409 of 411 announced prefixes are RPKI valid.
  • Warning: 102 of 411 announced prefixes have no IRR route object: 177.22.251.0/24, 45.167.62.0/23, 177.152.72.0/22, 2804:9f8:4026::/48, 170.82.75.0/24 (+97).
  • Info: 14 upstreams and peers, 28 downstream networks seen.
HolderAS262773 - PROXXIMA TELECOMUNICACOES SA
IPv4 prefixes353
IPv6 prefixes58
RPKI409 valid · 1 invalid · 1 not found
Without IRR route object102
Downstream networks28
Routes to fix
PrefixRPKI
138.122.3.0/24 RPKI invalid
138.97.224.0/22 No ROA

Announced prefixes 411

45.167.60.0/22 45.167.60.0/23 45.167.62.0/23 45.175.216.0/22 45.175.216.0/23 45.175.216.0/24 45.175.217.0/24 45.175.218.0/23 45.175.218.0/24 45.175.219.0/24 45.228.144.0/22 45.228.144.0/23 45.228.144.0/24 45.228.145.0/24 45.228.146.0/24 45.228.147.0/24 131.255.220.0/22 131.255.220.0/24 131.255.221.0/24 131.255.222.0/23 131.255.222.0/24 131.255.223.0/24 138.36.176.0/22 138.36.176.0/23 138.36.176.0/24 138.36.177.0/24 138.36.178.0/23 138.36.178.0/24 138.36.179.0/24 138.94.156.0/22 138.94.156.0/23 138.94.156.0/24 138.94.157.0/24 138.94.158.0/23 138.94.158.0/24 138.94.159.0/24 138.97.224.0/22 138.122.0.0/22 138.122.2.0/24 138.122.3.0/24 138.122.36.0/22 138.122.36.0/24 138.122.37.0/24 138.122.38.0/24 138.122.39.0/24 138.122.76.0/22 138.122.76.0/23 138.122.76.0/24 138.122.77.0/24 138.122.78.0/23 138.122.78.0/24 138.122.79.0/24 138.185.164.0/22 138.185.164.0/23 138.185.166.0/23 143.137.60.0/22 143.137.60.0/23 143.137.62.0/23 143.202.124.0/22 143.202.124.0/23 143.202.124.0/24 143.202.125.0/24 143.202.126.0/23 143.202.126.0/24 143.202.127.0/24 167.249.48.0/22 167.249.48.0/24 167.249.49.0/24 167.249.50.0/24 167.249.51.0/24 168.194.120.0/22 168.194.120.0/23 168.194.122.0/23 168.194.178.0/24 168.197.72.0/22 168.197.72.0/23 168.197.72.0/24 168.197.73.0/24 168.197.74.0/23 168.197.74.0/24 168.197.75.0/24 168.205.108.0/24 168.205.109.0/24 168.205.110.0/24 168.205.111.0/24 168.232.112.0/22 168.232.112.0/23 168.232.112.0/24 168.232.113.0/24 168.232.114.0/23 168.232.114.0/24 168.232.115.0/24 170.79.48.0/22 170.82.72.0/22 170.82.72.0/23 170.82.72.0/24 170.82.74.0/23 170.82.74.0/24 170.82.75.0/24 170.231.11.0/24

Showing the first 100.

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.
NameASN262773
Handle262773
RangeAS262773
CountryBR
Registered2010-08-30T10:47:48Z
Last changed2025-11-28T18:24:09Z
Abuse contactmarcelo.macedo@proxxima.net
Allocation
Registry (RIR)LACNIC
CountryBrazil (BR)
Delegated on2010-08-30
StatusAllocated
Delegated rangeAS262773

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

Contacts
RoleNameEmail
registrant PROXXIMA TELECOMUNICACOES SA
administrative, abuse Marcelo Jose de Macedo Oliveira marcelo.macedo@proxxima.net

Source: https://rdap.lacnic.net/rdap/autnum/262773. 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 AS262773 is in PeeringDB as PROXXIMA TELECOMUNICAÇÕES.
  • Pass: AS262773 is in PeeringDB as PROXXIMA TELECOMUNICAÇÕES.
  • Info: Peering policy: Open.
  • Info: Present at 3 internet exchanges with 3 ports (210G in total).
  • Info: The record was last updated 2023-04-13.
NetworkPROXXIMA TELECOMUNICAÇÕES (Proxxima)
AS numberAS262773
TypeCable/DSL/ISP, South America
Websitehttp://www.proxxima.net
IRR as-setAS262773:AS-PROXXIMA
Prefixes (IPv4 / IPv6)200 / 50
Traffic500-1000Gbps, Mostly Inbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Looking glasshttp://lg.proxximatelecom.com.br
Last updated2023-04-13
Contacts
Technicalpeering@proxxima.net

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup