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

AS265095 ·

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

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

AS pageAS265095
HolderAS265095 - Grimm Telecom
AllocationLACNIC, Brazil (BR), allocated 2016-07-14
Prefixes (IPv4 / IPv6)3 / 1
RPKI valid0% (0 / 4)
Upstreams and peers8

What to fix

  1. Warning

    4 of 4 announced prefixes have no ROA (RPKI not found): 170.254.24.0/22, 170.254.24.0/23, 170.254.26.0/23, 2804:32b8::/32.

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

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

    170.254.24.0/22 AS265095 max-length /22
    170.254.24.0/23 AS265095 max-length /23
    170.254.26.0/23 AS265095 max-length /23
    2804:32b8::/32 AS265095 max-length /32

    Open in RPKI / ROA validator Guide

  2. Warning

    1 of 4 announced prefixes have no IRR route object: 170.254.26.0/23.

    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 AS265095 in your RIR’s IRR database (or RADB).

    route: 170.254.26.0/23
    origin: AS265095

    Open in ASN & BGP prefix lookup

  3. 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

  4. 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 4 of 4 announced prefixes have no ROA (RPKI not found): 170.254.24.0/22, 170.254.24.0/23, 170.254.26.0/23, 2804:32b8::/32.
  • Pass: AS265095 announces 3 IPv4 and 1 IPv6 prefixes.
  • Warning: 4 of 4 announced prefixes have no ROA (RPKI not found): 170.254.24.0/22, 170.254.24.0/23, 170.254.26.0/23, 2804:32b8::/32.
  • Warning: 1 of 4 announced prefixes have no IRR route object: 170.254.26.0/23.
  • Info: 8 upstreams and peers, 0 downstream networks seen.
HolderAS265095 - Grimm Telecom
IPv4 prefixes3
IPv6 prefixes1
RPKI4 not found
Without IRR route object1
Downstream networks0
Routes to fix
PrefixRPKI
170.254.24.0/22 No ROA
170.254.24.0/23 No ROA
170.254.26.0/23 No ROA
2804:32b8::/32 No ROA

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.
NameASN265095
Handle265095
RangeAS265095
CountryBR
Registered2016-07-14T11:56:13Z
Last changed2020-11-03T18:07:35Z
Abuse contactcremmjunior@hotmail.com
Allocation
Registry (RIR)LACNIC
CountryBrazil (BR)
Delegated on2016-07-14
StatusAllocated
Delegated rangeAS265095

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

Contacts
RoleNameEmail
registrant Grimm Telecom
administrative, abuse Rogério Cremm Junior cremmjunior@hotmail.com

Source: https://rdap.lacnic.net/rdap/autnum/265095. 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: AS265095 is in PeeringDB as Grimm Telecom.
  • 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.
NetworkGrimm Telecom
AS numberAS265095
Type, Not Disclosed
Prefixes (IPv4 / IPv6)0 / 0
TrafficNot Disclosed
Ratio requiredNo
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup