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

AS18449 · 

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

Warning: AS18449 (AS18449) announces 4 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS18449
HolderAS18449 - MVS Net, S.A. de C.V.
AllocationLACNIC, Mexico (MX), allocated 2000-08-30
Prefixes (IPv4 / IPv6)4 / 0
RPKI valid50% (2 / 4)
Upstreams and peers2

What to fix

  1. Warning

    No IPv6 prefixes announced.

    Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.

    Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.

    Open in ASN & BGP prefix lookup

  2. Warning

    2 of 4 announced prefixes have no ROA (RPKI not found): 201.139.1.0/24, 201.139.2.0/24.

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

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

    201.139.1.0/24 AS18449 max-length /24
201.139.2.0/24 AS18449 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    2 of 4 announced prefixes have no IRR route object: 201.139.2.0/24, 201.139.1.0/24.

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

    route: 201.139.2.0/24
origin: AS18449

route: 201.139.1.0/24
origin: AS18449

    Open in ASN & BGP prefix lookup

  4. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS18449 announces 4 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 2 of 4 announced prefixes have no ROA (RPKI not found): 201.139.1.0/24, 201.139.2.0/24.
  • Info: 2 of 4 announced prefixes are RPKI valid.
  • Warning: 2 of 4 announced prefixes have no IRR route object: 201.139.2.0/24, 201.139.1.0/24.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderAS18449 - MVS Net, S.A. de C.V.
IPv4 prefixes4
IPv6 prefixes0
RPKI2 valid · 2 not found
Without IRR route object2
Downstream networks0
Routes to fix
PrefixRPKI
201.139.1.0/24 No ROA
201.139.2.0/24 No ROA

Upstreams and peers seen to the left 2

AS8151 Uninet S.A. de C.V. AS19332 Marcatel COM

Announced prefixes 4

201.139.1.0/24 201.139.2.0/24 201.139.3.0/24 201.139.14.0/24

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration Found at rdap.arin.net.
  • Pass: Found at rdap.arin.net.
Name18449
HandleAS18449
RangeAS18449
Statusactive
Registered2000-08-30T12:00:00Z
Last changed2011-06-22T19:28:16Z
Abuse contactafernandez@mvs.com
Allocation
Registry (RIR)LACNIC
CountryMexico (MX)
Delegated on2000-08-30
StatusAllocated
Delegated rangeAS18449

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

Contacts
RoleNameEmail
registrant MVS Net, S.A. de C.V.
administrative Ivan Diaz Gonzalez admcom_gmvs@mvs.com
technical, abuse Alvaro Fernandez afernandez@mvs.com

Source: https://rdap.arin.net/registry/autnum/18449. Registration data from rdap.arin.net, shown under its terms of use (terms): not for marketing or bulk collection.

Open in WHOIS / RDAP lookup
PeeringDB PeeringDB did not answer: HTTP 404
  • Warning: PeeringDB did not answer: HTTP 404

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup