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

AS203178 · 

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

Warning: AS203178 (AXARNET-RESERVED) announces nothing right now. 1 warning

AS pageAS203178
HolderAXARNET-RESERVED AXARNET COMUNICACIONES, S.L.
AllocationRIPE NCC, Spain (ES), allocated 2016-03-16
Prefixes (IPv4 / IPv6)0 / 0

What to fix

  1. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI AS203178 is not announcing anything right now.
  • Info: AS203178 is not announcing anything right now.
HolderAXARNET-RESERVED AXARNET COMUNICACIONES, S.L.
IPv4 prefixes0
IPv6 prefixes0
Downstream networks0

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

Open in ASN & BGP prefix lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameAXARNET-RESERVED
HandleAS203178
RangeAS203178
Statusactive
Registered2016-03-16T11:19:05Z
Last changed2026-09-24T09:54:53Z
Abuse contactabuse@axarnet.es
Allocation
Registry (RIR)RIPE NCC
CountrySpain (ES)
Delegated on2016-03-16
StatusAllocated
Delegated rangeAS203178

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

Contacts
RoleNameEmail
registrant AS50926-MNT
registrant AXARNET COMUNICACIONES, S.L.
registrant RIPE-NCC-END-MNT
abuse Abuse Team - Axarnet Group abuse@axarnet.es

Source: https://rdap.db.ripe.net/autnum/203178. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.

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