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

AS268623 ·

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

Warning: AS268623 (AS268623) announces 7 IPv4 and 3 IPv6 prefixes. 2 warnings

AS pageAS268623
HolderAS268623 - VTEK TELECOM LTDA - ME
AllocationLACNIC, Brazil (BR), allocated 2018-10-11
Prefixes (IPv4 / IPv6)7 / 3
RPKI valid0% (0 / 10)
Upstreams and peers2
Peering policyOpen

What to fix

  1. Warning

    10 of 10 announced prefixes have no ROA (RPKI not found): 45.164.120.0/22, 45.164.120.0/23, 45.164.120.0/24, 45.164.121.0/24, 45.164.122.0/23 (+5).

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

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

    45.164.120.0/22 AS268623 max-length /22
    45.164.120.0/23 AS268623 max-length /23
    45.164.120.0/24 AS268623 max-length /24
    45.164.121.0/24 AS268623 max-length /24
    45.164.122.0/23 AS268623 max-length /23
    45.164.122.0/24 AS268623 max-length /24
    45.164.123.0/24 AS268623 max-length /24
    2804:5404:8000::/33 AS268623 max-length /33
    2804:5404::/32 AS268623 max-length /32
    2804:5404::/33 AS268623 max-length /33

    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 10 of 10 announced prefixes have no ROA (RPKI not found): 45.164.120.0/22, 45.164.120.0/23, 45.164.120.0/24, 45.164.121.0/24, 45.164.122.0/23 (+5).
  • Pass: AS268623 announces 7 IPv4 and 3 IPv6 prefixes.
  • Warning: 10 of 10 announced prefixes have no ROA (RPKI not found): 45.164.120.0/22, 45.164.120.0/23, 45.164.120.0/24, 45.164.121.0/24, 45.164.122.0/23 (+5).
  • Pass: Every announced prefix has an IRR route object.
  • Info: 2 upstreams and peers, 3 downstream networks seen.
HolderAS268623 - VTEK TELECOM LTDA - ME
IPv4 prefixes7
IPv6 prefixes3
RPKI10 not found
Downstream networks3
Routes to fix

Upstreams and peers seen to the left 2

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.
NameASN268623
Handle268623
RangeAS268623
CountryBR
Registered2018-10-11T11:40:14Z
Last changed2021-08-18T20:22:18Z
Abuse contactvanilson4@hotmail.com
Allocation
Registry (RIR)LACNIC
CountryBrazil (BR)
Delegated on2018-10-11
StatusAllocated
Delegated rangeAS268623

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

Contacts
RoleNameEmail
registrant VTEK TELECOM LTDA - ME
administrative, abuse Vanilson dos Santos Ferreira vanilson4@hotmail.com

Source: https://rdap.lacnic.net/rdap/autnum/268623. 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: AS268623 is in PeeringDB as VTEK TELECOM.
  • Info: Peering policy: Open.
  • Info: No internet exchange ports are listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2024-07-05.
NetworkVTEK TELECOM (VTEK TELECOM)
AS numberAS268623
TypeCable/DSL/ISP, Regional
Websitehttp://www.vtek.net.br/
IRR as-setAS268623:AS-VTEKTELECOM
Prefixes (IPv4 / IPv6)7 / 7
Traffic5-10Gbps, Balanced
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2024-07-05

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup