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

AS28458 ·

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

Warning: AS28458 (AS28458) announces 212 IPv4 and 2 IPv6 prefixes. 2 warnings

AS pageAS28458
HolderAS28458 - IENTC S DE RL DE CV
AllocationLACNIC, Mexico (MX), allocated 2015-06-29
Prefixes (IPv4 / IPv6)212 / 2
RPKI valid69% (147 / 214)
Upstreams and peers84
Peering policyOpen

What to fix

  1. Warning

    10 of 214 announced prefixes have no ROA (RPKI not found): 38.49.128.0/24, 38.49.129.0/24, 38.49.130.0/24, 38.49.131.0/24, 38.49.132.0/24 (+5).

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

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

    38.49.128.0/24 AS28458 max-length /24
    38.49.129.0/24 AS28458 max-length /24
    38.49.130.0/24 AS28458 max-length /24
    38.49.131.0/24 AS28458 max-length /24
    38.49.132.0/24 AS28458 max-length /24
    38.49.133.0/24 AS28458 max-length /24
    38.49.134.0/24 AS28458 max-length /24
    38.49.135.0/24 AS28458 max-length /24
    38.49.136.0/24 AS28458 max-length /24
    38.49.137.0/24 AS28458 max-length /24

    Open in RPKI / ROA validator Guide

  2. Warning

    99 of 214 announced prefixes have no IRR route object: 206.135.88.0/24, 206.135.13.0/24, 206.135.14.0/24, 206.135.73.0/24, 206.135.30.0/24 (+94).

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

    route: 206.135.88.0/24
    origin: AS28458
    
    route: 206.135.13.0/24
    origin: AS28458
    
    route: 206.135.14.0/24
    origin: AS28458

    Open in ASN & BGP prefix lookup

Checks

Routing and RPKI 10 of 214 announced prefixes have no ROA (RPKI not found): 38.49.128.0/24, 38.49.129.0/24, 38.49.130.0/24, 38.49.131.0/24, 38.49.132.0/24 (+5).
  • Pass: AS28458 announces 212 IPv4 and 2 IPv6 prefixes.
  • Warning: 10 of 214 announced prefixes have no ROA (RPKI not found): 38.49.128.0/24, 38.49.129.0/24, 38.49.130.0/24, 38.49.131.0/24, 38.49.132.0/24 (+5).
  • Info: 147 of 214 announced prefixes are RPKI valid.
  • Info: The RPKI state of 57 prefixes was not looked up (no ROA of AS28458 covers them; only the first 10 are checked).
  • Warning: 99 of 214 announced prefixes have no IRR route object: 206.135.88.0/24, 206.135.13.0/24, 206.135.14.0/24, 206.135.73.0/24, 206.135.30.0/24 (+94).
  • Info: 84 upstreams and peers, 50 downstream networks seen.
HolderAS28458 - IENTC S DE RL DE CV
IPv4 prefixes212
IPv6 prefixes2
RPKI147 valid · 10 not found · 57 not looked up
Without IRR route object99
Downstream networks50
Routes to fix

Announced prefixes 214

38.49.128.0/24 38.49.129.0/24 38.49.130.0/24 38.49.131.0/24 38.49.132.0/24 38.49.133.0/24 38.49.134.0/24 38.49.135.0/24 38.49.136.0/24 38.49.137.0/24 38.49.138.0/24 38.49.139.0/24 38.49.140.0/24 38.49.141.0/24 38.49.142.0/24 38.49.143.0/24 38.49.144.0/24 38.49.145.0/24 38.49.146.0/24 38.49.147.0/24 38.49.148.0/24 38.49.149.0/24 38.49.150.0/24 38.49.151.0/24 38.49.152.0/24 38.49.153.0/24 38.49.154.0/24 38.49.155.0/24 38.49.156.0/24 38.49.157.0/24 38.49.158.0/24 38.49.159.0/24 38.65.136.0/24 38.65.137.0/24 38.65.138.0/24 38.65.139.0/24 38.194.224.0/24 38.194.226.0/24 38.194.227.0/24 38.194.228.0/24 38.194.229.0/24 38.194.230.0/24 38.194.231.0/24 38.194.232.0/24 38.194.233.0/24 38.194.235.0/24 38.194.236.0/24 38.194.237.0/24 38.194.238.0/24 38.194.239.0/24 38.194.240.0/24 38.194.241.0/24 38.194.242.0/24 38.194.243.0/24 38.194.245.0/24 38.194.246.0/24 38.194.247.0/24 38.194.248.0/24 38.194.249.0/24 38.194.250.0/24 38.194.251.0/24 38.194.252.0/24 38.194.253.0/24 38.194.254.0/24 38.194.255.0/24 38.226.209.0/24 45.195.1.0/24 45.195.79.0/24 124.198.144.0/24 134.49.66.0/24 134.49.68.0/24 134.49.70.0/23 134.49.73.0/24 134.49.94.0/23 136.176.162.0/23 136.176.170.0/23 136.176.172.0/22 136.176.176.0/24 136.176.180.0/22 138.122.96.0/22 138.122.96.0/24 138.122.97.0/24 138.122.98.0/24 138.122.99.0/24 145.63.162.0/24 145.63.164.0/24 145.63.166.0/23 145.63.169.0/24 145.63.170.0/24 145.63.174.0/23 145.63.178.0/24 145.63.190.0/23 154.94.0.0/24 154.197.58.0/24 154.212.5.0/24 154.212.6.0/24 154.212.7.0/24 156.252.12.0/22 156.252.12.0/24 156.252.13.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.
Name28458
HandleAS28458
RangeAS28458
Statusactive
Registered2015-06-29T15:46:53Z
Last changed2015-06-29T15:46:53Z
Abuse contactip@ientc.com
Allocation
Registry (RIR)LACNIC
CountryMexico (MX)
Delegated on2015-06-29
StatusAllocated
Delegated rangeAS28458

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

Contacts
RoleNameEmail
registrant IENTC S DE RL DE CV
administrative, technical, abuse IENTC Telecom ip@ientc.com

Source: https://rdap.lacnic.net/rdap/autnum/28458. 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 AS28458 is in PeeringDB as IENTC Telecom Mexico.
  • Pass: AS28458 is in PeeringDB as IENTC Telecom Mexico.
  • Info: Peering policy: Open.
  • Info: Present at 13 internet exchanges with 13 ports (1.1T in total).
NetworkIENTC Telecom Mexico (IENTC Telecom)
AS numberAS28458
TypeNSP, North America
Websitehttps://ientc.com
IRR as-setRADB::AS-IENTC-MX
Prefixes (IPv4 / IPv6)25000 / 646
Traffic5-10Tbps, Mostly Inbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2026-05-20
Contacts
Abuseabuse@ientc.com
Salescarriers@ientc.com
Technicalpeering@ientc.com

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup