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

AS61571 · 

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

Warning: AS61571 (AS61571) announces 1 IPv4 and 1 IPv6 prefixes. 3 warnings

AS pageAS61571
HolderAS61571 - Metro Tecnologia
AllocationLACNIC, Brazil (BR), allocated 2015-03-09
Prefixes (IPv4 / IPv6)1 / 1
RPKI valid0% (0 / 2)
Upstreams and peers1
Peering policyOpen

What to fix

  1. Warning

    2 of 2 announced prefixes have no ROA (RPKI not found): 200.0.89.0/24, 2801:80:ed0::/48.

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

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

    200.0.89.0/24 AS61571 max-length /24
2801:80:ed0::/48 AS61571 max-length /48

    Open in RPKI / ROA validator Guide

  2. Warning

    No IRR as-set is listed.

    Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.

    Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.

    Open in PeeringDB lookup

  3. 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 2 of 2 announced prefixes have no ROA (RPKI not found): 200.0.89.0/24, 2801:80:ed0::/48.
  • Pass: AS61571 announces 1 IPv4 and 1 IPv6 prefixes.
  • Warning: 2 of 2 announced prefixes have no ROA (RPKI not found): 200.0.89.0/24, 2801:80:ed0::/48.
  • Pass: Every announced prefix has an IRR route object.
  • Info: One upstream or peer seen (AS28670): an outage there takes the whole network off the internet.
HolderAS61571 - Metro Tecnologia
IPv4 prefixes1
IPv6 prefixes1
RPKI2 not found
Downstream networks0
Routes to fix
PrefixRPKI
200.0.89.0/24 No ROA
2801:80:ed0::/48 No ROA

Upstreams and peers seen to the left 1

AS28670 REDEL

Announced prefixes 2

200.0.89.0/24 2801:80:ed0::/48

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.
NameASN61571
Handle61571
RangeAS61571
CountryBR
Registered2015-03-09T11:43:57Z
Last changed2019-11-29T13:38:59Z
Abuse contactcgr@metronetwork.com.br
Allocation
Registry (RIR)LACNIC
CountryBrazil (BR)
Delegated on2015-03-09
StatusAllocated
Delegated rangeAS61571

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

Contacts
RoleNameEmail
registrant Metro Tecnologia
administrative Gerencia de Recursos Metro Network financeiro@metronetwork.com.br
abuse CGR - Metro Network cgr@metronetwork.com.br

Source: https://rdap.lacnic.net/rdap/autnum/61571. 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 IRR as-set is listed.
  • Pass: AS61571 is in PeeringDB as Metro Network.
  • Info: Peering policy: Open.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2022-07-27.
NetworkMetro Network (Empresa especializada na operação de empresas de telecomunicações)
AS numberAS61571
TypeEnterprise, South America
Websitehttp://www.metronetwork.com.br
Prefixes (IPv4 / IPv6)1 / 0
TrafficBalanced
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup